From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: sva-news@mygooglest.com, 19872@debbugs.gnu.org
Subject: bug#19872: 24.4; UTF8 characters of unusual width (Gnus markers)
Date: Wed, 18 Feb 2015 05:43:51 +0200 [thread overview]
Message-ID: <83k2zf6g08.fsf@gnu.org> (raw)
In-Reply-To: <878ufwcamp.fsf@building.gnus.org>
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: sva-news@mygooglest.com, 19872@debbugs.gnu.org
> Date: Wed, 18 Feb 2015 11:43:26 +1100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I don't see why would you need to do all that. First, you already do
> > these calculations, to know how many blanks to insert, right? So you
> > already know whether a string is too long, at least in terms of
> > characters, right? And :align-to can work in character units as well
> > as in pixels.
>
> Well, the problem here is that some fonts are wider than others. If
> Gnus says "this should be 20 characters wide", then if some of the
> glyphs are wider than the normal 20 characters, then things won't line
> up any more.
AFAIR, :align-to works in units of canonical character width, so this
problem does not exist.
> > And second, AFAIU you are talking about an additional feature. The OP
> > presented a use case where no string is too long, AFAICT. So it would
> > get you bonus points to handle long strings as well, but that's not
> > what this bug report is about: the same problem exists with the
> > current "alignment" using whitespace, right?
>
> Gnus truncates the strings if they're too long and inserts spaces if
> they're too short.
Then I think you already have everything in place, just replace
insertion of blanks with a :align-to display property.
next prev parent reply other threads:[~2015-02-18 3:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 9:05 bug#19872: 24.4; UTF8 characters of unusual width (Gnus markers) Sebastien Vauban
2015-02-15 16:27 ` Eli Zaretskii
[not found] ` <mailman.138.1424017693.31049.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.138.1424017693.31049.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2015-02-16 9:45 ` Sebastien Vauban
2015-02-16 15:51 ` Eli Zaretskii
2015-02-16 20:10 ` Stefan Monnier
2015-02-17 4:17 ` Lars Ingebrigtsen
2015-02-17 15:44 ` Eli Zaretskii
2015-02-18 0:43 ` Lars Ingebrigtsen
2015-02-18 3:43 ` Eli Zaretskii [this message]
2015-02-19 5:49 ` Lars Ingebrigtsen
2015-02-19 6:30 ` Eli Zaretskii
2015-02-19 13:49 ` Stefan Monnier
2015-02-19 14:03 ` Eli Zaretskii
2015-02-19 16:12 ` Columns and proportional fonts (was: bug#19872: 24.4; UTF8 characters of unusual width (Gnus markers)) Stefan Monnier
2015-02-19 17:37 ` Columns and proportional fonts Ivan Shmakov
2015-02-19 18:09 ` Eli Zaretskii
2015-02-19 18:41 ` Stefan Monnier
2015-02-18 3:49 ` bug#19872: 24.4; UTF8 characters of unusual width (Gnus markers) Stefan Monnier
2016-02-07 6:04 ` Lars Ingebrigtsen
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=83k2zf6g08.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19872@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=sva-news@mygooglest.com \
/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.