[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: some questions about translating KDE2
From:       Stephan Kulow <coolo () kde ! org>
Date:       1999-12-07 7:29:05
[Download RAW message or body]

Wolfram Diestel wrote:
> 
> Hello,
> 
> I temporarily hardcoded the charset of the fonts
> in kconfigbase.cpp but that didn't solve the problem,
> that the accented characters of Latin-3 doesn't
> appear correctly.
> 
> If I use an unicode font they appear as the Latin-1-equivalents,
> using a Latin-3 font I get question marks. So I suppose that
> the translations in the *.po files are always treated
> as Latin-1 when recoding with QString.fromLocal8Bit.
> Setting LC_CTYPE to eo or eo.iso-8859-3 doesn't help.
> 
> What I'm doing wrong?
> 
> With the qt/example/i18n example I can make translation
> files in either Latin-3 or UTF-8 and display this with
> both Latin-3 and Unicode fonts. All four combinations work
> fine, in KDE at the moment none of these work.
> 
> I think it's the best approach to use the charset given in
> the po-file header for recoding to QString, as Qt does with
> this i18n-example.
> When I have KDE_LANG=eo:de:C and LC_CTYPE=eo.UTF8 with
> an application only translated for german, what I will see?
> 
> May be I din't understand something important...
> 
Hmm, my belief is that the charset is taken from the charset
file installed. What I'm not too sure about is if it's taken
into account in any way. I really don't know. But as you say
I guess not.

LC_TYPE isn't recognized in any case by KDE.

Greetings, Stephan

-- 
When your memory goes, forget it!

[prev in list] [next in list] [prev in thread] [next in thread]