From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jambunathan K Subject: comments and attributes Date: Wed, 01 Feb 2012 14:46:24 +0530 Message-ID: <81aa52vrpz.fsf_-_@gmail.com> References: <87aa5lwfxm.fsf@med.uni-goettingen.de> <81pqefv4r9.fsf@gmail.com> <87r4yt9x5u.fsf@med.uni-goettingen.de> <81ipk2mbzv.fsf@gmail.com> <878vkyi09l.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:38512) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RsWJB-0000Vh-5C for emacs-orgmode@gnu.org; Wed, 01 Feb 2012 04:16:58 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RsWJ1-00032J-Jh for emacs-orgmode@gnu.org; Wed, 01 Feb 2012 04:16:53 -0500 Received: from mail-pw0-f41.google.com ([209.85.160.41]:33470) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RsWJ1-00032D-92 for emacs-orgmode@gnu.org; Wed, 01 Feb 2012 04:16:43 -0500 Received: by pbaa12 with SMTP id a12so1038987pba.0 for ; Wed, 01 Feb 2012 01:16:42 -0800 (PST) In-Reply-To: <878vkyi09l.fsf@gmail.com> (Nicolas Goaziou's message of "Mon, 23 Jan 2012 22:20:38 +0100") 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: Orgmode Nicolas Goaziou writes: > Hello, > > Jambunathan K writes: > >> Does the existing behaviour as captured in [[Side-by-Side images laid >> out by hand]] be preserved with new export driver? > > I'm not sure to get the syntax right, but in the new exporter, you can > see what is the next or previous element, along with its > properties. Thus, you can detect when two paragraphs are back to back, > if they have appropriate :attr_latex properties and if they are enclosed > in a parent center-block element. > > The check could be done at the paragraph level, and, if positive, > org-odt-paragraph could return the draw:style....>... string. > > Am I missing something? On a related note, --8<---------------cut here---------------start------------->8--- * Example This is a single # some comment paragraph. This is another #+attr_odt: t paragraph. --8<---------------cut here---------------end--------------->8--- if I parse the above buffer, I get #+begin_src emacs-lisp (paragraph (:begin 412 :end 431 :contents-begin 412 :contents-end 430 :post-blank 0) "This \nis \na\nsingle") (comment (:begin 431 :end 446 :value "# some comment\n" :post-blank 0)) (paragraph (:begin 446 :end 459 :contents-begin 446 :contents-end 456 :post-blank 2) "paragraph.") (paragraph (:begin 459 :end 477 :contents-begin 459 :contents-end 476 :post-blank 0) "This \nis \nanother") (paragraph (:begin 477 :end 502 :contents-begin 491 :contents-end 501 :post-blank 0 :attr_odt ("t")) "paragraph.") #+end_src I see that the new export engine treats comment and control lines as par breakers. The backends that are in production treats the first paragraph as but a single paragraph. There is already a way by which parbreaks can be introduced. Do you think there could be some useful behaviour achieved - side by side export of images came up in this thread - by not having commented elements introduce parbreaks. I am only brainstorming here. I hope the examples and use-case taken up here help steer our discussion in a meaningful manner. > Regards,