From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Spacing within org-mode tables when diacritics are used
Date: Sat, 02 Sep 2017 22:21:10 +0300 [thread overview]
Message-ID: <83k21gykih.fsf@gnu.org> (raw)
In-Reply-To: <e610eabb-9ded-e38d-3f0b-74c93f334478@yandex.com> (message from Mario Castelán Castro on Sat, 2 Sep 2017 13:52:37 -0500)
> From: Mario Castelán Castro <marioxcc.MT@yandex.com>
> Date: Sat, 2 Sep 2017 13:52:37 -0500
>
> On 02/09/17 10:13, Eli Zaretskii wrote:
> > Maybe you are right, although string-width shouldn't affect display of
> > normal-width characters such as é. It only affects double-width
> > characters, or characters that Emacs composes into a single grapheme
> > cluster. Multibyte-ness per se doesn't come into play here. That's
> > why I asked how that é was typed, and what was its encoding on the
> > file (if the table was imported from a file). If there were actually
> > 2 characters, e and ́, then yes, using length would produce wrong
> > results that string-width would fix.
>
> So what you are saying is that GNU Emacs is broken in that it assumes
> that 1 Unicode code point corresponds to 1 glyph.
Which part of what I wrote led you to that conclusion? That's not
what I meant, not at all. What I meant was that a Lisp program is
broken if it uses 'length' to compute how many glyphs (the accurate
term is "grapheme clusters", not "glyphs") correspond to the
characters of a string. It should use 'string-width' instead.
next prev parent reply other threads:[~2017-09-02 19:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 19:19 Spacing within org-mode tables when diacritics are used Leo Vivier
2017-09-01 8:44 ` Eli Zaretskii
2017-09-01 21:02 ` Eric Abrahamsen
2017-09-02 7:45 ` Eli Zaretskii
2017-09-02 14:58 ` Eric Abrahamsen
2017-09-02 15:13 ` Eli Zaretskii
2017-09-02 18:14 ` Eric Abrahamsen
2017-09-02 18:52 ` Mario Castelán Castro
2017-09-02 19:21 ` Eli Zaretskii [this message]
2017-09-02 19:23 ` Mario Castelán Castro
2017-09-02 21:16 ` Eric Abrahamsen
2017-09-03 1:08 ` Mario Castelán Castro
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=83k21gykih.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).