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

Vincent Duvert wrote:
You got me by surprise :-p I wanted to wait for things to calm down a little on my side... But fortunately, this will be the case starting tomorrow. 

That's good to hear!
Anyway, nothing prevents you to start a manual translation process and then import the data in my system... It should not be too difficult. 

I'd prefer to wait a bit more and use your system.
I just had a look at it and I'm very impressed and delighted by what I've seen.
Now only the remaining issues have to be worked out. :)
The most important question is: Can you finish it all up and make it work from a haiku-os.org website (right, Jorge?) within the next few weeks?
If it provides PHP and MySQL (and write access to some directories from PHP), then yes, the current version should work right out of the box (with some minor tweaks if it uses another type of database engine.
Jorge or another web guy will chime in on that. Also, it doesn't have to be on a haiku-os.org domain, it'd just be nice. At worst we'd have to look for some other available server. But that's all for later. 


Other questions:
All languages are in that one page, right?
Yes, there are only two pages : the admin page and the status pages (that show links to English and translated pages)
I meant the index-magicked page, i.e. the English version plus all languages are in one file. Only later, when exporting/generating the final HTML it'll separate into the differnt language HTML. That may be beneficial, if you insert new things in the English section, it could automatically appear in the {language} sections, waiting to be translated. 


Is there versioning to revert changes for each language?
Unfortunately there is not, and I don't think this would be easy to do with the current DB architecture...
That's too bad. But I guess there's always the SVN repository that keeps track and some accidentally lost/modified contents could be copied over by hand. 


How are big/small changes to the English original handled?
At this time, they are not handled. To assign translate IDs to the original document, the script just compares the contents of translatable blocks with the strings it has in its database... 

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.. 
And of course also the opposite, removing this stuff.
And it all has to be reflected in all languages. Adding/removing stuff must only be possible for the English version, as that has to stay the reference for all others. 


Are localized images supported?
Not for now, but I see a way to do it (add another attribute to tell the JavaScript code that the "href" attribute should be translated, not the inner HTML)
OK. That's maybe not of a great priority as those images can be added by hand for now. Also, the localized GUI isn't here yet. But the way PulkoMandy is moving along, it will be soon... 


Are the finished generated languages automatically commited to SVN?
The webserver where the code is stored at this time does not allows running external programs, but adding a system('svn ci ...'); after the generation of localized files should not be too difficult. 

On further reflection, maybe SVN commits should be done manually for starters.


Regards,
Humdinger

--
--=-=--=-=--=-=--=-=--=-=--=-=--=-=--=-=--=-=--=-
Deutsche Haiku News @ http://www.haiku-gazette.de

Other related posts: