Referring to this post: today I tried building nn_NO from Rosetta without using revision numbers (project 3.1 and 3.1.x). I get an error message (“invalid revision”). That probably means that I have to look up revision numbers every time I want to build a new nn_NO release, which is a slight annoyance and a source of error. Why do I have to do it?
More seriously, the current nn_NO translations are broken, although all strings in translate.wordpress.org are translated. Scrutiny reveals that all strings the .po files in an update, and in a fresh download, are fully translated. The .mo files, on the other hand, contain only 828 translations. There is something wrong, and I can’t find out what. I’d be thankful if anyone would care to look at nn.wordpress.org. and examine the language files to confirm the problem, and find out how I get fully translated .mo files.
frilyd 8:54 am on May 24th, 2011 Permalink |
Further investigation: Building from dist file branch “trunk” gives wrong .mo files, while building from branch “tags/3.0” gives correct (or at least better) .mo files. I eagerly await the codex file about releasing localised builds. I thought I knew this, but now I am in doubt about what really is the correct procedure for releasing localised builds.
WordPress | Norsk (Nynorsk) » Nokre vanskar med WordPress-omsetjingane 8:59 am on May 24th, 2011 Permalink |
[…] i byggje- og utgjevingsmekanismane for WordPress, eller kanskje måten eg har brukt dei på – meir info her. Fleire andre språk har hatt liknande problem. For å freiste å rette på dette, har eg gjeve ut […]