Hi,
In my transition to UTF-8, I found that Gnome 1.2.x has a lot of files
in mixed encodings. All *.desktop files and .directory files are in
mixed encodings. Entries for [ja] are in EUC-JP, entries for [de] are
in ISO-8859-1/15 and entries for [ru] are in KOI8-R and so on. On the
other hand,
On Thu, May 02, 2002 at 09:51:44AM +0900, Gaspar Sinai wrote:
I am not much of an Emacs guy but if I were I would probably
use QEmacs, which looks pretty decent to me:
http://fabrice.bellard.free.fr/qemacs/
I had a quick look at qemacs a couple of weeks ago, for other reasons
(namely
Hi,
At Mon, 6 May 2002 07:46:33 +0200,
Pablo Saratxaga wrote:
In Hiragana/Katakana, processing of n is complex (though
it may be less complex than Hangul).
No. The N is just a kana like any other, no complexity at all involved.
Complexity only happens when typing in latin letters. That
On Mon, 6 May 2002, Pablo Saratxaga wrote:
On Mon, May 06, 2002 at 10:11:34AM +0900, Tomohiro KUBOTA wrote:
Note for xkb experts who don't know Hiragana/Katakana/Hangul:
input methods of these scripts need backtracking. For example,
in Hangul, imagine I hit keys in the c-v-c-v (c:
Hi,
At 02 May 2002 23:54:37 +1000,
Roger So wrote:
Note that the source from Li18nux will try to use its own encoding
conversion mechanisms on Linux, which is broken. You need to tell it to
use iconv instead.
I didn't know that because I am not a user of IIIMF nor other Li18nux
products.
On Sun, 2002-05-05 at 21:00, Tomohiro KUBOTA wrote:
At 02 May 2002 23:54:37 +1000,
Roger So wrote:
Note that the source from Li18nux will try to use its own encoding
conversion mechanisms on Linux, which is broken. You need to tell it to
use iconv instead.
I didn't know that because I
On Sun, 5 May 2002, Tomohiro KUBOTA wrote:
At 02 May 2002 23:54:37 +1000,
Roger So wrote:
I _do_ think xkb is sufficient for Japanese though, if you limit
Japanese to only hiragana and katagana. ;)
I believe that you are kidding to say about such a limitation.
Japanese language has
Hi,
At Sun, 5 May 2002 19:12:31 -0400 (EDT),
Jungshik Shin wrote:
I believe that you are kidding to say about such a limitation.
Japanese language has much less vowels and consonants than Korean,
which results in much more homonyms than Korean. Thus, I think
Well, actually it's due
Kaixo!
On Mon, May 06, 2002 at 10:11:34AM +0900, Tomohiro KUBOTA wrote:
Note for xkb experts who don't know Hiragana/Katakana/Hangul:
input methods of these scripts need backtracking. For example,
in Hangul, imagine I hit keys in the c-v-c-v (c: consonant,
v: vowel) sequence. When I hit
On Thu, May 02, 2002 at 02:03:06AM -0400, Jungshik Shin wrote:
I know very little about Win32 APIs, but according to what little
I learned from Mozilla source code, it doesn't seem to be so simple as
you wrote in Windows, either. Actually, my impression is that Windows
IME APIs are almost
Hi,
At Thu, 2 May 2002 02:14:29 -0400 (EDT),
Jungshik Shin wrote:
You mean IIIMF, didn't you? If there's any actual implementation,
I'd love to try it out. We need to have Windows 2k/XP or MacOS 9/X
style keyboard/IM switching mechanism/UI so that keyboard/IM modules
targeted
Markus Kuhn writes:
There is also bash/readline
SuSE 8.0 ships with a bash/readline that works fine with (at least)
width 1 characters in an UTF-8 locale.
There is also an alpha release of a readline version that attempts to
handle single-width, double-width and zero-width characters in all
On Thu, 2002-05-02 at 17:11, Tomohiro KUBOTA wrote:
There _is_ already an implementation of IIIMF. You can download
it from Li18nux site. However, I could not succeeded to try it.
Since I have heard several reports of IIIMF users, it is simply
my fault.
Note that the source from Li18nux
Bruno Haible wrote on 2002-05-02 12:23 UTC:
There is also an alpha release of a readline version that attempts to
handle single-width, double-width and zero-width characters in all
multibyte locales. But it's alpha (read: it doesn't work for me yet).
Yes, it seems the train is rolling now for
Markus Kuhn [EMAIL PROTECTED] writes:
c) Emacs - Current Emacs UTF-8 support is still a bit too provisional
for my comfort. In particular, I don't like that the UTF-8 mode is not
binary transparent. Work on turning Emcas completely into a UTF-8
editor is under way, and I'd
On Wed, 1 May 2002, Florian Weimer wrote:
Markus Kuhn [EMAIL PROTECTED] writes:
c) Emacs - Current Emacs UTF-8 support is still a bit too provisional
for my comfort. In particular, I don't like that the UTF-8 mode is not
binary transparent. Work on turning Emcas completely
Hi,
At Wed, 01 May 2002 20:02:57 +0100,
Markus Kuhn wrote:
I have for some time now been using UTF-8 more frequently than
ISO 8859-1. The three critical milestones that still keep me from
moving entirely to UTF-8 are
How about bash? Do you know any improvement?
Please note that tcsh have
On Thu, May 02, 2002 at 11:38:38AM +0900, Tomohiro KUBOTA wrote:
* input methods
Any way to input complex languages which cannot be supported
by xkb mechanism (i.e., CJK) ? XIM? IIIMP? (How about Gnome2?)
Or, any software-specific input methods (like Emacs or Yudit)?
How much
Hi,
At Thu, 2 May 2002 00:16:25 -0400,
Glenn Maynard wrote:
* input methods
Any way to input complex languages which cannot be supported
by xkb mechanism (i.e., CJK) ? XIM? IIIMP? (How about Gnome2?)
Or, any software-specific input methods (like Emacs or Yudit)?
How
On Thu, 2 May 2002, Glenn Maynard wrote:
On Thu, May 02, 2002 at 11:38:38AM +0900, Tomohiro KUBOTA wrote:
* input methods
Any way to input complex languages which cannot be supported
by xkb mechanism (i.e., CJK) ? XIM? IIIMP? (How about Gnome2?)
Or, any
On Thu, 2 May 2002, Tomohiro KUBOTA wrote:
At Wed, 01 May 2002 20:02:57 +0100,
Markus Kuhn wrote:
I have for some time now been using UTF-8 more frequently than
ISO 8859-1. The three critical milestones that still keep me from
moving entirely to UTF-8 are
How about bash? Do you
21 matches
Mail list logo
