From: Christian Moe <mail@christianmoe.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: [ANN][RFC] org-odt.texi/org-odt.pdf preview (was Re: Org-odt table format)
Date: Thu, 27 Oct 2011 11:09:24 +0200 [thread overview]
Message-ID: <4EA91FC4.8000008@christianmoe.com> (raw)
In-Reply-To: <81y5w78w95.fsf_-_@gmail.com>
Hi, Jambunathan,
This is great. I'd be happy to proofread. What's the best way to
return the proofs to you? A diff of the .texi?
A couple of questions and suggestions. First, about the syntax rather
than about the manual:
- Image attributes: Are the parentheses needed in the ATTR_ODT line?
(This is not about the manual, but about the syntax.) It would be
simpler and generally more consistent with user expectations from
other ATTR lines, I think, if it worked like this:
#+ATTR_ODT: :width 10 :height 10
About the manual:
- Literal examples:
- Add a hint, where does one get an enhanced htmlfontify.el?
- References and captions (not covered): It would be worth mentioning
in the Tables and Images sections that these will work, but that you
may need to use Tools>Update>Fields in LibreOffice to get them
displayed right.
- There are some long technical sections that are great if you want to
get under the hood, but may be a bit intimidating, and that come
before the short first-aid stuff. You might want to consider:
- Starting "Applying Custom Styles" with a simple howto setting out
the user-friendly steps: export an ODT (with num:t and any other
settings needed to get all the styles), tweak its looks in LibreOffice
(preserving heading numbering as an option), save the result and point
to it with ODT_STYLES_FILE.
(As it is, the manual gives a strong impression that the user will
have to mess with XML files to get custom styles.)
- Possibly moving "Exporting and Converting to Other Formats" to the
end of the manual.
- Possibly separating out the explanation of custom table styles as a
separate section and moving it to the end of the manual. (BTW, custom
table styles sounds great, I'm looking forward to trying this out.)
Yours,
Christian
On 10/26/11 8:04 PM, Jambunathan K wrote:
>
> The org-odt.texi and org-odt.pdf are in the parent of this mail. It is
> also accessible as attachment at
> http://article.gmane.org/gmane.emacs.orgmode/48468
>
> Proof readers invited.
>
next prev parent reply other threads:[~2011-10-27 9:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 10:58 Org-odt table format Vikas Rawal
2011-10-26 17:53 ` Jambunathan K
2011-10-26 18:04 ` [ANN][RFC] org-odt.texi/org-odt.pdf preview (was Re: Org-odt table format) Jambunathan K
2011-10-27 9:09 ` Christian Moe [this message]
2011-10-28 4:19 ` Jambunathan K
2011-10-28 7:47 ` Christian Moe
2011-12-10 23:13 ` Jambunathan K
2011-12-11 7:18 ` Christian Moe
2011-12-10 23:16 ` Jambunathan K
2011-10-28 2:01 ` Org-odt table format Vikas Rawal
2011-10-28 3:38 ` Jambunathan K
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=4EA91FC4.8000008@christianmoe.com \
--to=mail@christianmoe.com \
--cc=emacs-orgmode@gnu.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).