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: Mon, 22 Jan 2018 11:27:21 -0800 [thread overview]
Message-ID: <20180122192721.GB88560@protagoras> (raw)
In-Reply-To: <150196ab-c7ac-428b-b989-583e8e91db64-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 6315 bytes --]
Here's what I get when I convert
$$
\underbrace{xxx\ldots xx}_n
$$
from markdown to docx (see attached screenshot).
That looks just right to me. I wasn't sure how to
interpret your "linear format" strings, so I'm not
sure what you're seeing. You can attach a screenshot.
Your pandoc is compiled against a recent version
of texmath (0.10.1).
+++ Emma Cliffe [Jan 22 18 10:08 ]:
> Dear John,
> Thanks for the information below. For some reason I didn't see your
> response when you posted it. I have just now tried the latest version
> of pandoc from the downloads page (pandoc 2.1.1 Compiled with
> pandoc-types 1.17.3, texmath 0.10.1, skylighting 0.6) and I am getting
> the same problem. The output in linear format of Word is ((xxx…xx)┬(}
> ))┬n which does not render correctly. This seems to be about the same
> as what I was getting before: ((xxx…xx)┬⏟)┬n and not what I would
> expect to get: ⏟(xxx…xx)┬n
> From what I can tell the binary is using a version of texmath that
> contains the below mentioned fix?
> Thanks for any help you can give us.
> Emma
> On Tuesday, 3 October 2017 21:52:27 UTC+1, John MacFarlane wrote:
>
> 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][1]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To post to this group, send email to
> > [2][2]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit
> > [3][3]https://groups.google.com/d/msgid/pandoc-discuss/
> f240aa27-3e64-430c-
> > 82b0-55e095a5b175%[4]40googlegroups.com.
> > For more options, visit [4][5]https://groups.google.com/
> d/optout.
> >
> >References
> >
> > 1. mailto:[6]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > 2. mailto:[7]pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > 3. [8]https://groups.google.com/d/msgid/pandoc-discuss/f240aa27-
> 3e64-430c-82b0-55e095a5b175-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=
> email&utm_source=footer
> > 4. [9]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 [10]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [11]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [12]https://groups.google.com/d/msgid/pandoc-discuss/150196ab-c7ac-428b
> -b989-583e8e91db64%40googlegroups.com.
> For more options, visit [13]https://groups.google.com/d/optout.
>
>References
>
> 1. javascript:/
> 2. javascript:/
> 3. https://groups.google.com/d/msgid/pandoc-discuss/f240aa27-3e64-430c-
> 4. http://40googlegroups.com/
> 5. https://groups.google.com/d/optout
> 6. javascript:/
> 7. javascript:/
> 8. https://groups.google.com/d/msgid/pandoc-discuss/f240aa27-3e64-430c-82b0-55e095a5b175-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 9. https://groups.google.com/d/optout
> 10. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 11. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 12. https://groups.google.com/d/msgid/pandoc-discuss/150196ab-c7ac-428b-b989-583e8e91db64-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 13. 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/20180122192721.GB88560%40protagoras.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #2: Screen Shot 2018-01-22 at 11.22.54 AM.png --]
[-- Type: image/png, Size: 10229 bytes --]
next prev parent reply other threads:[~2018-01-22 19:27 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
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 [this message]
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=20180122192721.GB88560@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).