18
From twext
|
we need to
[edit] simplify.twx describes filename=db proposal.. maybe too complex at this demo stage? we don't need #tags yet.. we could start more basic: currently in xml we have: <twext> <para> <line> <text>hello</text> <twxt>hola</twxt> </line> </para> </twext> AFAIK, minimum "meta" data we need in file is: title twxt_lang TEXT_LANG we can prepare to add more in future, ie: date_created date_modified author owner license editors (translators) tags so, if we restrict new xml tags to minimum, we add: <twext> <title>TITLE OF DOCUMENT</title> <TEXT_LANG>ENGLISH</TEXT_LANG> <twxt_lang>español</twxt_lang> <para> <line> <text>hello</text> <twxt>hola</twxt> </line> </para> </twext> now we can save a title in within twext language categories (no more need for twext folders) probably the simplest system will * acheive intended demo result * provide user feedback on what next intent of http://twext.cc/go/18#.twx is make human readable summary of findable data easily accessible and easy to improve.. if we can make this very simple multilingual twexter work w/ http://twext.cc/go/18#.twx that might be cool.. but if it's really complex better simple for now.. [edit] if we try .twxif .twx filename=db and array definitions from RIGHT TO LEFT, then maybe .twx file named like this: ..twextlanguage.TEXTLANGUAGE..title..twx_version..timestamp.twx * timestamp is our always unique resource locator * twx_version maps meta data ie: ..3..2..1..0.twx = map for .twx version 0.1 ..twx.TXT.. = twext language.TEXT LANGUAGE (case sensitive) ..title = document title ..twx_version_0.1 = version of .twx array ..timestamp = unique resource locator then filename might look like this: ..español.ENGLISH..Example-of-a-Filename..0.1..20060425.122022.0.twx
contents of file might look like this:
<twext>
<time>20060425.122022.0</time>
<version>0.1</version>
<title>Example of a Filename</title>
<TXT>ENGLISH</TXT>
<twx>español</twx>
<para>
<line>
<text>hello</text>
<twxt>hola</twxt>
</line>
</para>
</twext>
[edit] .twx.twx is now called dodo .twx is maybe we turn titles into somekinda database so we define and find data in a ..numbered namespace.. ..n..twx ..0..1..2..3..4..twx ..what..where..when..who..etc..twx ..title..langs..time..editors..tags..twx ..long_title..ENGLISH.espanol..200714.093422.1..waqas,duke..file_system,spot,db..twx print report easy: title: LONG HONKIN TITLE langs: ENGLISH.espanol clock: 200714.093422,1 edits: waqas, duke mtags: file system, spot, meaningful url, twexter, db search could focus on specific ..n.. to find.. [edit] timestamptimestamp per save spots single point of truth in memory.. so a .twx file needs not title (..0..) thus can maybe serve dichos and citage.. a twext_object?
[edit] historyif file saved (w/ timestamp but no other info), then later opened and modified, the new file should be associated with the original.. maybe if ..0.. = timestamp, then ..20070425.123456.789_20070422.123456.789.. ? saving file histories is needed for wiki-like revert capabilities.. together, files record a process.. [edit] twext objecttimestamp creates a twext object ..time..twx further definable by languages, tags, title.. [edit] mtagstags (google labels) categorize info.. can simple markup make tags meta? a;author l;license so, if ..4.. = ..mtags.. then in ..4..: ..l;link,c;credit,a;author,l;loop,w;whateva.. simple arrays [edit] translatableif 1A=A3 2B=B1 3C=C2 then 1=3 2=1 3=2 so could be rearranged right to left: ..who..tag..when..where..what..twexml disorder, reordered: ..wtf..what..where..who..when..twexml ..3..2..1..0..twx or mapped to new versions of .twx data? [edit] garbage collection? [edit] findturn url field into search interface ie if twext.cc/x;english,xx;espanol..a;lennon is input direct into url field, then twexter searches twext.cc for "ENGLISH" TEXT with "spanish" twext for author "Lennon" or search by date, language pair twext.cc/t;20070425,x;english;xx;espanol etc [edit] feedback
[edit] prefssimplest possible interface for user to control styles, output and languages to included/exclude [edit] slopSelect Language OPtionscombined w/ prefs from xnav: [edit] findsearch ..db..twx to find info in numbered namespace [edit] addlangsimplest possible interface to a add language [edit] complete interface
MULTILINGUAL TWEXTER SPEC evert says XUL.. we have twexml, maybe w/ ..db.. files?
"flexible" meaning easy to let other programs read data in saved file, as a single point of truth with variable output: then convert to various formats: hopfully ..db..twx solves below: [edit] searchable?you tell me.. sounds like XML lets us define new doc type, then perform searches to find only our new type of doc.. even filter specific searches within our new doc type.. if so, our new xml doc type might implement some features: [edit] language identificationgive user option to identify languages of TEXT and twext parts of saved file.. for example, within a document,
if someone is in brazil learning kiswahili, they'll want to find twext docs with big kiswahili TEXT supported by little twxt in portugues.. the design should anticipate trilingual and multilingual content within a single document.. at a root level, we might try to avoid being trapped by categories [edit] tagslet user simply add tags and maybe somekinda shortcut smart tag.. tags are good because data isn't trapped by categories.. categories are good because they help sort data.. tags are a great example of being able to categorize data without trapping it in some freaking folder somewhere.. we should find an easy, flexible way to include and modify tag info in our xml docs..
idea is to make it easy to tag a twext file w/ info easy to sort.. ie if line starts with "x;" then doc may include translator info repeat: i'm new to xml so this may sound real stupid.. [edit] title3rd in line.. titles are useful, but tags might be more useful.. especially in the context of delyric citage.. another type of title-less twext object may be dichos (simple quotes).. maybe titles could just be tags? please don't hurt me
below will digest w/ mockups the print above.. [edit] SLOP select language options menusSelect Language Option Menus might be DHTML trick.. basically, drop down menus loaded with user_pref langauges.. i've seen some work very well, others not.. so maybe two ways to go:
SLOP lets user Select Language OPtions.
slop uses dynamic menus: twexter responds to changes in either menu instantly, with no need for any additional input button. the interface language is controlled by the twext_slop_menu on the left. so if user changes twext_slop_menu from english to español, then interface language changes from english to español
on the right, the TEXT_slop_menu controls the TEXT language; this menu directs search queries, chunktext inputs or format fetches to internal xml format so if user changes TEXT_slop_menu from ESPAÑOL to ENGLISH, queries, fetches and inputs will interact with xml
the TEXT_slop_menu does not control the interface language, but make one exception: the word for "TEXT" (left of TEXT_slop_menu) should be in language selected by TEXT_slop_menu. confusing? either eliminate "twext" and "TEXT" labels (rely on lowercase in twext_slop and UPPERCASE in TEXT_slop) or just go DHTML:
solutions must be robust, bug-free, strong on most browsers and work with unicode. if in any SLOP MENU user selects "+"
temporarily save user input, so user can be sent back to page without losing input then send user to prefs: [edit] XPREF twext user preferencesto multilingualize, we need to identify languages.. adding languages to twext will hopefully be very easy, so many languages, even dialects, slangs, hybrids may be added.. too many.. users are likely to want to exclude many languages from their twext interface.. users may also want to control personal preferences for format, style and output of twext text between any two languages.. http://twext.cc/dev-old/xo/control.html shows ancient attempt at user preferences interface.. soon regurgitating here.. [edit] FINDhopefully "internal xml" output will produce flat files that, if stored in urls, can easily be searched with your favorite search engine.. hopefully, we can add tags to such "internal xml" output to filter searches by language, author, translator, generic tags, etc.. is this possible with xml output we're defining?
question re: naming convention
twext is meaning lots of things..
what should we call "twext internal xml ouput"? xxml? xmlx? twexml? twextxml?
[edit] ADDLANG add languages to systembefore adding langs to twext, user should be able to
addlang should cost minimal user work, and avoid being trapped by categories.. when preview, save, prefs, find, slop work, then we can add languages to twexter:
|
|
