From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Ineditable InDesign tables
Date: Mon, 2 Nov 2015 22:59:06 -0800 [thread overview]
Message-ID: <20151103065906.GA63949@protagoras.berkeley.edu> (raw)
In-Reply-To: <63666713-4a76-4729-9e2b-5ec536946624-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Try creating a simple markdown table in table.md, then:
pandoc -t icml table.md
to look at the icml source pandoc produces for that table.
Let us know if anything looks fishy. I don't know anything
about ICML, but output for a simple table looks plausible to me
and I don't see doubled anything...
Any ICML experts out there who can comment?
+++ Adam Rice [Nov 02 15 15:08 ]:
> I'm using Pandoc to create an ICML file from a series of markdown
> files. I have a few simple tables in these files.
> When I create an InDesign document and flow the ICML file into it, the
> tables do appear, however, the column widths are extremely narrow
> (about 6 characters wide), and I cannot reformat them. When I look at
> the table in InDesign's Story Editor, there seem to be some spurious
> tags, which I suspect might be part of the problem: Story Editor is
> showing me *two* "TablePar > TableHeader" tags for each column-header
> cell, and two "TablePar" tags for each ordinary cell.
> When I create an equivalent table from scratch in InDesign, I see only
> one tag per cell. It also doesn't include (for better or worse) the
> table captions that result from Pandoc.
> Thanks in advance for any help.
>
> --
> 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/63666713-4a76-4729-
> 9e2b-5ec536946624%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/63666713-4a76-4729-9e2b-5ec536946624-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 4. https://groups.google.com/d/optout
next prev parent reply other threads:[~2015-11-03 6:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 23:08 Adam Rice
[not found] ` <63666713-4a76-4729-9e2b-5ec536946624-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-11-03 6:59 ` John MACFARLANE [this message]
2015-11-04 16:12 ` mb21
[not found] ` <4fdbbbd3-e672-4fba-8373-7712e1eba4af-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-11-04 23:34 ` Adam Rice
[not found] ` <74189035-9f1e-4e3f-9c70-84df43cc2041-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-11-05 9:44 ` mb21
[not found] ` <6e61390a-690c-41c7-8912-2f87dde74147-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-11-05 14:09 ` Adam Rice
[not found] ` <5cdf0a04-78b5-4322-8ed0-eff1125d4c0b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-11-06 20:47 ` mb21
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=20151103065906.GA63949@protagoras.berkeley.edu \
--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).