From: Nikolay Yakimov <g.livid-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Reference.docx and default Word styles
Date: Tue, 24 Feb 2015 09:56:19 -0800 (PST) [thread overview]
Message-ID: <62149c61-fcbb-465d-b1ca-6d0b881c9072@googlegroups.com> (raw)
In-Reply-To: <10d80cbd-5bdb-4937-811c-24af52aaadf3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1550 bytes --]
Thank you for your input, Matthew, John
I think this kind of concludes this discussion, since both of you are in
favor of #2, and I was leaning to it as well.
As for FootnoteRef and Link, I'll be sure to test for regressions to the
best of my ability. Not sure if I'll be able to fix underlying issue, but
I'll have to try to know for sure.
One point I'm still not sure about is captions. On one hand, ImageCaption
and TableCaption have semantic value, since they store more information
than just Caption style. On the other hand, there *is* a style for captions
already.
I'm thinking about having Caption in reference.docx and generating
ImageCaption and TableCaption in the same manner as, e.g. SourceCode,
basing them on Caption. This will have an added benefit of simplifying
getting captions in docx reader (something I was planning to tackle in near
future), since all captions, including Word-created ones, will be based on
the same style. Any objections?
--
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/62149c61-fcbb-465d-b1ca-6d0b881c9072%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2062 bytes --]
next prev parent reply other threads:[~2015-02-24 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 22:14 Nikolay Yakimov
[not found] ` <10d80cbd-5bdb-4937-811c-24af52aaadf3-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-02-24 10:36 ` Matthew Pickering
[not found] ` <d71ce0fa-d002-474a-8e6e-b97500b27352-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-02-24 17:26 ` John MacFarlane
2015-02-24 17:56 ` Nikolay Yakimov [this message]
[not found] ` <62149c61-fcbb-465d-b1ca-6d0b881c9072-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-02-24 18:11 ` John MacFarlane
[not found] ` <20150224181115.GA439-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
2015-02-24 18:16 ` Nikolay Yakimov
[not found] ` <30cd30a9-014a-426a-b0f8-5be416ba4c58-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-02-24 20:57 ` Denis Navas
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=62149c61-fcbb-465d-b1ca-6d0b881c9072@googlegroups.com \
--to=g.livid-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).