public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Conversion of underbrace (to and from Word)
Date: Tue, 3 Oct 2017 13:52:28 -0700	[thread overview]
Message-ID: <20171003205227.GA14633@protagoras> (raw)
In-Reply-To: <f240aa27-3e64-430c-82b0-55e095a5b175-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

This bug got fixed in texmath in February 2016.

If you compile your pandoc against the most recent version
of texmath, it should work.

Anyway, this will be fixed in the pandoc 2.0 binary
packages.  Or you can try (at your own risk) a binary
from pandoc-nightlies.


+++ Emma Cliffe [Oct 03 17 02:36 ]:
>   Morning,
>   I am having trouble getting pandoc to convert underbrace either into
>   Word or out of Word. I wondered if there is either something I am doing
>   wrong, whether this is a known problem (I can't find a report) or if
>   there is a work round for converting into Word.
>   If I try to convert:
>   \[
>   \underbrace{xxx\ldots xx}_n
>   \]
>   for instance then what I get in Word (linear format) is:
>   ((xxx…xx)┬⏟)┬n
>   which does not render as a stretched underbrace.
>   I would expect to get:
>   ⏟(xxx…xx)┬n
>   which is typed directly into Word as \underbrace(xxx\ldots xx)_n (then
>   space to trigger). You get the same linear interpretation if you use
>   the mouse to create the structure.
>   The above is the direction I am interested in. I am actually converting
>   from MathML and see the same behaviour as in the cut down test of md or
>   tex to docx I have explained above.
>   For completeness I tried to convert in the other direction. Starting
>   from the above structure in Word I end up with:
>   \[\underset{n}{}\]
>   which has not only lost the xxx...xx but underbrace has become underset
>   which is not the same thing.
>   Does anyone know anything more about this?
>   Many thanks,
>   Emma
>
>   --
>   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-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To post to this group, send email to
>   [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>   To view this discussion on the web visit
>   [3]https://groups.google.com/d/msgid/pandoc-discuss/f240aa27-3e64-430c-
>   82b0-55e095a5b175%40googlegroups.com.
>   For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
>   1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
>   3. https://groups.google.com/d/msgid/pandoc-discuss/f240aa27-3e64-430c-82b0-55e095a5b175-/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/20171003205227.GA14633%40protagoras.
For more options, visit https://groups.google.com/d/optout.


  parent reply	other threads:[~2017-10-03 20:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03  9:36 Emma Cliffe
     [not found] ` <f240aa27-3e64-430c-82b0-55e095a5b175-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-03  9:43   ` Emma Cliffe
2017-10-03 10:14   ` Emma Cliffe
2017-10-03 20:52   ` John MACFARLANE [this message]
2018-01-22 18:08     ` Emma Cliffe
     [not found]       ` <150196ab-c7ac-428b-b989-583e8e91db64-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-01-22 19:27         ` John MACFARLANE
2018-01-23 10:27           ` Emma Cliffe
     [not found]             ` <d253238b-b377-41c7-a0bf-44cfc2a447fc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-01-23 11:06               ` Emma Cliffe
     [not found]                 ` <0a27b5b4-cdcd-4446-a5f1-31fbdfe3b2dc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-01-23 13:55                   ` Emma Cliffe
     [not found]                     ` <333b70c6-30a1-4167-8135-f6fe87429621-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2018-01-23 17:02                       ` 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=20171003205227.GA14633@protagoras \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@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).