Hi Jeremy > 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. When you are finished - you click "submit" and a new tiddler is created with all slices and sections (working in the background of the form) interpreted and put into the needed JavaScript quotes of a standard .js systemConfig tiddler. You exclude the @translator space and have the translation in your space. There should be some fallback-procedure, if you decide not to make a full translation, - then untouched fields should use the English terms suggested by the form... - no core change needed... Doable? 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.
