From: "JDani Jiménez" <jdjp83-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Insistent format converting from MarkDown to OpenDocument
Date: Fri, 29 Apr 2016 02:21:43 -0700 (PDT) [thread overview]
Message-ID: <3681192c-529b-47f0-afcd-393ecf49508c@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1764 bytes --]
Why when converting this MarkDown code:
This is **bold text**, this is regular text. This is **bold text** again.
I'm getting this OpenDocument code:
<text:p text:style-name="Text_20_body">
This is
<text:span text:style-name="T1">
bold
</text:span>
<text:span text:style-name="T2">
</text:span>
<text:span text:style-name="T3">
text
</text:span>
, this is regular text. This is
<text:span text:style-name="T4">
bold
</text:span>
<text:span text:style-name="T5">
</text:span>
<text:span text:style-name="T6">
text
</text:span>
again.
</text:p>
This is the python code I'm using to convert it:
pandoc_args = []
pandoc_args.append("--reference-odt")
pandoc_args.append("style_reference_file.odt")
opendocument_code = pypandoc.convert(markdown_code, 'opendocument', format=
'markdown_github', extra_args=pandoc_args)
This is the result:
<https://lh3.googleusercontent.com/-MjLFMgsLy04/VyMlXBjmFrI/AAAAAAAAQVU/syCsLO6CHv8GBBSrfg09zXD0z6knRHLzQCLcB/s1600/pandoc_styles.png>
I understand that I have to define styles, that's not the problem, I'll
control it in the future. But this is my question: why, for the same style,
I get different style-names?
Thanks again!
--
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/3681192c-529b-47f0-afcd-393ecf49508c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 11118 bytes --]
next reply other threads:[~2016-04-29 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 9:21 JDani Jiménez [this message]
[not found] ` <3681192c-529b-47f0-afcd-393ecf49508c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-04-29 9:52 ` JDani Jiménez
2016-04-30 3:27 ` 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=3681192c-529b-47f0-afcd-393ecf49508c@googlegroups.com \
--to=jdjp83-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).