we have basic xml to css ouput from chunked text/twxt.. now were specifying outputs for multilingual twexter

[edit] TWEXML

sounds like XML is so we can write our own markup... perfect..

• twexml is unique string (no non-twext google results)

<twexml>
<textlang>
<twxtlang>
<line>
<chunk>
<text>
<twxt>
<bla>
<title>
<author>
<translator>
<owner>
<license>

[edit] XUL?

evert busy as a mother :-) emailed some advice re: xml xsl xul fo xliff odf etc

• xsl ill suited for binary formats.. not all XML transforms well into just another format. The base design of your xml-format is very important.
• most people take XML (that should be the one thing the "system") and transform it just a few strategically chosen formats, further transformed by other tools. ie paper output w/ FO (Formatting Objects: a specific DTD of XML, geared towards layout/formatting), which can then be transformed by dedicated tools to ... PDF ... etc etc.
• http://xmlgraphics.apache.org/fop/ and http://www.w3.org/Style/XSL/ to start with.
• to play it really nice, have XML transformed into XUL
• The real challenge is then getting the base XML-right ... Have a look at XLIFF. http://www.oasis-open.org/committees/xliff/documents/xliff-specification.htm
• SVG for more advanced graphic output.

i've heard the OLPC uses SVG for their high-res screen

• ODF (Open Document Format, used by among others OpenOffice ...) is free

[edit] back burner

maybe try soon

[edit] searching chunked text

prob: search engines can't read chunk-spanning TEXT strings

This might be solvable in a way, if we change

<text>blah</text>
<twxt>halb</twxt>

to

<text twxt='halb'>blah</text>

very interesting =) mut spec may be incompatable w/ "halb" but maybe not:)

• twexter
• input

OUTPUT

• twext
• twexml
• data
• dodo
• git

OI VE

• namespace in xml
• xliff
• fop
• xslt
• xsl
• xul
• jason

OK simple start = mysql for plugin test