unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Sebastien Vauban <sva-news@mygooglest.com>
Cc: 19872@debbugs.gnu.org
Subject: bug#19872: 24.4; UTF8 characters of unusual width (Gnus markers)
Date: Sun, 15 Feb 2015 18:27:19 +0200	[thread overview]
Message-ID: <83wq3juom0.fsf@gnu.org> (raw)
In-Reply-To: <86bnkvilxl.fsf@example.com>

> From: Sebastien Vauban <sva-news@mygooglest.com>
> Date: Sun, 15 Feb 2015 10:05:58 +0100
> 
> Now that I've changed some Gnus markers to UTF8 "drawings" [1], I don't
> have my Gnus summary buffer correctly aligned anymore.
> 
> See http://screencast.com/t/s33eYYg7Cn.
> 
> Is there a solution to that, to guarantee that the alignment can be
> correct?

Only if Gnus will align text using the :align-to display property,
instead of inserting whitespace characters.

> Worse, it seems that the same UTF8 char can have a "correct" width in
> some fonts, and not in others...

Of course: it depends on the dimensions of the glyphs in each font.





  reply	other threads:[~2015-02-15 16:27 UTC|newest]

Thread overview: 15+ 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 [this message]
     [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
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-18  3:49           ` 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

  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=83wq3juom0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=19872@debbugs.gnu.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 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).