Am 15.03.2012 um 08:42 schrieb Morten Omholt Alver: > 2012/3/15 Dominik Waßenhoven <domw...@users.sourceforge.net>: >> Just to be clear on this: colons and equal signs have to be escaped in the >> key, but not in the translation, right? > > Yes, that's right. > >> At the moment, there seem to be only some inconsistencies with the >> _no.properties, but apart from this I can see no problems with Popeye (or I >> did not get it right at some point). > > What made me suspect Popeye was that I cleaned these wrong keys, and > then saw them come back after running Popeye. It may be these keys > came from the _en.properties file, even though I tried to clean up > that one as well.
I think you have to clean up every file, not only _en and _no. Take the following example from _en: Unsupported_version_of_class_%0\:_%1=Unsupported_version_of_class_%0:_%1 In _no, this is Unsupported_version_of_class_%0\:_%1=Ikke_st\u00f8ttet_versjon_av_klassen_%0:_%1 In _de, it is Unsupported_version_of_class_%0:_%1=Nicht_unterst\u00fctzte_Version_der_Klasse_%0:_%1 Here, the colon is not escaped, and thus Popeye finds different keys. The one found in _de (and presumably other translations, but I have not checked this) is considered as not translated in _no and _en, whereas the version with escaped colon is considered as not translated in the German version. Dominik.- ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Jabref-devel mailing list Jabref-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jabref-devel
