From: Jambunathan K <kjambunathan@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Applying style to a paragraph for HTML export
Date: Thu, 05 May 2011 18:15:54 +0530 [thread overview]
Message-ID: <814o591fjx.fsf@gmail.com> (raw)
In-Reply-To: <pknbozh72f2.fsf@this.is.really.invalid> (Robert Pluim's message of "Thu, 05 May 2011 14:33:05 +0200")
Robert Pluim <rpluim@gmail.com> writes:
> Jambunathan K <kjambunathan@gmail.com> writes:
>
>> Robert Pluim <rpluim@gmail.com> writes:
>>
>>> (I thought this would be a FAQ, but I can't find anything similar)
>>>
>>> Hi,
>>>
>>> I'm exporting from org to html, which is working well. Since my final
>>> target is MSWord, I'd like to add style information to various
>>> paragraphs, ie bold, underline etc. I can see how to do eg *bold* for
>>> individual words, but how do I apply that kind of formatting to a span
>>> of text?
>>
>> I recommend using the odt exporter and then use LibreOffice to convert
>> the resulting file to MSWord.
>>
>> http://orgmode.org/worg/org-faq.html#convert-to-open-office
>
> Whilst that would work, it's inherently a 2-step process, versus 1 for
> the html route, plus it requires installing yet-another-application.
I thought you said your final target is MSWord and not html.
> In any case, the example file for the odt-converter has corrected my
> misunderstanding: *bold* works even for multiple words (although it
> appears the various style markers don't nest: */bold-italic/* give me
> the same as *bold*).
Spanned text has to be part of the single emacs line and not be broken
across multiple lines.
>
> Thanks
>
> Robert
>
>
>
--
next prev parent reply other threads:[~2011-05-05 12:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 9:37 Applying style to a paragraph for HTML export Robert Pluim
2011-05-05 12:05 ` Jambunathan K
2011-05-05 12:33 ` Robert Pluim
2011-05-05 12:45 ` Jambunathan K [this message]
2011-05-05 13:16 ` Robert Pluim
2011-05-05 12:51 ` Jambunathan K
-- strict thread matches above, loose matches on Subject: below --
2010-12-17 8:52 should the mail list be splitted resp. sub-tagged ? Torsten Wagner
2010-12-17 12:15 ` Andrew J. Korty
2010-12-17 14:00 ` Giovanni Ridolfi
2010-12-17 15:56 ` Nick Dokos
2010-12-17 17:28 ` Samuel Wales
2010-12-17 15:40 ` Nick Dokos
2010-12-17 18:21 ` William Gardella
2010-12-17 20:33 ` William Gardella
2010-12-17 21:16 ` Eric S Fraga
2010-12-18 12:09 ` Torsten Wagner
2011-01-04 15:19 ` Bastien
2011-01-04 17:39 ` Štěpán Němec
2011-01-04 18:12 ` Bastien
2011-01-04 18:31 ` Jeff Horn
2011-01-04 19:49 ` Štěpán Němec
2011-01-04 20:43 ` Nick Dokos
2011-01-04 18:52 ` Nick Dokos
2011-01-04 19:25 ` Robert Pluim
2011-01-05 9:13 ` Achim Gratz
2011-01-05 9:56 ` Robert Pluim
[not found] ` <rpluim@gmail.com>
2011-01-04 20:02 ` Nick Dokos
2011-01-05 8:15 ` Robert Pluim
2011-05-05 14:05 ` Applying style to a paragraph for HTML export Nick Dokos
2011-05-05 14:35 ` 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=814o591fjx.fsf@gmail.com \
--to=kjambunathan@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).