From: Jambunathan K <kjambunathan@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Orgmode <emacs-orgmode@gnu.org>
Subject: comments and attributes
Date: Wed, 01 Feb 2012 14:46:24 +0530 [thread overview]
Message-ID: <81aa52vrpz.fsf_-_@gmail.com> (raw)
In-Reply-To: <878vkyi09l.fsf@gmail.com> (Nicolas Goaziou's message of "Mon, 23 Jan 2012 22:20:38 +0100")
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Hello,
>
> Jambunathan K <kjambunathan@gmail.com> 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:fram
> draw:style....>...</draw:frame> 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,
next prev parent reply other threads:[~2012-02-01 9:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 8:52 [ODT] image scaling overridden by long caption Andreas Leha
2012-01-19 20:03 ` Jambunathan K
2012-01-21 10:18 ` Andreas Leha
2012-01-23 19:53 ` Jambunathan K
2012-01-23 21:20 ` Nicolas Goaziou
2012-02-01 9:16 ` Jambunathan K [this message]
2012-02-01 13:04 ` comments and attributes Nicolas Goaziou
2012-02-15 0:03 ` [ODT] image scaling overridden by long caption Andreas Leha
2012-01-27 14:40 ` Jambunathan K
2012-01-27 22:41 ` Andreas Leha
2012-01-31 4:59 ` Jambunathan K
2012-02-07 10:04 ` Andreas Leha
2012-01-23 1:53 ` Side-by-side support (was:Re: [ODT] image scaling overridden by long caption) Christian Wittern
2012-01-23 16:34 ` Side-by-side support Jambunathan K
2012-01-23 23:51 ` Christian Wittern
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=81aa52vrpz.fsf_-_@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/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).