From: CesarJ M <cesarjorgemartinez-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Converting from md to docx cut title lenght marker
Date: Wed, 27 Sep 2017 08:31:43 -0700 (PDT) [thread overview]
Message-ID: <d38d254a-6645-43cf-8301-acd7f7e78e5d@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1337 bytes --]
Hi,
I using pandoc:
$ pandoc --version
pandoc.exe 2.0
Compiled with pandoc-types 1.17.2, texmath 0.9.4.2, skylighting 0.4
Then, I convert this example md (I convert to a letter):
- [3. Aaaaaaaa aa AAA AaAaaaaaa](#3-aaaaaaaa-aa-aaa-aaaaaaaaa)
- [3.1. Aaaaaaaa aa aaaaaaaa aa aa aaaaaaaaaa AAA
AaAaaaaaa](#31-aaaaaaaa-aa-aaaaaaaa-aa-aa-aaaaaaaaaa-AAA-AaAaaaaaa)
...
## 3.1. Aaaaaaaa aa aaaaaaaa aa aa aaaaaaaaaa AAA AaAaaaaaa ##
To docx. Then, the second level link not work in the docx. Click in modify
hyperlink and:
Text: 3.1. Aaaaaaaa aa aaaaaaaa aa aa aaaaaaaaaa AAA AaAaaaaaa
Direction: #31-aaaaaaaa-aa-aaaaaaaa-aa-aa-aaaaaaaaaa-AAA-AaAaaaaaa
But in marker I see the following:
"#31-aaaaaaaa-aa-aaaaaaaa-aa-aa-aaaaaaaa"
Is cutting the title.
Regards
--
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/d38d254a-6645-43cf-8301-acd7f7e78e5d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 1812 bytes --]
reply other threads:[~2017-09-27 15:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d38d254a-6645-43cf-8301-acd7f7e78e5d@googlegroups.com \
--to=cesarjorgemartinez-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).