From: mohamed <mohamed.hibti@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Exporting an article to a (very) specific formatting template
Date: Mon, 29 Apr 2013 15:15:15 +0000 (UTC) [thread overview]
Message-ID: <loom.20130429T170633-939@post.gmane.org> (raw)
In-Reply-To: loom.20130429T092019-738@post.gmane.org
James Harkins <jamshark70 <at> gmail.com> writes:
>
> Actually, let me take a few steps back from my specific question about
> the title command. There are some other workflow questions that might
> make that question redundant.
>
> This journal (for some reason unknown to me) has designed the
> publication format in MS Word, and there are some specific
> requirements. So I have a couple of choices:
>
> - Export to LaTeX, and try to reproduce their layout (likely with a
> new document class based on "article"). That's a chunk of work, but
> they also confirmed that I could send PDF as long as it follows the
> style guidelines.
>
> - Export to ODT. This is probably simpler for setup -- I'd probably
> just need to change some of the names of paragraph or character
> styles in their template so that org can find them for section
> headings, abstract etc. But... there is more risk of the formatting
> breaking. If I send .odt, MS Word might choke on it, or similar
> if I resave my .odt as .docx. (The word online is that LibreOffice
> does not do well saving docx.)
>
> Or, export to ODT and let LibreOffice turn that into a PDF. I hesitate
> to do this, when LaTeX is a far superior typesetter. (But, tweaking
> all the formatting details in LaTeX is quite likely to give me some
> more gray hairs...)
>
> Advice? Thanks --
> hjh
>
>
I used both aproaches :
- Usually I customize the org options (latex templates) to meet the
requirements of the final document. It is convenient for me to stay in
emacs. For the gray hairs, you do it once and thus you have minor
modifications.
- But sometimes when I work with other colleagues I need to have something
more common, odt seems fine but as you mentioned you may have to add a final
manual toutch to be sure your document can be modified by the others.
Regards,
next prev parent reply other threads:[~2013-04-29 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 7:22 Exporting an article to a (very) specific formatting template James Harkins
2013-04-29 15:15 ` mohamed [this message]
2013-04-30 1:57 ` James Harkins
2013-04-30 15:14 ` Eric S Fraga
2013-04-30 15:57 ` Marcin Borkowski
2013-04-29 21:09 ` Marcin Borkowski
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=loom.20130429T170633-939@post.gmane.org \
--to=mohamed.hibti@gmail.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).