all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Display certain glyphs with paddings on the side
Date: Tue, 3 Dec 2019 15:00:19 -0500	[thread overview]
Message-ID: <cbcc7ff7-6af3-c5f9-5249-4ae59933347f@gmail.com> (raw)
In-Reply-To: <83a789jk8c.fsf@gnu.org>

On 2019-12-03 14:13, Eli Zaretskii wrote:
>> Cc: emacs-devel@gnu.org
>> From: Clément Pit-Claudel <cpitclaudel@gmail.com>
>> Date: Tue, 3 Dec 2019 13:43:33 -0500
>>
>>> No, character composition does nothing to the width of glyphs on
>>> display.  We take the width from the glyph metrics reported by the
>>> font.
>>
>> For the OP's purpose, I think character composition is "enough", in the sense that it can be used to display a glyphs with padding on the sides (as far as I know, composition can't be used to shrink a glyph, however).
>>
>> Concretely, I'm think of this:
>>
>>   (insert (compose-string "a" 0 1 '(?\s (br . bl) ?\s (bc . bc) ?我)))
>>
>> If I'm reading the spec correctly, this should draw the character 我 with padding on both sides to reach the width of two spaces (assuming the choice of fonts is such as 我 is narrower than two spaces to being with).
> 
> This isn't really workable in practice. 

Sorry, my point wasn't that the OP should do that; rather, I was pointing out that the display engine was powerful enough to achieve the desired result.

Ideally, what I'd love to have is a mode that implements a grid-like layout, where each character occupies an exact multiple of the base character width, regardless of which font it comes from.

Deciding what this multiple should be for each character could be done in various ways; for my purposes (and for OP's case as well, I think), it would be enough to use one cell for halfwidth characters, two for fullwidth characters, and add a few exceptions for things like TAB and zero-width spaces (I'm using the terms fullwidth and halfwidth in the sense of https://www.unicode.org/reports/tr11/).

Should I open a bug report about this?

Cheers,
Clément.



  reply	other threads:[~2019-12-03 20:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-30 19:51 Display certain glyphs with paddings on the side Yuan Fu
2019-12-02 16:24 ` Eli Zaretskii
2019-12-03  4:56   ` Richard Stallman
2019-12-03 15:43     ` Eli Zaretskii
2019-12-03 15:49       ` Yuan Fu
2019-12-03 16:42   ` Clément Pit-Claudel
2019-12-03 17:38     ` Eli Zaretskii
2019-12-03 18:36       ` Yuri Khan
2019-12-03 18:42         ` Eli Zaretskii
2019-12-03 18:43       ` Clément Pit-Claudel
2019-12-03 19:13         ` Eli Zaretskii
2019-12-03 20:00           ` Clément Pit-Claudel [this message]
2019-12-04  1:22             ` Yuan Fu
2019-12-04  3:41             ` Eli Zaretskii
2019-12-02 18:34 ` 황병희
2019-12-03 15:51   ` Yuan Fu
2019-12-03 22:33     ` 황병희

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cbcc7ff7-6af3-c5f9-5249-4ae59933347f@gmail.com \
    --to=cpitclaudel@gmail.com \
    --cc=eliz@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.