Yes, I think an arrangement like that could work. The key first step would be to construct a mechanism for processing translations in slice/section format and automatically loading them up into the variables defined by Lingo.js.
I'm not recommending that we do this right now, of course - migrating tiddlywiki.org and subversion is the first step, Best wishes Jeremy On Mon, Jan 24, 2011 at 4:01 AM, Måns <[email protected]> wrote: >> --- addendum >> > Dealing with the JavaScript issue could be done by moving to a tiddler >> > slice and >> > section syntax, admittedly a fairly significant core change. >> >> Could we have a Space for translation (@translator space), which works >> sth like privateer, and is only meant for temporary inclusion... >> You include the @translator space and open a tiddler i.e [[localize]] >> and fill in a form which consists of a table with English terms and a >> corresponding inputfield. > > I believe translations for Spaces actually would need a second template > which deals with everything specific for TiddlySpace i.e TiddlySpace > backstage items and TiddlySpace theme (css wrapped items) like sideBarTabs > etc... Or have I overlooked/missed an alternative translation template made > especially for TiddlySpace?? > Cheers Måns Mårtensson > > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWikiDev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/tiddlywikidev?hl=en. > -- Jeremy Ruston mailto:[email protected] http://www.tiddlywiki.com -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
