unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: tumashu <tumashu@163.com>
To: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Any new method to deal with Emacs Fonts settings puzzles nearly every Chinese emacser?
Date: Sat, 13 Nov 2021 22:36:11 +0800 (CST)	[thread overview]
Message-ID: <2c676019.21d2.17d19ba2dc8.Coremail.tumashu@163.com> (raw)


Hello everyone:



   (1)    How to let A Chinese char width = 2 * Ascii char width is an eternal topic for Chinese new emacser.


it let all Chinese new users and many old users puzzle a lot, that is the reason my cnfonts package (a Chinese fonts setup utils) get >600 github star.
recent day, we talk about Emacs fonts, so I want to know, is it possible provide a feature in emacs core to solve this problem?
The way cnfonts provide just a hack way I think. https://github.com/tumashu/cnfonts



The two question is that: How to force set min line-width to a value?  Chinese emaser use will use two fonts generally, a Ascii fonts and A Chinese fonts.
Two fonts will use different height to let 1 Chinese Char width = 2 * Ascii char width,  but this set will get other problem:


     (2)                     Chinese char Height > Ascii char height,


The results is that head-line, mode-line and minibuffer's height will shark (change frequently depend Chinese char exist or not).
it looks very very ugly.


These two questions make Chinese Emacs new users feel that Emacs is particularly low !!!


Thanks!













             reply	other threads:[~2021-11-13 14:36 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-13 14:36 tumashu [this message]
2021-11-13 14:49 ` Re:Any new method to deal with Emacs Fonts settings puzzles nearly every Chinese emacser? tumashu
2021-11-13 15:03   ` tumashu
2021-11-13 15:32     ` Any " Eli Zaretskii
2021-11-13 16:19       ` Feng Shu
2021-11-13 16:42         ` Eli Zaretskii
2021-11-13 19:35           ` Feng Shu
2021-11-13 20:03             ` Eli Zaretskii
2021-11-13 23:38               ` Feng Shu
2021-11-14  0:28                 ` Eric Abrahamsen
2021-11-14  7:37                   ` Eli Zaretskii
2021-11-14  7:51                     ` Po Lu
2021-11-14  9:07                       ` Werner LEMBERG
2021-11-14  9:38                         ` Po Lu
2021-11-15  7:20                           ` Byung-Hee HWANG
2021-11-14  7:31                 ` Eli Zaretskii
2021-11-14  7:36                   ` Po Lu
2021-11-14  8:09                     ` Eli Zaretskii
2021-11-14  8:24                       ` Feng Shu
2021-11-14  9:41                       ` Po Lu
2021-11-14 11:33                         ` Eli Zaretskii
2021-11-14 11:57                           ` Po Lu
2021-11-15  0:36                       ` tumashu
2021-11-15  0:48                       ` tumashu
2021-11-15 12:43                         ` Eli Zaretskii
2021-11-15 12:47                           ` Po Lu
2021-11-15 13:55                             ` Eli Zaretskii
2021-11-13 15:21 ` Eli Zaretskii
2021-11-13 16:04   ` Feng Shu
2021-11-13 16:12   ` Feng Shu
2021-11-13 16:36     ` Eli Zaretskii
2021-11-13 19:33       ` Feng Shu
2021-11-13 19:54         ` Feng Shu
2021-11-13 20:06           ` Eli Zaretskii
2021-11-13 23:31             ` Feng Shu
2021-11-14  6:48               ` Eli Zaretskii
2021-11-14  7:03                 ` Feng Shu
2021-11-13 20:02         ` Eli Zaretskii
2021-11-13 23:29           ` Feng Shu
2021-11-13 23:14   ` Phil Sainty
2021-11-14  0:02     ` Feng Shu
2021-11-14  0:18       ` Feng Shu
2021-11-14  7:36         ` Eli Zaretskii
2021-11-14  7:54           ` Po Lu
2021-11-14  8:14             ` Eli Zaretskii
2021-11-14  9:43               ` Po Lu
2021-11-14  6:45     ` Eli Zaretskii
2021-11-14  7:17       ` Feng Shu
2021-11-14  8:00         ` Eli Zaretskii
2021-11-14  1:12   ` Po Lu
2021-11-14  1:52     ` Feng Shu
2021-11-14  7:55     ` Eli Zaretskii

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=2c676019.21d2.17d19ba2dc8.Coremail.tumashu@163.com \
    --to=tumashu@163.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).