[haiku] Re: Translation/localization info for translators
- From: PulkoMandy <pulkomandy@xxxxxxxxx>
- To: haiku@xxxxxxxxxxxxx
- Date: Sun, 28 Mar 2010 12:34:37 +0200
> So now, in the spirit of helping out, I have changed the "I've finished my
> translation. Now what?" entry of the HTA FAQ to the following:
>
> "At present, the process of committing the approved translations to the Haiku
> repository is done manually by the Haiku developers. The localization
> progress is being monitored and approved translations are periodically
> committed to the Haiku repository. You can keep an eye on the SVN Commits Log
> mailing list to see when your translation work is committed."
>
> If you feel the above statement needs to be changed, please let me know via
> reply to this list or feel free make the changes yourself on HTA.
Looks fine to me.
>
>> When :
>> 1) all the bugs in hta are fixed
>> 2) the translation approval system is in place
>> we will consider moving to an automated commit system so that I don't
>> have to handle all the translations by hand (they are going way to
>> fast for me and I'm lagging behind).
>
> It does look like you are carrying all the burden here. Is there room for
> other people helping lower your load somehow? HTA seems to be pretty
> straightforward, so if a trusted non-developer could prepare the files for
> you, then perhaps the language managers could do the work of downloading the
> patches for you, and all you would have to do is commit to SVN. What do you
> think?
hta should allow anyone to export a patch with all the files ;
commiting it to svn would then be straightforward and could be
automated. Unfortunately, this functionality is broken, meaning
someone have to change the jamfiles by hand (exporting the catkeys
themselves works fine).
>
>> We're trying to improve the workflow itself, things changes on a day
>> to day basis, so expect the documentation to get out of sync.
>
> The problem does not seem to be documentation being out of sync because of
> changes in the workflow, but rather a problem of duplication of resources and
> lack of coordination and among the people using different resources for
> different purposes (translation of user guide vs. translation of
> applications). In my own experience, there is a clear disconnect between
> translating the user guide and translating the system and its applications,
> and this IMNSHO makes it more complicated for the translators to be
> productive, and also affects the quality of the work as it leads to
> inconsistencies in the translations.
>
> A good first step to improve the situation would be to consolidate where the
> info for localization/translators is documented (currently Trac wiki vs. HTA
> vs. user guide translation tool) and where the translation/localization
> discussions take place (currently at mailing lists vs. HTA comments).
>
> As a general observation, your last paragraph seems to imply that
> improvements are being considered/discussed/worked on; however, it is not
> clear where this is happening. Being heavily involved in the Japanese
> localization and engaged to a lesser degree in the translation to Spanish, I
> would like to help make changes to the localization processes to improve the
> workflow and coordination. Can share with the rest of us where these
> discussions are taking place so that we can also participate and potentially
> contribute?
There are two separate tasks here : I was talking about the workflow
between hta and the svn to get the catalogs online. It is not
expected, as of now, for the translators to take part into this
process. As for what happens above that (the translation itself), I
don't know much about it. I think you could hask Travis and Vincent to
coordinate their efforts in making the best tools available...
--
Adrien Destugues / PulkoMandy
http://pulkomandy.ath.cx
Other related posts:
