emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Luis Anaya <papoanaya@hotmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Using HTML or ODF to get content from Org to Word
Date: Sat, 14 Jul 2012 14:42:10 -0400	[thread overview]
Message-ID: <BLU0-SMTP184B53E30C689A44C97E1E9B7D60@phx.gbl> (raw)
In-Reply-To: <mailman.101.1342281620.27625.emacs-orgmode@gnu.org> (emacs-orgmode-request@gnu.org's message of "Sat\, 14 Jul 2012 12\:00\:20 -0400")

emacs-orgmode-request@gnu.org writes:
>
> I am a bit puzzled. I thought that using the ODF-exporter would be
> the format of choice to get content from Org to Word. Why do you
> guys prefer HTML?

The following is my opinion why I prefer using HTML to ODF for transfer
to Word, but  there is no reason for not using ODF for transfer files.  
It is more a matter of personal taste than anything else. 

1. Mature support for HTML import on Word. ODF import was included in Office
2007 as an option. But HTML support has been available since Office
2000. (probably since Office '98, but it's been a while since I used
that one).  If you do not have the ODF facility installed in Word or 
if you're stuck with an older version of Office  then you have to 
convert to Word using Libre/Open Office.  That's an extra step and 
more conversion errors to add to the final result.  

2. Less nuances to worry about. HTML is clean and a plain ASCII format
at the expense of size.  I am not familiar with ODF's internal
structure, but I've worked on the generation of MS Open Office XML
documents at work.  Even though it's an XML format, there are sometimes 
difference in the positioning of elemements when documents are created
in Word vs  when they are created through a program using the MSOOXML
libraries. 

One issue I had during testing was the inclusion of images in
which they get installed on a different nodes if the document is created
through the .NET API. These causes images not to show up in
LibreOffice or AbiWord to crash. However they render fine in Word. 


My 2 cents...
-- 
Luis Anaya
papo anaya aroba hot mail punto com
"Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo

       reply	other threads:[~2012-07-14 18:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.101.1342281620.27625.emacs-orgmode@gnu.org>
2012-07-14 18:42 ` Luis Anaya [this message]
     [not found] <mailman.133.1342195226.11448.emacs-orgmode@gnu.org>
2012-07-14  8:37 ` How to integrate org-mode in a MS Windows-/Office-based environment? Luis Anaya
2012-07-14  9:56   ` Using HTML or ODF to get content from Org to Word (was: How to integrate org-mode in a MS Windows-/Office-based environment?) Karl Voit
2012-07-14 15:15     ` Giovanni Ridolfi
2012-07-14 15:39       ` Using HTML or ODF to get content from Org to Word Karl Voit
2012-07-14 16:07         ` Jambunathan K
2012-07-14 16:16           ` Jambunathan K
2012-07-14 18:00           ` Karl Voit
2012-07-14 18:11             ` 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=BLU0-SMTP184B53E30C689A44C97E1E9B7D60@phx.gbl \
    --to=papoanaya@hotmail.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).