Mailinglist Archive: opensuse-m17n (69 mails)
| < Previous | Next > |
Re: [m17n] UTF-8 and Turkish
- From: Mike Fabian <mfabian@xxxxxxx>
- Date: Tue, 14 May 2002 11:01:47 +0000 (UTC)
- Message-id: <s3tbsbj2dt2.fsf@xxxxxxxxxxxxxxx>
Togan Muftuoglu <toganm@xxxxxxxxxxxx> writes:
>>In Emacs use
>> M-x set-keyboard-coding-system RET utf-8 RET
>>then it works. Add
>>
>> (set-keyboard-coding-system 'utf-8)
>>
>>to your ~/.emacs if you want to use that always. Or maybe, to do that
>>only when Emacs is started in a locale which uses UTF-8 charmap, you
>>may prefer:
>>
>> (when (string-match "UTF-8" (shell-command-to-string "locale charmap"))
>> (set-keyboard-coding-system 'utf-8))
>>
>> (when (string-match "UTF-8" (shell-command-to-string "locale charmap"))
>> (set-default-coding-systems 'utf-8))
>
> Ok this I added to my .gnu-emacs-custom, as I read ( or my
> interpretation ) during the creation of the user $HOME/.emacs and
> $HOME/.gnu-emacs are copied from /etc/skel directory.
Yes, if you use the default Emacs startup files from /etc/skel,
it is probably best to add you own setup to the end of ~/.gnu-emacs.
The SuSE default ~/.emacs contains
(setq custom-file "~/.gnu-emacs-custom")
(load "~/.gnu-emacs-custom" t t)
therefore ~/.gnu-emacs-custom will be used when you change settings in
Emacs with 'M-x customize' and choose 'Save for Future Sessions'.
Adding your onw extensions to ~/.gnu-emacs-custom works as well, but
the idea is to use ~/.gnu-emacs for setting up stuff by manually
adding lisp code and to use ~/.gnu-emacs-custom for the stuff saved
automatically by 'M-x customize'.
> When I start emacs yes I can type read save in utf-8 however I have some
> strange output on some of the keys in Capital form whether I use shift
> or CapsLock.
>
> <begin>
> # this part is written under Emacs
>
> The problematic keys are as follows:
>
> Udiaresis (Capital letter): prints out this ? and says Mark Set I
> have the same result when I use caps lock or Shift
>
> Scedilla (Capital letter): prints out Š same with caps lock and
> using shift
>
> Ccedilla (captial letter) I recive Invalid character message
> 05600,2944,0xb80
>
> Odiaresis (capital letter): I receive Invalid character message
> 0340000, 114688, 0x1c000
>
> </end>
Yes, I can reproduce this.
> I tried with replacing SuSE created .emacs and .gnu-emacs with renaming
> my .gnu-emacs-custom to .emacs but still the same problem
> happens. However when I type these same characters in an xterm
> environment
> created by "utf8xterm" under Vim ( that is what I use for Mutt's editor)
> here are the results
>
> Ü Ş Ç Ö , I can type these characters I can see them on my display and
> there are no error messages that are visible to me. Is this a bug with
> emacs or are there other customizations I have to tweak.
It appears to be a bug in Emacs.
I see the same problem with GNU Emacs 21.1.1 (which is the version
distributed with SuSE Linux 8.0) but it works correctly with GNU Emacs
21.2.50.1, which is a current CVS version of Emacs.
It also works already with the XEmacs version distributed with SuSE
Linux 8.0, i.e. you can use XEmacs instead of Emacs as a workaround.
In case of XEmacs, you add your personal setup like
(wh2en (string-match "UTF-8" (shell-command-to-string "locale charmap"))
(set-default-coding-systems 'utf-8))
to
~/.xemacs/init.el
I'll try whether I can find what change between GNU Emacs 21.1.1 and
GNU Emacs 21.2.50.1 fixed this bug.
--
Mike Fabian <mfabian@xxxxxxx> http://www.suse.de/~mfabian
睡眠不足はいい仕事の敵だ。
>>In Emacs use
>> M-x set-keyboard-coding-system RET utf-8 RET
>>then it works. Add
>>
>> (set-keyboard-coding-system 'utf-8)
>>
>>to your ~/.emacs if you want to use that always. Or maybe, to do that
>>only when Emacs is started in a locale which uses UTF-8 charmap, you
>>may prefer:
>>
>> (when (string-match "UTF-8" (shell-command-to-string "locale charmap"))
>> (set-keyboard-coding-system 'utf-8))
>>
>> (when (string-match "UTF-8" (shell-command-to-string "locale charmap"))
>> (set-default-coding-systems 'utf-8))
>
> Ok this I added to my .gnu-emacs-custom, as I read ( or my
> interpretation ) during the creation of the user $HOME/.emacs and
> $HOME/.gnu-emacs are copied from /etc/skel directory.
Yes, if you use the default Emacs startup files from /etc/skel,
it is probably best to add you own setup to the end of ~/.gnu-emacs.
The SuSE default ~/.emacs contains
(setq custom-file "~/.gnu-emacs-custom")
(load "~/.gnu-emacs-custom" t t)
therefore ~/.gnu-emacs-custom will be used when you change settings in
Emacs with 'M-x customize' and choose 'Save for Future Sessions'.
Adding your onw extensions to ~/.gnu-emacs-custom works as well, but
the idea is to use ~/.gnu-emacs for setting up stuff by manually
adding lisp code and to use ~/.gnu-emacs-custom for the stuff saved
automatically by 'M-x customize'.
> When I start emacs yes I can type read save in utf-8 however I have some
> strange output on some of the keys in Capital form whether I use shift
> or CapsLock.
>
> <begin>
> # this part is written under Emacs
>
> The problematic keys are as follows:
>
> Udiaresis (Capital letter): prints out this ? and says Mark Set I
> have the same result when I use caps lock or Shift
>
> Scedilla (Capital letter): prints out Š same with caps lock and
> using shift
>
> Ccedilla (captial letter) I recive Invalid character message
> 05600,2944,0xb80
>
> Odiaresis (capital letter): I receive Invalid character message
> 0340000, 114688, 0x1c000
>
> </end>
Yes, I can reproduce this.
> I tried with replacing SuSE created .emacs and .gnu-emacs with renaming
> my .gnu-emacs-custom to .emacs but still the same problem
> happens. However when I type these same characters in an xterm
> environment
> created by "utf8xterm" under Vim ( that is what I use for Mutt's editor)
> here are the results
>
> Ü Ş Ç Ö , I can type these characters I can see them on my display and
> there are no error messages that are visible to me. Is this a bug with
> emacs or are there other customizations I have to tweak.
It appears to be a bug in Emacs.
I see the same problem with GNU Emacs 21.1.1 (which is the version
distributed with SuSE Linux 8.0) but it works correctly with GNU Emacs
21.2.50.1, which is a current CVS version of Emacs.
It also works already with the XEmacs version distributed with SuSE
Linux 8.0, i.e. you can use XEmacs instead of Emacs as a workaround.
In case of XEmacs, you add your personal setup like
(wh2en (string-match "UTF-8" (shell-command-to-string "locale charmap"))
(set-default-coding-systems 'utf-8))
to
~/.xemacs/init.el
I'll try whether I can find what change between GNU Emacs 21.1.1 and
GNU Emacs 21.2.50.1 fixed this bug.
--
Mike Fabian <mfabian@xxxxxxx> http://www.suse.de/~mfabian
睡眠不足はいい仕事の敵だ。
| < Previous | Next > |