unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Sun Yijiang <sunyijiang@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Problem with chinese gbk fonts on w32
Date: Mon, 1 Aug 2005 16:38:15 +0800	[thread overview]
Message-ID: <5065e29005080101382635f42d@mail.gmail.com> (raw)
In-Reply-To: <ubr4idthf.fsf@jasonrumney.net>


[-- Attachment #1.1: Type: text/plain, Size: 1926 bytes --]

Sorry, I've reviewed my .emacs and found where the problem is. The
problem is NOT mule-gbk, it's "create-fontset-from-fontset-spec".
Following setting results in double-width Chinese characters:

(create-fontset-from-fontset-spec
"-*-bitstream vera sans mono-normal-r-*-*-14-*-*-*-c-*-fontset-gbk,
chinese-gb2312:-*-simsun-normal-r-normal-*-16-*-*-p-*-gb2312*-*,
chinese-cns11643-5:-*-simsun-normal-r-normal-*-16-*-*-p-*-gbk*-*,
chinese-cns11643-6:-*-simsun-normal-r-normal-*-16-*-*-p-*-gbk*-*,
chinese-cns11643-7:-*-simsun-normal-r-normal-*-16-*-*-p-*-gbk*-*" t)

I think the problem is that I set different fonts for each char set. If
I comment out this setting and still use mule-gbk, Chinese characters
looks OK. If I use this setting, the Chinese characters looks
double-width, either with or without mule-gbk. This setting works for
previous CVS Emacs builds and seems to become "bad" recently.

I remember this problem first appeared with a check in of w32bdf.c
early this year. The problem can be resolved by rolling back w32bdf.c
to revision 1.20 at that time. But now even this rolling back does not
work, maybe other changes affects this problem.


2005/8/1, Jason Rumney <jasonr@gnu.org>:
> 
> Sun Yijiang <sunyijiang@gmail.com> writes:
> 
> > I think this change is probably not fully tested. When I use the
> > mule-gbk package and set font for chinese characters, they look so
> > wide, but when I use "emacs -q" they look nice, make no difference
> > with previous CVS Emacs. I roll back the src/w32bdf.c to older
> > version, and everything is OK. I think the change of w32bdf.c should
> > be reviewed, since this is really a bug.
> 
> You seem to be saying that you only see the "bug" when you load
> mule-gbk, which is not part of Emacs. What does mule-gbk do? Does it
> perhaps try to work around the previous bug by doubling the width of
> Chinese characters?
> 
>

[-- Attachment #1.2: Type: text/html, Size: 2363 bytes --]

[-- Attachment #2: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

  reply	other threads:[~2005-08-01  8:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-01  2:31 Problem with chinese gbk fonts on w32 Sun Yijiang
2005-08-01  7:08 ` Jason Rumney
2005-08-01  8:38   ` Sun Yijiang [this message]
2005-09-06  7:43     ` Sun Yijiang
2005-09-06  8:00       ` Jason Rumney
2005-09-06  8:13         ` Sun Yijiang

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=5065e29005080101382635f42d@mail.gmail.com \
    --to=sunyijiang@gmail.com \
    --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).