From: Ognyan Kulev <ogi@fmi.uni-sofia.bg>
Cc: emacs-devel@gnu.org
Subject: Re: TUTORIAL.bg and windows-1251
Date: Wed, 31 Dec 2003 17:06:07 +0200 [thread overview]
Message-ID: <3FF2E5DF.4090906@fmi.uni-sofia.bg> (raw)
In-Reply-To: <200312042328.IAA06933@etlken.m17n.org>
Kenichi Handa wrote:
> In article <3FCF60C9.8060009@fmi.uni-sofia.bg>, Ognyan Kulev <ogi@fmi.uni-sofia.bg> writes:
>>Unfortunately, it doesn't work in Emacs[1]. (The ctext.el that you sent
>>me in previous mail works.) emacs is started with LANG=bg_BG. I'm
>>setting lang.env. to English and back to Bulgarian, but nothing helped.
>
> Please check the value of
> `ctext-non-standard-encodings-alist'. Does it contain an
> element something like:
> ("microsoft-cp1251" windows-1251 1 CHAR-TABLE)
> If not, please byte compile lisp/language/cyrillic.el and
> make Emacs again.
Today (2003-12-31) I've checked out emacs and tested it again.
Unfortunately, it doesn't work as expected -- microsoft-cp1251 font
encoding is not used.
ctext-non-standard-encodings-alist contains microsoft-cp1251.
I tried to understand the code, but without great success. So
ctext-pre-write-conversion seems the only place that uses
ctext-non-standard-encodings property of current language environment
(via ctext-non-standard-encodings-table). Do I understand it right that
somehow all rendering of text to X is done via the "special" compound
text (ctext) coding system, while buffer can be in other coding system?
If not, how this ctext coding system is used, and, consequently,
ctext-non-standard-encodings property? (I just try to help getting
this thing working.)
Regards
--
Ognyan Kulev <ogi@{fmi.uni-sofia.bg,fsa-bg.org,jabber.org}>
7D9F 66E6 68B7 A62B 0FCF EB04 80BF 3A8C A252 9782
next prev parent reply other threads:[~2003-12-31 15:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-14 18:56 TUTORIAL.bg and windows-1251 Ognyan Kulev
2003-11-15 12:19 ` Ognyan Kulev
2003-11-26 7:33 ` Ognyan Kulev
2003-11-15 14:24 ` Jason Rumney
2003-11-17 7:21 ` Kenichi Handa
2003-11-18 15:49 ` Ognyan Kulev
2003-11-24 23:55 ` Kenichi Handa
2003-11-26 7:16 ` Ognyan Kulev
2003-11-26 7:47 ` Kenichi Handa
2003-11-26 8:30 ` Ognyan Kulev
2003-11-26 13:17 ` Kenichi Handa
2003-11-26 14:08 ` Ognyan Kulev
2003-12-03 8:34 ` Kenichi Handa
2003-12-04 16:28 ` Ognyan Kulev
2003-12-04 23:28 ` Kenichi Handa
2003-12-31 15:06 ` Ognyan Kulev [this message]
2003-12-31 15:54 ` Eli Zaretskii
2004-01-05 4:20 ` Kenichi Handa
2004-01-05 4:14 ` Kenichi Handa
2004-01-06 12:03 ` YAMAMOTO Mitsuharu
2004-01-07 0:25 ` Kenichi Handa
2004-01-07 1:32 ` YAMAMOTO Mitsuharu
2004-01-07 16:22 ` Ognyan Kulev
2004-01-07 23:58 ` Kenichi Handa
2004-01-09 16:10 ` Ognyan Kulev
2004-01-13 4:07 ` Kenichi Handa
2004-01-14 11:42 ` Ognyan Kulev
2004-01-14 12:10 ` Kenichi Handa
2004-01-17 19:31 ` Ognyan Kulev
2004-01-19 0:34 ` Kenichi Handa
2004-01-21 6:45 ` Ognyan Kulev
2004-01-21 10:52 ` Kenichi Handa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FF2E5DF.4090906@fmi.uni-sofia.bg \
--to=ogi@fmi.uni-sofia.bg \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).