From: Nikolay Yakimov <g.livid-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Reference.docx and default Word styles
Date: Mon, 23 Feb 2015 14:14:27 -0800 (PST) [thread overview]
Message-ID: <10d80cbd-5bdb-4937-811c-24af52aaadf3@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2297 bytes --]
Hi. I'm working on https://github.com/jgm/pandoc/pull/1968, and I've got
some questions.
Some styles in reference.docx are marked as custom, some are not. Some of
those not marked custom are recognized by Word as built-in. Some are not,
however. Word automatically marks those as custom, but this introduces
unnecessary ambiguity. Furthermore, some styles not recognized by Word as
built-in actually duplicate built-in styles, and could be renamed to
reflect that.
Here is a list of styles I'm most concerned about:
Nameambiguoustypecan be replaced byAuthoryesp?Abstractyesp?Compactyesp?Image
Captionyespcaption?Block QuoteyespIntense Quote, Block Text, QuoteTable
Captionyespcaption?Definition Termyesp?Definitionyesp?FirstParagraphyesp?
LinknocHyperlinkFootnote Refnocfootnote reference
these are either ambiguous (again, meaning that they are neither custom,
nor Word defaults), duplicate default Word styles, or both.
So the question is, what should be done with them? I've got the following
options:
1. Update reference.docx to define ambiguous styles as custom. Do
nothing more. This is a quick-and-dirty solution.
2. Replace styles in reference with word-recognized ones as best I can,
set those I can't as custom. This is a longer path, but leading to
hopefully better user experience.
3. Do nothing at all, and hope for the best. This will likely lead to
'surprises' in the future, and not the pleasant kind, I fear.
First two options require significant updates to reference.docx though, and
option 2 is not strictly backwards-compatible with pandoc-created docx
(although it'll likely be a couple of styles, not much more).
So, what are your thoughts on this matter?
--
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/10d80cbd-5bdb-4937-811c-24af52aaadf3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 14240 bytes --]
next reply other threads:[~2015-02-23 22:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 22:14 Nikolay Yakimov [this message]
[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
[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=10d80cbd-5bdb-4937-811c-24af52aaadf3@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).