On 04/19/2013 02:07 PM, Krishnababu Krothapalli wrote: > Hi, > > In my opinion we should not fill untranslated entries with english > entries at upstream repo, instead we better to leave the <locale> > file with out corresponding entry. So that dashboard page will also > show the missing entries status for that local. > > Since we can only see the string count only under "unchanged" one > can't find the file location of the entry. > > As we know in .po file if any strings remained untranslated in the > current release then those will remained as untranslated for upcoming > releases till they get translated. > > Like that untranslated strings shouldn't have those entries in the > corresponding <locale> .dtd .properties files.
As a translator, I would keep messages untranslated, if I have no time to do it or the English message is complex enough to confuse me. But if it makes sense to keep the message in English itself, I would certainly copy n paste it to the translation space, e.g. trademarks, tags, etc. There's a difference here! Also, what if I would like to switch back to the traditional way of translating things directly in dtd/properties in hg repo? How would I find all messages I have not translated (but kept in English by pootle conversion as part of the process)? It shouldn't be that hard decision to have either Pootle or Mozilla hg? Thanks, Ankit > > > > On 04/18/2013 07:53 PM, Dwayne Bailey wrote: >> >> >> >> On 18 April 2013 10:30, Krishnababu Krothapalli >> <krisnab...@gmail.com <mailto:krisnab...@gmail.com>> wrote: >> >> Hi, >> >> I have noticed one thing that [1] pushing back untranslated strings >> as english strings to [2]. >> >> >> Correct, by design. >> >> >> Which means those entries/strings will remain in english in >> respective <locale> .dtd and .properties files and considered as >> translated, as a result of which those entries wont showed as >> missing/untranslated at [3]. >> >> >> But they will show up under unchanged on that page. >> >> On Pootle you can more readily see what is unchanged on purpose >> and what is translated, so you get a better picture from the stats >> on Pootle. >> >> >> I think while pushing back to upstream "hg repo" from "locamotion", >> untranslated strings shouldn't have those entries in respective >> <locale> . So that [3] compare script can show the status for those >> missing entries for the corresponding <locale>. This gives the >> freedom to the translator to work in his preferred ways, means >> either via locamotion or by direct "hg pull/push" or by both. >> >> >> If you are working on locamotion.org <http://locamotion.org> then >> you shouldn't be doing direct pushes yourself as it will likely >> cause collisions and takes a long time to correct. Rather fix >> strings in Pootle. >> >> >> Please correct me if i am missing anything! >> >> Thanks in advance! >> >> [1] http://mozilla.locamotion.org [2] >> http://hg.mozilla.org/releases/l10n/mozilla-aurora/te/ [3] >> https://l10n.mozilla.org/shipping/dashboard >> <https://l10n.mozilla.org/shipping/dashboard> >> >> -- Regards, Krishna. >> >> >> >> >> -- Dwayne >> >> *Translate* +27 12 460 1095 > -- Regards, Krishna. -- Regards, Ankit Patel http://www.ankit644.com/ ------------------------------------------------------------------------------ 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
