Re: experimental manual source for advanced translation handling

Jeroen van Wolffelaar wrote: > That the xml processing is slowed down is a pity, but it is > IMO not important. It's the output and the ease of modifying > /translating that counts, not the number of cycles wasted on it. the actual slowdown running jade was about 15sec with a total of 13min on my (slow disk) laptop, so nobody will really notice this > > [...] have them split up and recombined in the background > > during the actual built, but that is a different story ... > > The latter option is IMO best: you do not break CVS, you do > not have to change all files, and you can still edit the files > in a module-basis, rather than a single file for every minor > function. > For translation it is less useful, you'll need to get single functions > from the english sources when you want to translate a new function, > rather than simply copying a file. i still want to have each translation as a cvs module of its own, so breaking them up into single files might be a good chance to move them instead of updation the current repository maybe we could stay with the english version as is, but have a split up tree generated with the cvs version of the master file insterted as a comment at the very top so translaters could take this over as they do their work ... (although this would break the simple/stupid rule) and, hey, we could even build a web frontend for translators based on this, offering them only those parts for a change that really need one <evil_genious_mode> we could go even further and reduce translation files to the parts between <refpurpose>...</refpurpose> and </funcsynopsis>...</refsect1> while getting <refname> und <funcsynopsis> from the original file ;) </evil_genious_mode> -- Hartmut Holzgraefe hartmut@six.de http://www.six.de +49-711-99091-77