Kaixo!
Li Thu, 20 Jul 2000 07:50:29 -0500,
David Faure <[EMAIL PROTECTED]> scr�jheut:
> You can apply this patch to kdebase:
>
> --- kdebase-1.1.2/konsole/src/main.C.srtxg Thu Jul 13 20:22:40 2000
> +++ kdebase-1.1.2/konsole/src/main.C Thu Jul 13 21:02:28 2000
> @@ -81,8 +81,14 @@
>
> #define WITH_VGA
>
> -char *fonts[] = {"6x13", "5x7", "6x10", "7x13", "9x15", "10x20",
> - "linux8x16", "linux8x8" };
> +char *fonts[] = {"6x13,*-medium-r-*-13-*-c-*,*-fixed-*,*-m-*",
> + "5x7,*-medium-r-*-7-*-c-*,*-fixed-*,*-m-*",
> + "6x10,*-medium-r-*-10-*-c-*,*-fixed-*,*-m-*",
[etc]
DF> konsole in kde2 does
DF> const char *fonts[] = {
DF> "6x13", // FIXME: "fixed" used in favor of this
DF> "5x7", // tiny font, never used
DF> "6x10", // small font
DF> "7x13", // medium
DF> "9x15", // large
DF> "10x20", // huge
DF> "-misc-console-medium-r-normal--16-160-72-72-c-160-iso10646-1", // "Linux"
DF> "-misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1", // "Unicode"
DF> };
DF> Do you think the first 6 ones should be fixed the same way ?
In fact konsole forces the use of fixed fonts, hard compiled in.
That is, imho, a very bad design (If one of such fonts is missing for
whatever reaseon (eg: it looks crappy, I replaced it with a nicer one)
then the program will crash).
With KDE1 (that is, Qt1) the support of locales was also very limited (only
a very small subset of languages were supported) so a patch was applied
were font resolution was delegated to X11.
That means fontsets are used and X11 will search on the given fontset
a font matching the right encoding depending on the locale.
Impossible to do with font names as "6x13" -> no usable font -> crash.
Does KDE2 (that is, QT1) works with Japanese, Korean, Chinese, Vietnamese,
Armenian, etc locales ?
If yes, then konsole can be left using latin1 only fonts (however, that
may be a bad thing for people using other languages though, an error
message in Greek is not very readable when written in latin1 gibberish.
If it is possible to choose the font in a dialog box (as it is the case
with gnome-terminal) then that isn't a problem. Otherwise the program is
still as bad for non latin1 users and should be changed too).
I haven't yet looked at QT2; but it seems that, while it still manages
all locales and charsets and fonts itself, it is at least much more modular,
allowing more easily to add the missing charsets.
Then, if that is true, we should only create those missing charset/locale
modules/codecs (do you have any pointer to some documentation on that ?)
DF> I think it works with non-latin1 fonts, though, given that there are
DF> non-latin-1 users. Just wondering.
>From the above quote it seems it doesn't work with non latin1
(unless for the unicode font)
The test is very easy to do:
RPM_INSTALL_LANG=all rpm -Uv --force rpm-*.rpm
echo -e "LANG=ru\nKDE_LANG=ru" > ~/.i18n (for example)
LC_ALL=pl KDE_LANG=pl konsole &
rpm --allfiles -ev dontexist (on the newly loaded konsole)
is the Polish text in latin2 ?
The error text showed is:
rpm: --allfiles mo�na u�y� tylko w trakcie instalacji pakiet�w
^1 ^1^2 ^3
1: z with dot above
2: c with acute accent
3: o with acute accent
--
� bient�t,
Pablo Saratxaga PGP Key available, key ID: 0x8F0E4975
http://www.srtxg.easynet.be/
