From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Ben Finney <ben@benfinney.id.au>
Cc: 18870@debbugs.gnu.org
Subject: bug#18870: \emsp and alignment in org clock report
Date: Tue, 17 Mar 2015 22:09:07 +0100 [thread overview]
Message-ID: <87sid31gcs.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <1426142440.1635596.239250013.1BC7F573@webmail.messagingengine.com> (Ben Finney's message of "Thu, 12 Mar 2015 17:40:40 +1100")
Hello,
Ben Finney <ben@benfinney.id.au> writes:
> I confirm this behaviour.
>
> With a plain text terminal, a clock report shows like:
>
> |-------------------+------------------------------+--------+------+------|
> | willow-it.org | *File time* | *5:25* | |
> |
> | | Willow IT | 5:25 | |
> |
> | | \emsp Administration | | 3:44 |
> |
> | | \emsp\emsp Induction | | |
> 3:44 |
> | | \emsp Training & development | | 1:41 |
> |
> | | \emsp\emsp Odoo research | | |
> 1:41 |
> |-------------------+------------------------------+--------+------+------|
>
> The "\emsp" should be space characters (of some kind; either U+0020 SPC
> or U+2003 EM SPACE) with correct alignment for the character width.
> Displaying literal "\emsp" is a regression and should not happen.
This is not a regression. This change favors a correct export over
a correct display.
Having some space character is not desirable as it would just move the
problem the other way around (i.e., indentation would not appear during
export)
In a nutshell, the current situation is not perfect, but we have yet to
find a proper character to preserve both indentation during export and
readability.
> If having a U+2003 EM SPACE character is desirable, then instead of
> LaTeX-specific markup (which is useless in the text buffer), that
> character should appear directly in the data so it is useful for
> display.
Note that this is not LaTeX-specific markup. This is called an entity,
and is correctly exported in various back-ends.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2015-03-17 21:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <544f71eb.0aadc20a.595f.70e0@mx.google.com>
2015-03-12 6:40 ` bug#18870: \emsp and alignment in org clock report Ben Finney
2015-03-17 21:09 ` Nicolas Goaziou [this message]
2015-03-17 21:47 ` Ben Finney
2015-03-17 22:07 ` Nicolas Goaziou
2015-03-18 21:10 ` bug#18870: " Leo Ufimtsev
2015-03-19 16:48 ` Subhan Michael Tindall
2015-03-19 21:33 ` bug#18870: " Leo Ufimtsev
2015-03-21 8:55 ` Nicolas Goaziou
2015-03-22 21:44 ` Nicolas Goaziou
2015-03-23 16:09 ` J. David Boyd
2017-12-01 18:48 ` Nicolas Goaziou
2017-12-01 18:53 ` Glenn Morris
2017-12-01 19:11 ` Nicolas Goaziou
2015-03-22 22:49 ` Ben Finney
2015-03-23 0:02 ` Nicolas Goaziou
2016-08-22 6:18 ` bug#18870: " Sriram Karra
2016-08-22 7:57 ` Nicolas Goaziou
2017-12-04 5:49 ` Ben Finney
2017-12-04 7:22 ` Nicolas Goaziou
2017-12-04 8:32 ` Ben Finney
2017-12-04 13:43 ` Nicolas Goaziou
2017-12-04 19:42 ` Ben Finney
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sid31gcs.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=18870@debbugs.gnu.org \
--cc=ben@benfinney.id.au \
/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/org-mode.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).