WikizPad

Curl will make an easier wiki-pad than WikidPad because the Curl RichEditArea can generate the markup : The REA has both curl-source parse and format methods.

WikidPad is unable to display some of the input formatting until exported !  But Curl is a web content language for both data and processes - Curl offers both declarative markup and expression-based programming (rather like rebol, but without the graphics and UI issues and comes with two (2) developer IDE options (the Curl Lab or an Eclipse plugin.)

The security concern of generated markup can be addressed by requiring privilege for the applet and using a signed pcurl file along with encrypted text store.

WikizPad will offer one pane for formatting markup as RTF and one pane for editing markup as text (but with RTF appearance as desired for ease of edits.)

At the moment the features are being used for an SRS FlashCard edit/gen app, so reuse will be straight-forward.

[ more to follow ]

---

customized Curl flashcard

Some Curl flashcard markup proposals in the testbed viewer :

See
 http://www.aule-browser.com/flashcards/flashcard-kanji-03.dcurl
for Curl desktop code or
 flashcards/flashcard-kanji-03.curl
to run a test in the browser.

The test markup is

{EmFontSize 36pt}
{CardFontSize 18pt}
{CardBackground "blue"}
{HiLight "red"}

    {FrontSide color="gold", 

 日本語の漢字は {KJ \u9801} がです。
}

Curl flashcard markup

Here are three snaps of user editing flashcard output format using Curl as the markup :

then after an edit

then after a Curl markup edit

wikibooks as Curl ebooks

wikibooks as Curl ebooks

Currently some wiki books can be exported as PDF, ODT or ZIM.

[ what this space ]

---

formatting French ebooks

You might think that formatting French ebooks in Curl as web markup would be easy – and it is – but there are still challenges.

If you use the TocDocument as the default document-style there are markup hierarchy issues under each {heading level=n, } macro.

I usually start with simply a default vanilla {paragraph } macro and then move to user defined formats and procedures.

The challenge is to make this accessible to the non-programmer working in a non-Western language.

At this time I am evaluating two rebol language variants (r3 and red) and one Icon variant (Object Icon) for parsing my Curl markup in accordance NOT with Curl syntax but USER preferences.

If all else fails, I will fall back to Logtalk with some Prolog dialect.

In the case of my current French ebook, the rules are to cover non-breaking spaces. The rule of thumb in France is to surround "two-part" punctuation with spaces. The challenge is to address resizeable text frames or panes in which re-flowed text must remain readable.

The minor rules apply to ALL Curl ebooks where the text is in Curl markup (and until we have a webkit wrapper library, that is what I use) such as converting all ASCII single quotes, quotes, psuedo-hypens, brackets and installing matching left- and right- quotation devices.

---