public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Preserving whitespace when converting from docx to html
Date: Mon, 12 Feb 2018 13:04:18 -0500	[thread overview]
Message-ID: <75ffcc03-a8b9-61f4-213b-56b8e9517248@usa.net> (raw)
In-Reply-To: <20180212175452.GB21067@protagoras>

On 2/12/18 12:54 PM, John MACFARLANE wrote:
> There's no way to do it, sorry.  we try to capture document
> structure, and inevitably little stylistic details get lost.
> 
> +++ Phoebe Gao [Feb 12 18 08:31 ]:
>>   Does anyone know of a way to preserve whitespace when converting docx
>>   to html using Pandoc? When I have multiple spaces in my docx file (for
>>   formatting purposes), the outputted html replaces consecutive
>>   whitespaces with a single whitespace. Thanks! 

Also worth remembering is that HTML doesn't consider whitespace as 
significant - it collapses all whitespace.  So even if it was preserved, 
it wouldn't be persevered in the browser.

Daniel T. Staal

---------------------------------------------------------------
This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/75ffcc03-a8b9-61f4-213b-56b8e9517248%40usa.net.
For more options, visit https://groups.google.com/d/optout.


      reply	other threads:[~2018-02-12 18:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12 16:31 Phoebe Gao
     [not found] ` <4cd6d65d-4a07-4d69-84c6-9a19a672425c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-02-12 17:54   ` John MACFARLANE
2018-02-12 18:04     ` Daniel Staal [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=75ffcc03-a8b9-61f4-213b-56b8e9517248@usa.net \
    --to=dstaal-jdbf3xikgs8@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).