Hey Thanks for the work you've done on this, it looks good having all those languages translated!
A quick note - string #13 has two spaces before it which show up as [nsbn] or something - I presume this is from values in the strings.xml file. Apart from that, looks great! Steve 2010/5/14 Guillaume Rosaire <[email protected]> > > Well, I think I've commited this a bit early, it seems that each template > (.pot file) needs to be in its own directory with .po translations files > named after their iso code for Launchpad to import them, which was not how > android2po generated them... > > I'll look after this later. > > > 2010/5/14 Guillaume Rosaire <[email protected]> > > >> The locale folder has been created and populated in revision 148. >> >> From now on : >> Nobody modifies language specific strings.xml (same thing for >> arrays.xml) (I could have removed them from bazaar but that would have been >> not satisfying for people getting OSN sources without android2po installed), >> if modified by anyone, they will be overwritten. >> The only strings.xml file that may be updated is the default one, that's >> to say res/values/strings.xml >> Translation contributors will be able to work on the translations in the >> translate page of launchpad (in a few hours, once the .po files will have >> been imported by LP). Once a translation has been updated in any language, a >> new string.xml file for that language will be regenerated by android2po and >> commited back to bzr during the night. >> >> Regards, >> Guillaume >> >> >> >> >> 2010/5/13 Guillaume Rosaire <[email protected]> >> >>> >>> There are several ways of doing this, let me explain you how I see it >>> working to be sure everyone is happy with this. >>> >>> - on the main Opensatnav branch, a new directory will be created on the >>> project, a locale/ directory containing the template (strings-template.pot) >>> and every translations in gettext .po format (e.g. strings-fr.po) obtained >>> by running "android2po init" >>> - Launchpad will import these files after each commit to the branch and >>> enable contributors to work on them through the website. >>> - When contributors update translations, they will be commited back to >>> the branch by launchpad. >>> - The daily build script will do as follow : >>> if after a bzr update, it detects that the strings.xml file has >>> changed, it will run "a2po export" which will update .po files with the new >>> key or keys found in strings.xml and commit them back to the branch. >>> it will then do a "a2po import" that will regenerate all the >>> strings.xml with the content and commit them back to launchpad if changed. >>> >>> That way, that should work, language specific strings.xml will be updated >>> according to the .po translations, and when a new entry is made in the main >>> strings.xml, it will be mirrored to the .po files. >>> >>> >>> 2010/5/13 Guillaume Rosaire <[email protected]> >>> >>> >>>> I was not aware of Kieran's experimentation on the matter, I guess that >>>> would be easier that way :) >>>> >>>> >>>> >>>> 2010/5/13 steve brown <[email protected]> >>>> >>>> I believe this achieves something similar to what kieron was trying to >>>>> achieve with the xsl transformations. >>>>> S >>>>> >>>>> On May 13, 2010 4:49 PM, "Chris Andrew" <[email protected]> wrote: >>>>> >>>>> This sounds like a great idea; 'Work smarter, not harder'. Perhaps we >>>>> could set-up a test using a couple of non-English languages. >>>>> >>>>> Chris. >>>>> >>>>> >>>>> > >>>>> > On 13 May 2010 16:46, "Guillaume Rosaire" <[email protected]> wrote: >>>>> > >>>>> > >>>>> > Hi, >>>>> > >>>>> > I've just had... >>>>> >>>>> _______________________________________________ >>>>> Osn-dev mailing list >>>>> [email protected] >>>>> https://lists.kentgeek.org/mailman/listinfo/osn-dev >>>>> >>>>> >>>>> _______________________________________________ >>>>> Osn-dev mailing list >>>>> [email protected] >>>>> https://lists.kentgeek.org/mailman/listinfo/osn-dev >>>>> >>>>> >>>>> _______________________________________________ >>>>> Osn-dev mailing list >>>>> [email protected] >>>>> https://lists.kentgeek.org/mailman/listinfo/osn-dev >>>>> >>>>> >>>> >>> >> > > _______________________________________________ > Osn-dev mailing list > [email protected] > https://lists.kentgeek.org/mailman/listinfo/osn-dev > >
_______________________________________________ Osn-dev mailing list [email protected] https://lists.kentgeek.org/mailman/listinfo/osn-dev
