public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: jamie bowman <jamiereecebowman-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: track changes not detected in docx reader
Date: Mon, 17 Jun 2019 10:05:24 -0700 (PDT)	[thread overview]
Message-ID: <6fc5920d-e67b-45ed-ab18-ab668ba95f83@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1332 bytes --]

I have a .docx file which I've tried converting to various different 
formats (markdown attached as an example), but none of the formats are 
including the changes from the original file. I've tried all the options 
available to the --track-changes switch, but there is only a blank space 
where the changes were made. I have attached an excerpt from the document 
and the example conversion. I have tried on Windows 7 and MacOS using both 
the latest version of pandoc (2.7.3) and the prior release (2.7.2), but the 
same thing happens. I'm assuming it's something to do with the docx file, 
as when I save it as .odt and then convert, I get the changes (although the 
footnote formatting goes a bit awry). Has anyone had this issue before with 
.docx files?

-- 
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/6fc5920d-e67b-45ed-ab18-ab668ba95f83%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 1754 bytes --]

[-- Attachment #2: track-changes-test.docx --]
[-- Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document, Size: 84819 bytes --]

[-- Attachment #3: track-changes-test.md --]
[-- Type: text/markdown, Size: 1480 bytes --]

1 Introduction
==============

Refugee protection poses a unique and pressing challenge to the global
community and international law, especially at the present time.
According to UNHCR's annual statistical report, there 19.9 million
refugees in the world in 2017.[^1] Another 5.4 million Palestinian
refugees were registered by the United Nations Relief and Works Agency
for Palestine Refugees in the Near East (UNRWA).[^2]

As UNHCR pointed out in its 2017 statistical report, \[a\]ltogether,
more than two-thirds (68 per cent) of all refugees worldwide came from
just five countries.[^3] This highlights a striking feature of today's
refugee problems, i.e. situations in *a few* countries are generating
the *majority* of global refugee population. As Table 1[^4] illustrates,
every year from 2010 to 2017, numbers of refugees coming from the top
three to five origin countries already constituted the majority of
global refugee population.

[^1]: UNHCR, *Global Trends: Forced Displacement in 2017* at 2,
    available at www.unhcr.org/5b27be547.pdf (last visited 24 August
    2018). UNHCR's statistics adopt a broad definition of refugees which
    include refugees defined under treaties and the UNHCR Statute,
    individuals granted complementary or temporary protection and people
    in refugee-like situations, at 61.

[^2]: Ibid at 2.

[^3]: Ibid at 3.

[^4]: All the statistics are excerpted from the UNHCR *Global Trends*
    reports and calculated by this author.

             reply	other threads:[~2019-06-17 17:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17 17:05 jamie bowman [this message]
     [not found] ` <6fc5920d-e67b-45ed-ab18-ab668ba95f83-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-06-17 17:47   ` Image paths Craig Parker
     [not found]     ` <986687ce-fef3-4d0f-fa34-f8eaa334e089-UzRat0APdLvLPIzirxu/xA@public.gmane.org>
2019-06-17 18:05       ` Duy Huy Hoang Do
     [not found]         ` <CAGgd1yHokadjMj=1QPrF=75yy251n5wnA6chzTrY0L1NhHiv5w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-06-17 20:32           ` Craig Parker
2019-06-18  9:55       ` jamie bowman
2019-06-18 14:22   ` track changes not detected in docx reader 'Jason Seeley' via pandoc-discuss
     [not found]     ` <9023ffd7-42a7-4e1b-8ada-3a2c6bb4e183-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-06-23 10:45       ` John MacFarlane

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=6fc5920d-e67b-45ed-ab18-ab668ba95f83@googlegroups.com \
    --to=jamiereecebowman-re5jqeeqqe8avxtiumwx3w@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).