From: Andrew Dunbar (hippietrail@yahoo.com)
Date: Thu Oct 24 2002 - 23:23:23 EDT
--- Raphael Finkel <raphael@cs.uky.edu> wrote:
> 1. I have built a po file for Yiddish; it can be
> found at
> http://www.cs.uky.edu/~raphael/private/yi-YI.po .
>
> 2. Could whoever takes these things please do so
> and install it whereever these things go?
>
> 3. I had some problems that I mostly worked around
> by just eliminating a few entries in yi-YI that were
> marked "fuzzy", but these problems recur whenever I
> do
>
> ./update.pl yi-YI
>
> 4. Could someone give me a clear picture of what
> the following do and in what order one ought to
> invoke them when I want to (1) check for newly
> defined strings that need translation, (2) modify my
> idea of a good translation for existing things?
>
> update.pl yi-YI
> ui-backport.pl yi-YI
> update.pl --pot
> abi-extract.pl -N yi-YI
>
> 5. In fact, when I run AbiWord, I get lots of
> warnings about missing translations, such as
>
> DEBUG: WARNING: Translation for id
> [STYLE_NUMBER_LIST] not found.
>
> 5. I chose yi-YI as the name out of general
> ignorance of how the name ought to be chosen; I am
> happy to change to anything people want. What I
> mean by this name is "Yiddish in the YIVO
> orthography". YIVO is as close to a standards-
> setting organization as we have in the Yiddish
> community.
Hi Raphael. I'm a big fan of this work you've been
doing. My firm advice is to make all of your Yiddish
locales just "yi" with no country code. YI isn't a
legal ISO country code and we can't just make up our
own since ISO can add new codes as they please and
we'll end up clashing.
When the language code RFE gets sorted out, we'll have
a way to add the YIVO tag in a new and better way
which won't cause problems with ISO.
Until then if you can find places in some of the files
to place a comment that the files are YIVO, that would
be very good.
> 6. This week I get a new problem when I try my
> Yiddish strings; it didn't
> happen last week: seg fault (I am using
> Linux/gtk2.0) right after a failed
> assertion at src/af/ev/unix/ev_UnixMenu.cpp:647
> (UT_ASSERT(bResult)). (I
> always pipe "yes" into AbiWord to get past failed
> assertions; most don't kill
> AbiWord.) There was a previous failed assertion at
> 814 in the same file.
>
> 7. In src/wp/ap/unix/ap_UnixPrefs.cpp I am still
> using my own workaround in
> line 90 disabling the #if defined:
>
> #if defined (LC_MESSAGES) && defined (UNDEF)
>
> because no matter how I stand on my head, I cannot
> prevent setlocale() from
> returning "C" as the locale. My locale libraries
> just refuse to accept
> yi-YI.utf8 as a valid locale. Should I submit a bug
> report on that?
I know little of this field but Unicode tells us to
*always* write UTF-8 in uppercase and always with the
hyphen. So try "yi-YI.UTF-8" or just "yi.UTF-8" once
you have fixed the language code.
Good luck. Andrew.
=====
http://linguaphile.sourceforge.net/cgi-bin/translator.pl http://www.abisource.com
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
This archive was generated by hypermail 2.1.4 : Thu Oct 24 2002 - 23:31:07 EDT