A. Notice: \r escape sequence in pt.po
msgmerge pt.po tmw.pot -o pt.new.po
pt.po:796: internationalized messages should not contain the `\r' escape sequence
pt.po:803: internationalized messages should not contain the `\r' escape sequence
pt.po:810: internationalized messages should not contain the `\r' escape sequence
pt.po:817: internationalized messages should not contain the `\r' escape sequence
Code: Select all
msgid "Attack:" msgstr "" "Copy text \t\r\n" "Ataque %+d"
B. Question: Non valid C format strings in sv.po
Not sure how to work around this, I wasnÃƒÂ¢Ã¢â€šÂ¬Ã¢â€žÂ¢t able to escape the percentage sign. ÃƒÂ¢Ã¢â€šÂ¬Ã…â€œ% A...ÃƒÂ¢Ã¢â€šÂ¬Ã‚Â, ÃƒÂ¢Ã¢â€šÂ¬Ã…â€œ% E...ÃƒÂ¢Ã¢â€šÂ¬Ã‚Â and ÃƒÂ¢Ã¢â€šÂ¬Ã…â€œ% R...ÃƒÂ¢Ã¢â€šÂ¬Ã‚Â works, but for instance ÃƒÂ¢Ã¢â€šÂ¬Ã…â€œ% TÃƒÂ¢Ã¢â€šÂ¬Ã‚Â does not. Personally I would change the text from ÃƒÂ¢Ã¢â€šÂ¬Ã…â€œ% Accuracy: __ÃƒÂ¢Ã¢â€šÂ¬Ã‚Â to ÃƒÂ¢Ã¢â€šÂ¬Ã…â€œAccuracy: __ %ÃƒÂ¢Ã¢â€šÂ¬Ã‚Â, then this problem is solved, but IÃƒÂ¢Ã¢â€šÂ¬Ã¢â€žÂ¢m still curious how to enter a percentage sign in the gettext msgs.rm -f sv.gmo && /usr/bin/msgfmt -c --statistics -o sv.gmo sv.po
sv.po:808: 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the directive number 1, the character 'T' is not a valid conversion specifier.
sv.po:813: 'msgstr' is not a valid C format string, unlike 'msgid'. Reason: In the directive number 1, the character 'U' is not a valid conversion specifier.
/usr/bin/msgfmt: found 2 fatal errors
C. Strings not marked for translation
IÃƒÂ¢Ã¢â€šÂ¬Ã¢â€žÂ¢m willing to go through the source and enable gettext support for more strings (both the eAthena as the tmwserv client), if IÃƒÂ¢Ã¢â€šÂ¬Ã¢â€žÂ¢m ÃƒÂ¢Ã¢â€šÂ¬Ã‹Å“allowedÃƒÂ¢Ã¢â€šÂ¬Ã¢â€žÂ¢, a few questions:
- tmwserv: is the server messages translateable as of now?
- Error/log messages: the wiki says they shouldnÃƒÂ¢Ã¢â€šÂ¬Ã¢â€žÂ¢t be translated, personally I support translation of them; when English debug messages are needed they can be given with ÃƒÂ¢Ã¢â€šÂ¬Ã…â€œLANG=C tmwÃƒÂ¢Ã¢â€šÂ¬Ã‚Â or some such, and having them in your own language as a user can help quite much
- As of now some strings are translateable as ÃƒÂ¢Ã¢â€šÂ¬Ã…â€œLabel: %dÃƒÂ¢Ã¢â€šÂ¬Ã‚Â and others ÃƒÂ¢Ã¢â€šÂ¬Ã…â€œLabel:ÃƒÂ¢Ã¢â€šÂ¬Ã‚Â, which should be used? (I guess the first way could be mandatory for some languages in some cases, even if I cannot come up with any real scenario in my mind just now.)