From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Sebastien Vauban
<public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: wish: provide flush_right/right_aligned text rendering directive
Date: Thu, 22 May 2014 13:27:20 +0200 [thread overview]
Message-ID: <87a9aanjdz.fsf@selenimh.mobile.lan> (raw)
In-Reply-To: <868upugp7u.fsf@somewhere.org> (Sebastien Vauban's message of "Thu, 22 May 2014 11:03:17 +0200")
Hello,
Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
writes:
> Nicolas Goaziou wrote:
>> In addition to @code{#+BEGIN_CENTER} blocks (@pxref{Paragraphs}), it is
>> possible to justify contents to the left or the right of the page with the
>> following dedicated blocks.
>>
>> @example
>> #+BEGIN_JUSTIFYLEFT
>> It's just a jump to the left
>> #+END_JUSTIFYLEFT
>>
>> #+BEGIN_JUSTIFYRIGHT
>> And then a step to the right.
>> #+END_JUSTIFYRIGHT
>> @end example
>
> Do I understand correctly that those won't be converted to their
> HTML and LaTeX counterparts (flushright and raggedleft)?
Correct. As Bastien pointed out, there are means to achieve the same in
other back-ends.
> Shouldn't it be better to make that conversion as well for the back-ends
> which support such features?
For some values of "better" only.
At the moment, these blocks belong to the "special blocks" category, aka
"do whatever back-end specific stuff you want" category. This category
is convenient because it doesn't require to extend Org syntax, and it
has room left in some back-ends (like ascii, but not in latex and html,
which handle all possible special blocks already).
What you are asking is to move out these blocks from the "special
blocks" category (because, again, there is no room left in html and
latex), and, as a consequence, create a new syntax element in Org. While
this is possible, it implies to extend the parser to handle it, and,
more importantly, to ask all serious export back-ends in the wild to do
their best to support the new feature (if they don't provide
a transcoder, all contents will be ignored without notice).
My opinion is that the feature is a) not important enough and b) somehow
already available in Org. I'm all for consistency, but in this
particular case, the benefit is way too slim.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-05-22 11:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 13:52 wish: provide flush_right/right_aligned text rendering directive Gregor Zattler
2014-05-21 2:30 ` Bastien
2014-05-21 7:39 ` Gregor Zattler
2014-05-21 11:48 ` Bastien
2014-05-21 13:06 ` Nicolas Goaziou
2014-05-21 13:13 ` Bastien
2014-05-21 13:36 ` Nicolas Goaziou
2014-05-21 13:49 ` Bastien
2014-05-21 14:34 ` Nicolas Goaziou
2014-05-21 15:51 ` Bastien
2014-05-21 16:12 ` Nicolas Goaziou
2014-05-21 16:20 ` Bastien
2014-05-21 22:12 ` Nicolas Goaziou
2014-05-22 8:38 ` Bastien
2014-05-22 11:51 ` Nicolas Goaziou
2014-05-22 12:30 ` Bastien
2014-05-22 9:03 ` Sebastien Vauban
2014-05-22 9:15 ` Bastien
2014-05-22 9:26 ` Sebastien Vauban
2014-05-22 11:27 ` Nicolas Goaziou [this message]
2014-05-23 20:54 ` thanks, works great (was: Re: wish: provide flush_right/right_aligned text rendering directive) Gregor Zattler
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=87a9aanjdz.fsf@selenimh.mobile.lan \
--to=n.goaziou@gmail.com \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.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.
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).