From: "'RickEEE' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Converting Word.docx tables to AsciiDoc (adoc) formatting issue
Date: Mon, 9 Mar 2020 14:42:35 -0700 (PDT) [thread overview]
Message-ID: <8926d873-aea0-449e-b16e-252c3abf5306@googlegroups.com> (raw)
In-Reply-To: <yh480ky2sdo17w.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2376 bytes --]
Thx for getting back to me, John. Unfortunately, I cannot provide the
troublesome Word document, because the information is proprietary. To
date, I've search/replaced all double-quotes, single quotes with straight
ones. I've replaced all dashes. I'll keep digging. thx.
On Friday, March 6, 2020 at 11:14:13 AM UTC-6, John MacFarlane wrote:
>
> Can you give us a Word sample illustrating the problem?
>
> "'RickEEE' via pandoc-discuss" <pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>>
>
> writes:
>
> > Pandoc has been a huge time saver for converting source Word.docx files
> to
> > asciidoctor format. Specifically, I'm converting Word-format tables to
> > asciidoctor-format tables, and of the 40 I've converted, only one output
> > file has table width issues that i have not been able to overcome by
> > manually replacing "smart" quotes with straight quotes. However, one
> file
> > has me stumped, and I'm hoping that a pandoc extension will help my
> > situation.
> >
> > Below are some commands I've used. Any suggestions either on using the
> > Smart (or other) extension, or what other character could be causing the
> > formatting issue in the rendered HTML?
> >
> >
> > Commands I've used that all yield the same output:
> >
> > - pandoc -o outputfile.adoc wordfile.docx
> >
> >
> > - pandoc -t asciidoc-smart -o outputfile.adoc wordfile.docx
> >
> >
> > - pandoc --ascii -o outputfile.adoc wordfile.docx
> >
> >
> > I am using Pandoc 2.7.3 on Linux
> >
> > --
> > 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-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/d056ceca-c6f9-4bc5-91a7-162475a8ef2f%40googlegroups.com.
>
>
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/8926d873-aea0-449e-b16e-252c3abf5306%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3966 bytes --]
prev parent reply other threads:[~2020-03-09 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 22:31 'RickEEE' via pandoc-discuss
[not found] ` <d056ceca-c6f9-4bc5-91a7-162475a8ef2f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-03-06 17:13 ` John MacFarlane
[not found] ` <yh480ky2sdo17w.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-03-09 21:42 ` 'RickEEE' via pandoc-discuss [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=8926d873-aea0-449e-b16e-252c3abf5306@googlegroups.com \
--to=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).