From: Daniel E. Doherty <email@example.com>
To: Nicolas Goaziou <firstname.lastname@example.org>
Cc: Org-mode List <email@example.com>, "J. David Boyd" <firstname.lastname@example.org>
Subject: Re: /emsp in clock tables
Date: Fri, 12 Dec 2014 13:11:46 -0600 [thread overview]
Message-ID: <email@example.com> (raw)
It looks like an alignment bug to me. The \emsp is rendered as a double-width
character with org-pretty-entities on, and the table no longer aligns
At least it doesn't for me. Try tabbing through the table with
org-pretty-entities on when the \emsp char is used for indenting.
At Fri, 12 Dec 2014 18:26:39 +0100,
Nicolas Goaziou <firstname.lastname@example.org> wrote:
> Daniel E. Doherty <email@example.com> writes:
> > I am seeing the same thing. When I set org-pretty-entities t, the alignment
> > gets confused. I am assuming that the alignment algorithm assumes all
> > characters are the same width, but the utf8 rendering of an em-space is wider,
> > hence the problems.
> > Perhaps a fix would be for the clocktable to use two en-spaces instead of one
> > em-space to indent lower levels. It looks to me as though the en-space is as
> > wide as a single space.
> > Em-space [ ]
> > En-space [ ]
> > space [ ]
> > Using regular ASCII spaces at the beginning get deleted during alignment of
> > the table, but not the en-spaces.
> > I think this is a bug in the implementation of the clocktables. Any chance of
> > getting this fixed?
> What is the bug? The fact that \emsp is used instead \ensp?
> Nicolas Goaziou
next prev parent reply other threads:[~2014-12-12 19:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 16:52 /emsp in clock tables J. David Boyd
2014-12-11 17:16 ` Joost Helberg
2014-12-12 15:18 ` J. David Boyd
2014-12-12 16:46 ` Daniel E. Doherty
[not found] ` <firstname.lastname@example.org>
2014-12-12 19:11 ` Daniel E. Doherty [this message]
2014-12-12 19:59 ` J. David Boyd
2014-12-12 20:48 ` J. David Boyd
2014-12-12 23:05 ` Nicolas Goaziou
2014-12-13 11:58 ` Joost Helberg
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).