Hi,
If this scheme will be manageable for translators or not depends on each
translators skills. ;-) Anyway, the easier the process would be, the better
for translator (and for not translators).
For editing language bundles I sometimes use Eclipse, though my preferred
editor is NotePad. Call me *traditional*...or even freak but it's faster
because the eclipse plugin has to render file content in a friendly UI and
this takes time.
Cheers,
David
2013/9/17 Jim Procter <[email protected]>
> Hi David.
>
> On Tue Sep 17 11:37:47 2013, David Roldán Martínez wrote:
> > And why not to give commit privileges to translators but only to
> > language bundle files? In this way, translator would be able to work
> > independently to the rest of committers.
> hmm. this would require a different architecture for Jalview's git
> repository - since commit privileges are granted at the level of
> branches and top level repository access. Read on below...
>
> > Besides, you won't have to
> > maintain two branches simplifying relase management, as i18n will a be
> > core functionality.
> that was always the plan :)
>
> Lets think about this another way. Jalview's source is going to be
> separated into components in the near future - to yield a set of
> modular compilation blocks. At the same time, I think it would also be
> a good idea to separate the i18n translation packs, and the Jalview
> help into separate components that would build jars and and OSGi
> bundles for adding to the runtime classpath. That would mean that
> translators could have commit access to translation packs independently
> of core code modules (which would still include core i18n).
>
> I foresee something like the following set of git repositories:
>
> jalview_apis.git
> jalview_core.git
> jalview_help.git
> jalview_cli.git
> jalview_lite.git
> jalview_desktop.git
> jalview_i18n.git
>
> The complication here is that Jalview has multiple components that
> involve i18n - cli (headless jalview), desktop (the application you've
> i18n'ed) and lite (the web applet). I still plan on a single build
> mechanism, and synchronization across repositories will be done with
> git submodules. Do you think that will be managable for translators ?
>
> Jim.
>
> ps, As an aside here, are there any web or desktop applications that
> allow language packs to be edited in a user friendly manner ? I'd be
> happy to install something on *.jalview.org that allowed translators to
> log in and work directly on translations.
>
> _______________________________________________
> Jalview-dev mailing list
> [email protected]
> http://www.compbio.dundee.ac.uk/mailman/listinfo/jalview-dev
>
_______________________________________________
Jalview-dev mailing list
[email protected]
http://www.compbio.dundee.ac.uk/mailman/listinfo/jalview-dev
