From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: TUTORIAL.bg and windows-1251
Date: Thu, 8 Jan 2004 08:58:17 +0900 (JST) [thread overview]
Message-ID: <200401072358.IAA05239@etlken.m17n.org> (raw)
In-Reply-To: <3FFC3249.3010501@fmi.uni-sofia.bg> (message from Ognyan Kulev on Wed, 07 Jan 2004 18:22:33 +0200)
In article <3FFC3249.3010501@fmi.uni-sofia.bg>, Ognyan Kulev <ogi@fmi.uni-sofia.bg> writes:
>> By the way, for rendering, I installed the code I proposed a
>> while ago which forces *-microsoft-cp1251 fonts to be used
>> for Cyrillic letters of the charset mule-unicode-0100-24ff
>> in Bulgarian environment on 2003-12-29. Have you noticed
>> it?
> Wait! My report is exactly about that change not working. What you
> sent[1] in pure elisp works as expected though.
> [1] http://mail.gnu.org/archive/html/emacs-devel/2003-11/msg00452.html
??? I've thought that your bug report was about CTEXT
encoding in copy&paste, not about font because you wrote
something doesn't work before I install the change for font
selection.
So, do you mean that copy&paste has no problem now?
> When in current (2004-01-07) emacs I eval the following elisp (written
> by you), microsoft-cp1251 font is used for cyrillic characters. But
> just setting language environment to bulgarian doesn't work and
> iso10646-1 is used.
> (defun use-microsoft-cp1251-font ()
> (let ((fontspec '(nil . "microsoft-cp1251")))
> (map-char-table
> #'(lambda (k v)
> (if (and v (> k 128))
> (set-fontset-font "fontset-default" k fontspec)))
> (get 'encode-windows-1251 'translation-table))))
Please tell me what this returns:
(get-language-info "Bulgarian" 'overriding-fontspec)
and the effect of this.
(set-overriding-fontspec-internal
(get-language-info "Bulgarian" 'overriding-fontspec))
---
Ken'ichi HANDA
handa@m17n.org
next prev parent reply other threads:[~2004-01-07 23:58 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
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 [this message]
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=200401072358.IAA05239@etlken.m17n.org \
--to=handa@m17n.org \
--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).