[haiku-doc] Re: Another try at user guide translations


Le 18 juil. 09 à 14:14, Humdinger a écrit :


>> This is the major thing that needs solving.
>> We need a way to a) insert whole blocks of stuff (e.g. <p>, <h1>, <table> etc.) into an >> original English page and also b) in-block things like changed words, an additional 
>> sentence etc.

[...]

Do I make any sense? Is it feasible? Got a better idea?

Makes sense.
One way to simplify the process would be to provide documentation authors a web interface similar to the translate interface, where small changes could be done ("big" changes would still be made by directly editing the file). This way, big changes (adding/removing/reordering blocks) are handled the same way it is now (and the translations should not be lost) ; and when a small change is done, the script knows to which block ID apply it (and can also validate the new XML code). After the edit, translations for this block would be marked as inexact (I'm not sure if a checksum is really necessary... Adding a boolean column "translation_fr_inexact" for each language should probably be enough). The tool could also provide a checkbox "Translations will not need updates after this edit", to avoid unvalidating translations when the edit was just a typo fix. Like you said, the original text would also be saved, and displayed to the translators. When the translation is validated, the "inexact" flag would be removed (the current tool checks if the XML entered has the same structure as the original, so we should not get out of sync XML). During the "commit" operation, English pages would be updated the same way this is currently done for translations (using an XML file tagged with the IDs). This means that the "update" process should be run first if the reference files were changed (or else their changes would be lost). 

Comments welcome ;-)

Vincent

Other related posts: