Re: transifex for translation updates
Vagrant Cascadian <[email protected]>
| Newsgroups | gmane.linux.terminal-server.devel |
|---|---|
| Message-ID | <[email protected]> |
On Sat, Mar 28, 2009 at 05:49:32PM -0400, David Johnston wrote:
> On Sat, 2009-03-28 at 07:07 -0700, Vagrant Cascadian wrote:
> > On Tue, Mar 10, 2009 at 11:21:28AM +1000, Noriko Mizumoto wrote:
> > > If you like to have this translated into other languages (including
> > > Japanese next time too), it might be good idea for you to register the
> > > package with Transifex.
> > > https://translate.fedoraproject.org/submit/maintainers/info
> >
> > thanks for the information! i'm not familiar with fedora's
> > infrastructure...
> > many of the translations thus far have come from debian's
> > translation infrastructure. that has largely worked well, although some
> > translations are lagging or are missing
> > is there a way to get transifex to only accept translations for a certain set
> > of languages (i.e. ones that are lagging or missing)?
> > i don't want to interfere with existing translation processes that are working
> > fine, but also don't want to present a barrier to additional help with
> > translations.
>
> Vagrant, are we pulling translations in automatically, or do you pull
> them in manually?
it's been all manually committed translations so far. every once in a while,
i've requested translation updates from all the previous translators and
translation teams, and posted requests for new translations, like so:
http://lists.debian.org/debian-i18n/2009/03/msg00112.html
> If it's automatic, it should be relatively simple to
> update the makefile so that it gets whichever translation (fedora or
> debian) is more current.
well, it's not just a simple matter of which is most current- some translation
teams may have different review processes and QA standards, for example. some
may have loose team structures or even just individual translators. some teams
are probably totally distro-independent.
i'd like the processes that have been working well to continue to work, while
leaving the door open for additional contributions.
live well,
vagrant
------------------------------------------------------------------------------
_____________________________________________________________________
Ltsp-developer mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-developer
For additional LTSP help, try #ltsp channel on irc.freenode.net