emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: James Harkins <jamshark70@zoho.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: ox-odt: List items contain body paragraphs, confusing styles
Date: Sun, 20 Aug 2017 20:46:44 +0800	[thread overview]
Message-ID: <15dffae5f20.2778.82338e46905ca0a1b8f7a8095ee71cce@zoho.com> (raw)
In-Reply-To: <87mv6uim30.fsf@nicolasgoaziou.fr>

On August 20, 2017 18:13:13 Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:

> Out of curiosity, instead of creating a new style, wouldn't some
> standard style be enough, e.g., "Text_20_body_20_indent"?
>
> Also, what happens in the following cases
>
>     - ...
>
>       #+begin_quote
>       Quoted paragraph
>       #+end_quote
>
>       #+begin_center
>       Centered paragraph
>       #+end_center
>
> Should the use "Quotations" and "OrgCenter", which inherit from
> "Text_20_body", or some new style inheriting from the one dedicated to
> text in plain lists?

Interesting questions -- however, I'm leaving tomorrow for a week's 
holiday. So I won't get to this for awhile.

I should also say: This is the first time I've needed the ODT exporter for 
anything serious. So, I shouldn't be taken as any sort of authority on how 
the styles "should" work. I'm reporting behavior that seemed odd to me and, 
to the extent that I have time, I don't mind prowling around in the ODT 
data structures to see what is going on inside. That's about the extent of 
what I can do. I'm not affiliated with LibreOffice in any way... In fact, I 
quite dread using it. TBH I prefer exporting to LaTeX, but it's a 
humanities journal and they don't understand about superior technology :D

That said, I'm not sure why those cases would be challenging. In the normal 
list item case, you have a list item node enclosing one or more paragraph 
nodes. In the cases you mentioned, the list item node would contain a quote 
block or centered block node. As I understand the exporter, the depth-first 
traversal would encode the child nodes normally, and pass the encoded 
result up to the list item parent. My observation of LO is that it tries to 
merge properties from the list style and paragraph style, which it would do 
if it's centered, block quote or whatever. So my guess is, do nothing 
special for these cases. But that's a guess.

hjh

Sent with AquaMail for Android
http://www.aqua-mail.com

      reply	other threads:[~2017-08-20 12:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17  2:47 ox-odt: List items contain body paragraphs, confusing styles James Harkins
2017-08-17 14:33 ` Nicolas Goaziou
2017-08-18  3:27   ` James Harkins
2017-08-19  8:36     ` Nicolas Goaziou
2017-08-19 10:40       ` James Harkins
2017-08-19 11:55         ` Nicolas Goaziou
2017-08-20  6:10           ` James Harkins
2017-08-20 10:13             ` Nicolas Goaziou
2017-08-20 12:46               ` James Harkins [this message]

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=15dffae5f20.2778.82338e46905ca0a1b8f7a8095ee71cce@zoho.com \
    --to=jamshark70@zoho.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).