From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Ufimtsev Subject: bug#18870: bug#18870: \emsp and alignment in org clock report Date: Wed, 18 Mar 2015 17:10:20 -0400 (EDT) Message-ID: <1296089020.23116290.1426713020569.JavaMail.zimbra@redhat.com> References: <544f71eb.0aadc20a.595f.70e0@mx.google.com> <1426142440.1635596.239250013.1BC7F573@webmail.messagingengine.com> <87sid31gcs.fsf@nicolasgoaziou.fr> <20150317214758.GE19234@benfinney.id.au> <87oanr1do8.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41851) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YYMHu-0005pF-3N for emacs-orgmode@gnu.org; Wed, 18 Mar 2015 18:18:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YYMHq-0002mu-T8 for emacs-orgmode@gnu.org; Wed, 18 Mar 2015 18:18:06 -0400 Received: from debbugs.gnu.org ([140.186.70.43]:53483) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YYMHq-0002mq-Qx for emacs-orgmode@gnu.org; Wed, 18 Mar 2015 18:18:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1YYMHq-0006Zv-Eb for emacs-orgmode@gnu.org; Wed, 18 Mar 2015 18:18:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87oanr1do8.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou Cc: Ben Finney , 18870@debbugs.gnu.org I can't speak for the technical details,=20 but I get the sense that \emsp isn't the right thing to be displayed on an = *agenda clock report* because=20 agenda clock reports don't get exported (afaik).=20 Even \__ is more preffered than an \emsp, as \emsp is not 'easy to read' pe= r se. Since there are clearly difference in opinions, maybe a solution is to have= a variable like 'org-clockreport-indentation-character' which defaults to = \emsp=20 for correct export, but could be changed to spaces or '\__' by the user. Th= is would give people the choice between better export or better text-buffer= display. Thoughts? Leo Ufimtsev | Intern Software Engineer @ Eclipse Team ----- Original Message ----- From: "Nicolas Goaziou" To: "Ben Finney" Cc: 18870@debbugs.gnu.org Sent: Tuesday, March 17, 2015 6:07:03 PM Subject: [O] bug#18870: \emsp and alignment in org clock report Ben Finney writes: > The behaviour described =E2=80=93 displaying =E2=80=9C\emsp=E2=80=9D inst= ead of space > characters =E2=80=93 is a regression. That's what is being reported in th= is > bug. There wasn't space characters in the first place, but "\___" constructs. See commit bacfe5b4f7244eaf151f4e26a1d94dd8f66c1d19.=20 Also, the bug is about table alignment when `org-pretty-entities' is used. >> 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) > > So the U+2003 EM SPACE character should be translated *during export*, > and not be literally in the displayed text. No, because it means this character should be treated specially by Org (e.g., LaTeX just ignores it so it needs to be turned into a space there).=20 This is not a good idea, especially considering it is an invisible character. > IS the above suggestion an acceptable solution? No, it isn't.=20 An acceptable solution would be a character or a string that looks decent both in the buffer and in an exported document, without further processing. >> Note that this is not LaTeX-specific markup. This is called an entity, >> and is correctly exported in various back-ends. > > But not for display, which is the bug to be fixed here. Actually, it works more or less correctly for display on GUI with a non-nil `org-pretty-entities', or calling `org-toggle-pretty-entities'. Regards,