On 25 April 2013 07:39, Ankit Patel <an...@redhat.com> wrote: > On 04/24/2013 06:48 PM, Axel Hecht wrote: > > Hi, > > > > I wanted to chime in here as well. > > > > Last time I looked, the PO files can't make a difference between > > > > - localizer didn't look at the string - devtools in target language X > > should be in English - my preference window happens to be the same > > size as in english, and I want a space between menu items and access > > keys (the 'true' in intl.properties) > > > > That's at least how I recall the problem of exporting with missing > > strings. > > > > The question of interoperability and upstreaming changes made in > > DTDs and properties directly into pootle is a completely different > > one, of course. And it could be yet harder to fix. > > > > Axel > > > > Another issue came to my notice: > https://bugzilla.mozilla.org/show_bug.cgi?id=864308 >
Please start another thread if you want to raise another issue. > > Guys, we like Pootle but we need all these problems to be fixed to make > our translation life easier! > I'm glad you like Pootle. >From what I've seen one or two people on a team have chosen to translate directly in Mercurial while also being hosted on Pootle. In most cases we only commit to Mercurial if a team is active, so that probably means the team is translating on Pootle and someone has decided now to also translate on Mercurial. Since we only host anything on Pootle when requested to do so every team on the server has specifically requested to be hosted there either by themselves, Arky or Jeff. We don't load you if we weren't asked. On Pootle we have always made one request, if you are hosted on Pootle then please don't make changes in Mercurial. It has its advantages in that you don't need to do anything on Mercurial and neither does your team. I've still to hear from anyone who has raised this issue exactly why they have chosen to work directly on Mercurial and what advantage it gives them. Pootle will not always be for everyone, but it solves many massive problems we've faced in community localisation. But the few people who have raised this issue, really haven't given me a clear reason for their direct Mercurial approach. They also haven't given me a clear picture as to how this helps them foster a community of localisers. I'd love them to give me some concrete reasons, as then perhaps we can address the real issues that working directly is offering them. So I guess that is the first issue, working in both places. The second issues is to not put English into untranslated entries. Interestingly this is possible when working on .properties files we have not done it on DTD files. I'm reluctant to implement this for one reason that it will require quite extensive testing and invasive changes. So the risk to the 99% of teams who don't care is really big in terms of breakage. And to be honest such a change is of no value to them. So let me talk for the 99% This is a group who we aren't hearing. Who to honest probably don't even know what you guys are talking about. What Mercurial, direct what, English strings??? If they had a choice to implement features would they choose the two above? I can't speak for them but I suspect not. I'd really rather be focusing on making Pootle 100% better for community localisation and addressing issues that related directly to localisation. > Thanks > -- > Regards, > Ankit Patel > http://www.ankit644.com/ > > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr > _______________________________________________ > Translate-pootle mailing list > Translate-pootle@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/translate-pootle > -- Dwayne *Translate* +27 12 460 1095 ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _______________________________________________ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
