public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: iandol <iandol-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: compatibility mode with default reference.docx
Date: Sun, 17 Sep 2017 07:40:43 -0700 (PDT)	[thread overview]
Message-ID: <c220f8cf-c9b1-47f3-80c6-439ad3611380@googlegroups.com> (raw)
In-Reply-To: <20170916180411.GA81541-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>


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

Convert file always works fine here. I suspect some users will not notice 
this, and the only detrimental thing I think is that kerning and proper 
opentype features are not enables in compatibility mode. 

On Sunday, 17 September 2017 02:04:28 UTC+8, John MacFarlane wrote:
>
> I think this is harmless.  We aim to produce a document that 
> can be opened with as many versions of Word as possible. 
> You can convert it with File -> Convert File. 
>
> Is there a problem with producing a docx in compatibility 
> mode? 
>
> +++ tolot27 [Sep 16 17 09:03 ]: 
> >   Hi! 
> >   I'm using the the nightly build from pandoc and also tried pandoc 
> >   1.19.2.1 and getting the same docx output in compatibility mode if I 
> >   just convert a simple document with the default reference.docx: 
> >   echo "# Test" | pandoc -o test.docx 
> >   What is the cause for this compatibility mode? 
> >   I use it with Windows 10 and Microsoft Office 365 German. 
> >   -- 
> >   Regards, 
> >   Mathias 
> > 
> >   -- 
> >   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 [1]pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
> >   To post to this group, send email to 
> >   [2]pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>. 
> >   To view this discussion on the web visit 
> >   [3]
> https://groups.google.com/d/msgid/pandoc-discuss/d9f63599-ef02-478c- 
> >   930b-299058da9b0e%40googlegroups.com. 
> >   For more options, visit [4]https://groups.google.com/d/optout. 
> > 
> >References 
> > 
> >   1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:> 
> >   2. mailto:pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:> 
> >   3. 
> https://groups.google.com/d/msgid/pandoc-discuss/d9f63599-ef02-478c-930b-299058da9b0e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer 
> >   4. https://groups.google.com/d/optout 
>
>

-- 
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/c220f8cf-c9b1-47f3-80c6-439ad3611380%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

      parent reply	other threads:[~2017-09-17 14:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-16 16:03 tolot27
     [not found] ` <d9f63599-ef02-478c-930b-299058da9b0e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-09-16 18:04   ` John MacFarlane
     [not found]     ` <20170916180411.GA81541-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-09-17 14:40       ` iandol [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=c220f8cf-c9b1-47f3-80c6-439ad3611380@googlegroups.com \
    --to=iandol-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).