On Thu, Apr 18, 2013 at 1:08 PM, Dwayne Bailey <dwa...@translate.org.za> wrote: >> 2) As a fully-fledged UI, we have strings for our web-browser >> (Browse), our simple word processor (Write) and a variety of other >> Activities that cover a broad array of common functions. >> >> 3) We act as a host for AbiWord L10n, which would contribute some good >> word processor strings that might be leveraged by other efforts. >> >> 4) Sugar Labs has some pretty extensive efforts going in languages >> that are otherwise not well-represented in L10n. Indigenous languages >> of South and Central America represents an area of strength due to the >> large OLPC deployments in those regions. These efforts are being >> match with efforts to create and upstream glibc locales for these >> languages, which might lead to broader L10n efforts in upstream >> projects. > > > This would help a few people working on new languages in Pootle instances > across projects.
Yes, we actively encourage migration upstream to work on the GNOME strings we use in our stack (to localize the GNOME dual-boot on XO laptops), assisted by GNOME providing us with our own "release set" that tracks the bits we use as a downstream: https://l10n.gnome.org/releases/olpc/ Sugar is the "first localized" software for a number of languages and while it is a very long game strategy, I think that learning on a localized FOSS environment will eventually increase interest in further L10n as those kids grow up to be FOSS contributors :-) >> >> 5) A fair number of our localizers work off-line, and I encourage them >> to use Virtaal at every opportunity. Having our strings in Amagamma >> would help with consistency. >> >> I'd need to double-check with our L10n community to see how they feel >> about it, but our strings are almost all GPL'ed (2 or 3), and I think >> most of our localizers would be excited about contributing their Sugar >> strings to a broader translation memory effort like Amagamma. > > > That would be cool, the issue of licensing comes up now and again around the > topics of TM, but that's for a debate elsewhere :) The Sugar UI is all FOSS (We're a member project of the Software Freedom Conservancy), and the OLPC stack is FOSS all the way down to the firmware. There is some pesky proprietary microcode in the WiFi card that RMS makes a fuss about, but it is nothing for localizers to be concerned about. >> >> So what is involved in contributing our collected strings into the >> Amagamma pool? I'm hoping to get us upgraded to a 2.5 instance in the >> near future if that would smooth the submission process. > > > Apart from time it is mostly us adapting import scripts and rebuild the DB > to include OLPC translations. > Let me do some outreach to my stakeholders (Sugar and AbiWord localizers, Suagr Labs Oversight Board, etc.) to make sure everyone is on board with the idea and at some point in the future we can work on defining a contribution process from Sugar Labs to Amagamma. cjl ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
