First of all, I would like to thank the people who sent feedback about
locale-inspector.
I have implemented your requests:
-better %s handling. Now things like %1$s are parsed properly.
-untranslated strings report (disabled by default).
-xml markup test.
-less false positives.
to enable untranslated test, edit your ini file:
[untranslated]
enabled=true
and to disable markup test:
[markup]
enabled=false
updated demo:
http://downloads.mozdev.org/br/l10n-report.zip
(accesskey test disabled for gu-IN, he, ja, ja-JP-mac, ko, pa-IN,
zh-CN and zh-TW locales)
download:
http://downloads.mozdev.org/br/locale-inspector.zip
--
Jeferson
tsahi
ציטוט Jeferson Hultmann:
--
Tsahi Asher
Hebrew L10n Team
http://www.mozilla.org.il
Hello,
In my opinion, command line interfaces are very useful for automatizing
tasks. I would like to thank Jeferson for this application. This is
going to be a great help for improving the quality of our translations.
GUI may be made a posteriori and, maybe it's not of my business, but I
would suggest Tsashi to help Jeferson in order to build such a GUI.
Best regards,
--
* Toni Hermoso Pulido
------------------------------------------------------
web: http://drac.homelinux.org
email: ton...@softcatala.org
gpg: B67B43DC
planet: http://planeta.softcatala.org
------------------------------------------------------
I worry about my child and the Internet all the time, even though she's
too young to have logged on yet. Here's what I worry about. I worry that
10 or 15 years from now, she will come to me and say 'Daddy, where were
you when they took freedom of the press away from the Internet?'
--Mike Godwin, Electronic Frontier Foundation
------------------------------------------------------
Thank you for this great tool.
Because of using MozillaTranslator in the past, we have some problems in
l10n process by using other tools now:
1) MT escaped all ":" > "\:"
Maybe a future locale-inspector release could check for these
(unnecessary) backslahes
2) We've many files including doubled backslashes "\\\\\". In some cases
these causes problems ("\\n" in properties does not produce a correct
line break).
Maybe a future locale-inspector release could check for doubled
backslashes "\\"
3) Sometimes we're using the UniPad text editor. UniPad escapes
backslashes in properties files. So we get false escaped escapes in
files ("\u005c:" instead of "\:" - this is related to the point 1).
Maybe a future locale-inspector release could check for "\u005c" (the
escaped code for a backslash, which never has to occur).
Regards
- --
Alexander Ihrig
- ------------------------------------------------------------------
Thunderbird Mail DE: http://www.thunderbird-mail.de
Enigmail DE: http://enigmail.thunderbird-mail.de/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
iD8DBQFDKsRYXTU1v1PSzx0RAp1tAJ0V4Bf93XZkn6VxGqwTSPFV+kGfngCfcuf6
6LP1A1zgjmMlPWwslefX9AY=
=Q0S1
-----END PGP SIGNATURE-----
Why don't you just build a GUI on top of the commandline. That is very
easy in C, too. And everyone can use what he prefers. :-)
Morty
> -better %s handling. Now things like %1$s are parsed properly.
Now I'm getting errors about the order of these C-format expressions.
Rearranging the order of the strings sometimes makes more sense in the
native language -- so the order shouldn't be an error.
> -untranslated strings report (disabled by default).
I enabled it as you said in your message, but funny I didn't get a
single untranslated string report.
--
Novica
Novica Nakov escreveu:
>> -better %s handling. Now things like %1$s are parsed properly.
>
>
> Now I'm getting errors about the order of these C-format expressions.
> Rearranging the order of the strings sometimes makes more sense in the
> native language -- so the order shouldn't be an error.
are you referring to this message? (mk locale)
ORIGINAL: %S Downloading message header %lu of %lu
LOCALIZED: Преземам %lu од %lu заглавја на пораки од %S
As far as I known, the localized string is wrong (you are formatting
a string as a long and a long as a string).
it should be:
Преземам %3$lu од %2$lu заглавја на пораки од %1$S
or
Преземам %2$lu од %3$lu заглавја на пораки од %1$S
See:
http://groups.google.com/group/netscape.public.mozilla.l10n/msg/9595e17b020e1c42
>> -untranslated strings report (disabled by default).
>
>
> I enabled it as you said in your message, but funny I didn't get a
> single untranslated string report.
strange. Are you using mono?
--
Jeferson
Tsahi Asher escreveu:
> it's very easy to write GUI in C#. why do you use a command line
> interface, with all that ini file stuff?
>
It's much easier don't write a GUI. :-) I don't think it's worth the
effort to write code to edit and save config options.
--
Jeferson
Alexander Ihrig escreveu:
> Because of using MozillaTranslator in the past, we have some problems in
> l10n process by using other tools now:
>
> 1) MT escaped all ":" > "\:"
>
> Maybe a future locale-inspector release could check for these
> (unnecessary) backslahes
looks like all you need is to use the locale-inspector's "merge" feature.
I translate using MT, export as a jar, unzip to a draft folder, run
locale-inspector and get totally clean files. :-)
[module mail]
original=path/to/en-US <-- "template" locale
translated=path/to/ab-CD <-- put translated files here
merge=path/to/cvs/folder <-- files created by locale-inpector
locale-inspector is smart enough to not overwrite files that don't
changed.
However, I can add an option to check redundant backslahes if you
really need it.
>
> 2) We've many files including doubled backslashes "\\\\\". In some cases
> these causes problems ("\\n" in properties does not produce a correct
> line break).
>
> Maybe a future locale-inspector release could check for doubled
> backslashes "\\"
the problem here is the code dont't have a way to known if the string
you want is a line break or the text "\n". :-\
>
> 3) Sometimes we're using the UniPad text editor. UniPad escapes
> backslashes in properties files. So we get false escaped escapes in
> files ("\u005c:" instead of "\:" - this is related to the point 1).
>
> Maybe a future locale-inspector release could check for "\u005c" (the
> escaped code for a backslash, which never has to occur).
I think it's can be done. Is it suitable to extend it to check for
all "\uXXXX" where XXXX < 128?
--
Jeferson
it's not very easy in C, but in C# (and a decent IDE, like visual studio
or SharpDevelop) it can be done in less than an hour, and probably
another hour to wire the UI to the existing functionality (but i haven't
seen the code yet, so it might be longer).
i have my own work to do, so i'll leave that to whoever is interested.
> See:
> http://groups.google.com/group/netscape.public.mozilla.l10n/msg/9595e17b020e1c42
I don't quite understand what's going on with this, but I'll fix it as
you say.
> strange. Are you using mono?
Yes. I don't get any errors though.
--
Novica
"\n" should never occur as a text. It's always meant as a line break.
--Abdulkadir Topal
An extension could need to show a text like:
"Type '\n' to create a new line."
file.properties:
label=Type \'\\n\' to create a new line.
--
Jeferson
Is it easy to write cross-platform GUI in c#?
command-line UI is crossplatform.
--
дамјан
The best things in life are free, but the
expensive ones are still worth a look.
Sure, but you have to admit, that's a lot less likely than the
accidental breaking, that really occurs, if you happen to use the
"wrong" editor ;)
--Abdulkadir
besides, despite it's claim, i don't consider .NET to be cross platform.
if it were, MS should have created the versions for non-Windows by
itself. if you want real cross platform, use Java.
I think I found a way to check these undesirable escapes. I compare
how many '\' chars original and localized texts have (after decoding).
btw, a lot of locales have properties files saved as utf-8. Looks
like utf-8 works, anyway. :-) locale-inspector will help localizers
find invalid properties files.
--
Jeferson
I'd like to have a function to list ALL comandkeys. This would be
helpfull to check the comandkeys and to create a help document with all
these keys.
Regards
- --
Alexander Ihrig
- ------------------------------------------------------------------
Thunderbird Mail DE: http://www.thunderbird-mail.de
Enigmail DE: http://enigmail.thunderbird-mail.de/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
iD8DBQFDRYybXTU1v1PSzx0RAlbpAJ9Y0F76nYhFvvu5YAXbraMjkpZnLACfUkZq
ZPllP+w963syFrFdFwR9nnM=
=NVxx
-----END PGP SIGNATURE-----
It's a great idea. But what would the output look like?