[haiku] Re: Haiku Translation Assistant ready for action
- From: "Travis D. Reed" <tdreed@xxxxxxxxx>
- To: haiku@xxxxxxxxxxxxx
- Date: Sat, 16 Jan 2010 19:04:19 -0600
I should clarify:
1. A developer localizes a program.
2. The developer compiles the SVN and uploads the generated default
catalog to the website.
3. Translators provide translations.
4. Once all the translations are available (I'm working on this now), the
developer generates that patch file from the website. This patch file
handles the new catkeys file as well as the modified Jamfile. All the
developer has to do is make sure the patch works.
5. The developer commits the patch.
6. If translators find bugs in the developer's work, they (soon) will be
able to notify the developer.
--
Travis D. Reed
On Sat, Jan 16, 2010 at 6:44 PM, Travis D. Reed <tdreed@xxxxxxxxx> wrote:
> Wow! I love seeing that I totally reproduced someone else's work! :( I
> *love* the screenshot idea and was planning it. Great minds think alike,
> huh?
>
> Workflow: Someone chooses what language and program they want to translate
> and then they start translating. SVN files can be imported (though I don't
> want to do that once everyone starts using the system as it would be
> redundant). I am working on Adrien's idea to mark a translation as ready to
> export.
>
> Imports from SVN work. Exports as patches work. It doesn't commit them
> automatically, though, as I do not (and DEFINITELY should not) have commit
> access. I think a living human should check on the patches before they are
> committed, but they seem to work.
>
> Was your site already working??? Want to join forces?!
>
> Travis D. Reed
>
>
>
> On Sat, Jan 16, 2010 at 4:30 PM, Siarzhuk Zharski <zharik@xxxxxx> wrote:
>
>> Hi, Travis!
>>
>> On Sat, 16 Jan 2010 00:33:20 -0600, "Travis D. Reed" <tdreed@xxxxxxxxx>
>> wrote:
>> > The Drupal version of my translation assistant is finally up and
>> running.
>> > Making translations is a snap now. (Though I won't certify the process
>> is
>> > entirely bug free.) Please let me know what you all think, especially if
>> > you're on the translation teams or are PulkoMandy.
>>
>> Nice to see that the same ideas are flying in the wind. We had the same
>> idea behind our translation wiki project at
>> http://siarzhuk.dyndns.org/wiki. It was targeted for some cyrillic
>> translations only. I think it can be interesting for you - especially the
>> idea of corresponding screen-shots for every translation table. ;-) It is
>> very helpful for keeping translation in the right context, isn't it? ;-)
>> What is the typical workflow of translation task? Does it include
>> automatic
>> commit of produced catkey-file onto Haiku source tree? Does
>> synchronization
>> from the sources tree to HTA tables work correctly?
>>
>> --
>> Kind Regards,
>> S.Zharski
>>
>>
>
Other related posts:
