On Fri, Apr 22, 2011 at 5:26 PM, Rob Savoye <[email protected]> wrote:
> On 04/22/11 14:24, Chris Leonard wrote: > > > and commit after the PO was finalized. Our Pootle server would merely > serve > > as a collaborative tool for finding and completing the PO. > > Sure more complete coverage of our translations would be great. The > process you described for getting them upstream to us should be fine. > Most of the Gnash messages are debug oriented that nobody sees, but they > might as well be accessible to people in their own language if they do > want to see them. > > > I believe that some of you are fairly familiar with Sugar Labs / OLPC and > > that there are a number of Gnash project members that are also Sugar Labs > / > > OLPC participants (John Gilmore <jgilmore>; Tomeu Vizoso <tomeu>; > Sridhar > > I was also an OLPC developer, from way back in the beginning, and > still test Gnash on XO machines. :-) > > Given the positive feedback so far, I've copied your existing PO files down to our Pootle server. see gnash.po at: http://translate.sugarlabs.org/projects/upstream_POT/ I can and will add languages to that project as I've added the blank POT template to the Templates "language". It may be joined in Upstream POT by other project files over time. The best place for any questions or requests about our Pootle server is our localization list. http://lists.laptop.org/listinfo/localization I'm going to be brutally honest and say that I will not be tracking the gnash-dev list closely. For me it is yet-another-mailing-list among many (given that my focus is on L10n more than the packages themselves). I will stay subscribed but I'd be grateful if someone could ping me or the L10n list if there is something that requires Pootle work (e.g. new strings added to POT, new languages requested, etc.). I'm documenting efforts to track and contribute upstream on the wiki here: http://wiki.sugarlabs.org/go/Translation_Team/Upstream_localization I will flesh out the Gnash entry to make it clear that we host a local "unofficial" copy, but that committing it requires communication with the upstream. cjl
_______________________________________________ Gnash-dev mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnash-dev
