From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: wish: provide flush_right/right_aligned text rendering directive Date: Thu, 22 May 2014 13:27:20 +0200 Message-ID: <87a9aanjdz.fsf@selenimh.mobile.lan> References: <20140510135216.GA2041@boo.workgroup> <878upvsw1u.fsf@bzg.ath.cx> <20140521073916.GA25852@boo.workgroup> <87sio3ic8y.fsf@bzg.ath.cx> <877g5f1dso.fsf@gmail.com> <878upvw9yr.fsf@bzg.ath.cx> <8738g31cfg.fsf@gmail.com> <87egznutrb.fsf@bzg.ath.cx> <87mwebyzcr.fsf@gmail.com> <87y4xvjfjk.fsf@bzg.ath.cx> <87ioozyuuf.fsf@gmail.com> <87k39fje7m.fsf@bzg.ath.cx> <877g5ezspi.fsf@gmail.com> <868upugp7u.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53094) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WnR9V-0007qI-Ro for emacs-orgmode@gnu.org; Thu, 22 May 2014 07:27:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WnR9N-0000B9-HF for emacs-orgmode@gnu.org; Thu, 22 May 2014 07:27:13 -0400 Received: from plane.gmane.org ([80.91.229.3]:47215) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WnR9N-0000Az-9J for emacs-orgmode@gnu.org; Thu, 22 May 2014 07:27:05 -0400 Received: from public by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WnR9L-0000lR-FT for emacs-orgmode@gnu.org; Thu, 22 May 2014 13:27:03 +0200 In-Reply-To: <868upugp7u.fsf@somewhere.org> (Sebastien Vauban's message of "Thu, 22 May 2014 11:03:17 +0200") 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: Sebastien Vauban Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org Hello, Sebastien Vauban 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