Re: Croatian translation - finished - PO and nsh

Here you go,

now Slovenian po and nsh are in utf-8, as you requested. In nsh I also
changed to unix style endings and corrected the typo (into VB), just
didn't touch the Espanol thing you changed, please check that string
name ... In the po file I corrected a few errors and made some shortcuts
functional (non-duplicate).

Noticed a small bug - menu titles (like File, Edit, View, Insert ...) do
not display shortcut underline (like underlined letter F in File etc.).
Couldn't find it among bugs, but there are 200 bugs with shortcuts and
menus, so I rather didn't file it. Maybe it's already in there, although
with my quick browsing I didn't notice it.

And it's true, the "..." substrings are in some instances hardcoded,
which is bad for Slovenian, we should have an empty space (" ") between
the word preceeding it and the "...", that's our syntax rule. Hope the
"..." strings will land in the po file instead being hardcoded code,
someday ...

Thanks,
m.

J.M. Maurer pravi:
> On Wed, 2006-05-17 at 22:42 +0200, Martin Srebotnjak wrote:
>
>> Renato et. al.,
>>
>> actually, Slovenian po is in ISO-2 and works just fine that way.
>> Croatian had to be utf-8 because the script that produced it (.pl) from
>> .strings file encoded it that way. But it could also be converted into
>> ISO-2 with the changed po codepage flag.
>>
>> As far as I can remember the Slovenian NSIS file is encoded in win-1250
>> and that also works just fine.
>>
>> But it's true that the readme.txt file in any language not covered by
>> ASCII will have to be in utf-8. I just discovered that this morning. So,
>> as you can see, utf-8 codepage is only required for readme.txt for
>> non-western languages.
>>
>
> Just for consistency, I'd prefer all files to be utf-8.
>
> Bye!
> Marc
>
>
>