Dne 6.8.2013 13:05, Karl Eichwalder napsal(a):
1/ ",ycp-format" flags are missing. This means we no longer are able to validate proper usage of format specifiers.
Ouch, this is quite tricky. We switched from YCP to Ruby so the "ycp-format" is actually not true anymore. Although we wrap the translation code so the YCP %<num> format specifiers work in Ruby code, we cannot know if that wrapper is used during POT build. It can be manually removed and replaced by pure Ruby format. (Well, maybe we could, but the parser would be too complicated and I don't think we would catch all possible use cases...) I don't want to blindly add "ycp-format" marks everywhere although it would work right now as nobody probably has touched any translation text yet. But later there will be such changes for sure and then we won't know which format is correct. I don't see any solution to this problem, I think we have just to live without the additional validation... :-(
2/ The extractor does not seem to collapse duplicates into one entry. Thus nfs_server.pot is invalid:
msgfmt --check 50-pot/nfs_server.pot 50-pot/nfs_server.pot:122: duplicate message definition... 50-pot/nfs_server.pot:119: ...this is the location of the first definition
Strange, there is some code for merging the duplicates and works quite well, it merged all duplicates correctly in my test cases. I'll check creating this specific POT file... Thanks for the feedback! Ladislav -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org