2012/3/15 Dominik Waßenhoven <domw...@users.sourceforge.net>: > Am 14.03.2012 um 18:45 schrieb Morten Omholt Alver: > >> 2012/3/14 Morten Omholt Alver <mortenal...@gmail.com>: >>> 2012/3/14 Dominik Waßenhoven <domw...@users.sourceforge.net>: >>>> Am 13.03.2012 um 22:17 schrieb Morten Omholt Alver: >>>> >>>>> I'm trying to update the Norwegian translation, but I've found a lot >>>>> of lines with keys containing unescaped colons (:). These don't work. >>>>> Using Popeye, I translated a number of keys that I afterwards found >>>>> were already translated, but which didn't appear because of the >>>>> unescaped colons. >>>>> >>>>> Have anyone else had similar problems? I'm wondering if Popeye is >>>>> somehow the cause of these wrong keys… >>>> >>>> By the way, I just saw this entry: >>>> Add_a_(compiled)_custom_ImportFormat_class_from_a_class_path._nThe_path_need_not_be_on_the_classpath_of_JabRef. >>>> >>>> Shouldn’t it be “path._\nThe_path”? >>>> >>>> In further investigating, I saw that the above line is in >>>> JabRef_no.properties (twice; once with "n" and once with "\n"), whereas it >>>> is only once in JabRef_en.properties. Morten, did you add these lines with >>>> Popeye, or with another editor? In any case, there seem to be some double >>>> entries in the no.properties now. >>> >>> Hm... it seems that the syncLang tool doesn't do escaping of colons, >>> so perhaps all keys that are brough in using syncLang have this >>> problem. I'll fix this right away. >> >> I've changed syncLang, so it automatically escapes : and = when >> getting new keys from Java files. However, I don't think Popeye treats >> keys with escaped colons right. When I run it, it seems to add new >> wrongly formatted keys to the _no.properties file, even when the keys >> in the _en.properties file doesn't contain them. > > 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. Morten ------------------------------------------------------------------------------ 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
