On Fri, Apr 6, 2012 at 3:01 PM, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-04-06 09:03, Alexander Melentyev wrote:
Just an academic interest: what this checks are so needed for? What is actually checked? The only problem I face is that sometimes I forget to insert a trailing '\n' in the end of multiline message where original msgid has it. Any other issues you know?
There is one that might cause crashes: a %s more or less. If the source has an accelerator, the translated message must have it, too. Most of the checks are for looks of the text. Wrong xml tags can make the text be unreadable. kbabel also checks for "English text", which would warn you of forgotten strings. Another would be matching quotes, I think.
There are others that could be added, but the software don't support it: sometimes the messages has newlines, to make it fit into a box, but we have to guess what is that box size. This could be solved if the file added a token like
msgsize "------------------------"
and then the checker would verify that too. But this "msgsize" has not been invented yet, don't worry :-)
- -- Cheers / Saludos,
You can try Pology http://techbase.kde.org/Localization/Tools/Pology It has a lot of checks and has integration with Lokalize, so you can run Pology and make open the wrong files in Lokalize showing only the faulty strings. Bye -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org