Subject: Re: bug #559 follow-up, need hints
From: Vlad Harchev (hvv@hippo.ru)
Date: Fri Jan 05 2001 - 03:59:06 CST
On Thu, 4 Jan 2001, Tamas Decsi wrote:
Hi Tamas,
> Hi Vlad,
>
> thanks for the hint. It worked, though - due to the fact that abiword
> recognizes hu-HU instead of the standard hu_HU - I had to rewrite it to
> hu-HU.ISO-8859-2
Hmm, do you mean that you had to set $LANG to hu-HU.ISO-8859-2 since
hu_HU.ISO-8859-2 didn't work? Very strange (I wonder why it works only the
first way). May be your are talking about localizing UI strings to hungarian?
I always use $LANG=ru_RU.KOI8-R to be able to input russian into it. Could you
please try $LANG=hu and tell whether it works? (Setting LANG to 'ru' works for
me for AW).
Are any special fonts needed for displaying Hungrarian (or the ones shipped
with AW work)?
> It may worth replacing all locale names along with the method to conform
Could you please explain what you mean by this in more detail?
> the standard, and then the _properly_ set locale will work, and bug #559
> can be closed.
>
> I will write up a short howto for hungarian users.
I think we should inspect why setting LANG to 'hu' doesn't work. If we
succeed inspecting, then no howto would be required IMO.
> All the best,
> Tamas
>
> On Thu, 4 Jan 2001, Vlad Harchev wrote:
>
> > Hi,
> >
> > I think locale is not configured properly - $LANG should be set to
> > hu_HU.ISO-8859-2 (of course if your system supports hungarian locale -
> > /usr/share/locale/{hu,hu_HU} should exist) - please try it and report
> > results. Anyway, it's a incorrect to use GdkEventKey->keyval - the right thing
> > is to use GdkEventKey->string.
> >
> > If setting LANG properly solves the problem, bug#559 should be closed.
> >
> > >
> > > Hello abi-dev,
> > >
> > > I couldn't stand and traced down the reason why abiword (unix) neglects
> > > some iso-8859-2 chars (eg. the 'nastiest' hungarian chars:
> > > o/O/u/U with double acute: charcodes 00f5, 00fb, 00d5, 00db).
> > >
> > > It turned out that in
> > > ev_UnixKeyboard::keyPressEvent()
> > > the passed
> > > GdkEventKey *e
> > > structure provides an empty string in
> > > e->string
> > > (at least) for the mentioned chars, while the
> > > e->charcode
> > > still gives the character code.
> > > Since that string is used as an input to ut_mbtowc (and then iconv), the
> > > whole thing results in an empty string, instead of those chars.
> > >
> > > My questions are:
> > >
> > > 1. this is not exactly bug #559, because the crash it notes did not happen.
> > > What should I do with this bug in bugzilla? (sorry, I've never used it
> > > before)
> > >
> > > 2. it turned out that the problem may be in gdk, and not in abi.
> > > I don't know much about gdk, so I need some hints:
> > >
> > > - Does gdk support iso-8859-2 encoding?
> > > - If yes, where it is told, that we use iso-8859-2 ?
> > > - If no, it seems to be abi's bug to use the GdkEventKey->string, and
> > > should be avoided somehow. Am I right?
> > >
> > > Any hints are welcome.
> > >
> > > Cheers,
> > > Tamas
> > >
> >
> > Best regards,
> > -Vlad
> >
>
Best regards,
-Vlad
This archive was generated by hypermail 2b25 : Fri Jan 05 2001 - 04:42:41 CST