locale-inspector, a tool to check locales
Jeferson Hultmann
I've made a command line tool to check locales. The
following items can be verified:
-bom
-entities
-placeholders (%S, #1, $var$ ...)
-access keys
-keybindings
The app also allows you to merge your locale into the en-US
one. So, you can create a valid translation in seconds (See
the "merge" line in ini file).
To illustrate, I've checked the 39 locales (mozilla1.8
branch): http://downloads.mozdev.org/br/l10n-report.zip
Download the application here:
http://downloads.mozdev.org/br/locale-inspector.zip
(It's a .NET app, so you'll need Windows and .NET framework
1.1. It's supposed to work with Mono but some extra coding
may be needed. Let me know if you are having any problems.)
check the INI files to config. And Please report the
grammar errors. :-)
--
Jeferson
Ville Pohjanheimo
> Hi Fellow Localizers,
>
> I've made a command line tool to check locales. The
> following items can be verified:
>
> -bom
> -entities
> -placeholders (%S, #1, $var$ ...)
> -access keys
> -keybindings
>
Brilliant! Seems to be an invaluable tool.
Thanks a bunch
-ville
--
yhteystiedot, contact info: http://ville.lucid.fi/
Hasse
Jeferson Hultmann wrote...
> Hi Fellow Localizers,
>
> I've made a command line tool to check locales. The
> following items can be verified:
>
> -bom
> -entities
> -placeholders (%S, #1, $var$ ...)
> -access keys
> -keybindings
>
> branch): http://downloads.mozdev.org/br/l10n-report.zip
Thank you for finding those mistakes in sv-SE!
--
Hasse
Mozilla sv-SE L10n team
Natsagdorj Shagdar
Thank you for the nice tool.
Best Regards
Natsagdorj Shagdar
Ahmet Serkan TIRATACI
This's a great tool that can let us see what our eyes can't easily see.
However, in some cases, it may not be possible to fix what is reported
by this tool. For example it says, for my language, "Yeniden dene" (Try
again) doesn't have "A" to be used as an access key and another letter
is used for that. As it's possible that I might not find another word or
expression for "Try again" that has "A" letter, it doesn't seem to be
meaningful as it's reported as an error. Of course, it gives us the
chance to rethink to find another suitable word/expression that has "A"
letter.
Thanks to those who worked to create this tool.
Serkan
BID Wen ShaoHua
really found a lot of mistakes!
maybe we should integrate this tool into the build process?
and one more thing from the result :
ERROR: different expression(s) at chrome\messenger\localMsgs.properties => 4026
ORIGINAL: Deleting %S of %S messages
LOCALIZED: 删除 %2$S 的 %1$S 个消息
I think that this kind of difference should be warning because we sometimes need to change the order of the variables.
So we are using %1$S instead of %S.
-----原始邮件-----
发件人: mozilla-l...@mozilla.org [mailto:mozilla-l...@mozilla.org]代表 Jeferson Hultmann
发送时间: 2005年9月6日 11:42
收件人: mozill...@mozilla.org
主题: locale-inspector, a tool to check locales
Hi Fellow Localizers,
I've made a command line tool to check locales. The
following items can be verified:
-bom
-entities
-placeholders (%S, #1, $var$ ...)
-access keys
-keybindings
The app also allows you to merge your locale into the en-US
one. So, you can create a valid translation in seconds (See
the "merge" line in ini file).
To illustrate, I've checked the 39 locales (mozilla1.8
branch): http://downloads.mozdev.org/br/l10n-report.zip
Download the application here:
http://downloads.mozdev.org/br/locale-inspector.zip
(It's a .NET app, so you'll need Windows and .NET framework
1.1. It's supposed to work with Mono but some extra coding
may be needed. Let me know if you are having any problems.)
check the INI files to config. And Please report the
grammar errors. :-)
--
Jeferson
_______________________________________________
mozilla-l10n mailing list
mozill...@mozilla.org
http://mail.mozilla.org/listinfo/mozilla-l10n
David Fraser
I would not recommend changing your translation to fit the access key,
rather use an appropriate access key and try and resolve access key
conflicts within your language if required...
David
Novica Nakov
> (It's a .NET app, so you'll need Windows and .NET framework
> 1.1. It's supposed to work with Mono but some extra coding
> may be needed. Let me know if you are having any problems.)
It seems it doesn't need any extra coding. I ran the exe with
mono-1.1.4 and it worked.
Thanks Jeferson. This a great tool.
--
Novica
Jeferson Hultmann
>
> and one more thing from the result :
> ERROR: different expression(s) at chrome\messenger\localMsgs.properties => 4026
> ORIGINAL: Deleting %S of %S messages
> LOCALIZED: 删除 %2$S 的 %1$S 个消息
> I think that this kind of difference should be warning because we sometimes need to change the order of the variables.
> So we are using %1$S instead of %S.
yes, it's a bug. :-| I'll try to fix it in the next version.
--
Jeferson
Jeferson Hultmann
> However, in some cases, it may not be possible to fix what is reported
> by this tool. For example it says, for my language, "Yeniden dene" (Try
> again) doesn't have "A" to be used as an access key and another letter
> is used for that. As it's possible that I might not find another word or
> expression for "Try again" that has "A" letter, it doesn't seem to be
> meaningful as it's reported as an error. Of course, it gives us the
> chance to rethink to find another suitable word/expression that has "A"
> letter.
You can disable tests you don't need. Insert into your ini file:
============8<---------------
[accesskey]
enabled=false
[keybinding]
enabled=false
[directories]
enabled=false
[files]
enabled=false
[bom]
enabled=false
;keys
[phrases]
enabled=false
;#1 %brand%
[placeholders]
enabled=false
;%s
[c-format]
enabled=false
[entities]
enabled=false
============8<---------------
--
Jeferson
Novica Nakov
> yes, it's a bug. :-| I'll try to fix it in the next version.
In the next version can you add an option to check which strings in the
locale are equal to the original from the en-US files?
I think this could be very useful.
--
Novica
Jeferson Hultmann
> In the next version can you add an option to check which strings in the
> locale are equal to the original from the en-US files?
>
Sure, what exactly do you need?
Should case, accesskeys, keybindings be ignored?
--
Jeferson
Andras Timar
> Hi Fellow Localizers,
>
> I've made a command line tool to check locales. The
> following items can be verified:
>
> -bom
> -entities
> -placeholders (%S, #1, $var$ ...)
> -access keys
> -keybindings
>
Excellent tool, thank you! I suggest that you also check inline HTML
tags in the entities. For example I got bug reports from users where the
bugs were caused by broken HTML tags in the translated
browser\chrome\overrides\netError.dtd
Best regards,
Andras
Novica Nakov
> Sure, what exactly do you need?
I want to be able to see how much strings in mk are same as in en-US, so
they are not translated, and where are they.I'm guessing that we have
50-100 strings for which suitable translation can't be found at the
moment, so I want to be able to keep track of them.
> Should case, accesskeys, keybindings be ignored?
I don't think it makes any difference. If it is easier to do it that
way, then they can be ignored.
Thanks Jeferson.
--
Novica