public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "'Nick Bart' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: "pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org"
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: How to improve .docx output?
Date: Thu, 22 Aug 2019 12:24:26 +0000	[thread overview]
Message-ID: <RC5rhmsP_qtblfskRIcPZHhdVlJt76IbH1X0a1IN_iFZ_-Q1fwRtQUS16-5M0zfTI0J54Wi9vk5Z8xzTRfAyYrOwpmlUzosE-rH9C1UcK7c=@protonmail.com> (raw)

For a certain project, I am forced to generate.docx documents.

While trying this out, I noticed that pandoc's default output still
feels somewhat rough around the edges in a number of aspects.

There are some issues that I have been able to fix using a
custom-reference.docx file (labelled as "can fix" below).

I have had trouble with others; some problems might of course be due to
the fact that I do not own Word (and have no inclination whatsoever to
buy it), so I have been editing custom-reference.docx with LibreOffice
(currently 6.2.6.2 on MacOS 10.13).

All in all, I wonder whether it would be feasible to generate.docx
documents that are out of the box more correct, feature-rich, and
aesthetically pleasing (ok, I'll admit I'm biased a bit here: more
latex-like) that currently.

What I've noticed so far regarding the default output, in no particular
order:

-   no page numbers (can fix)

-   no numbered section headings (was able to fix the first level, but
    not levels 2 and up; note that my results did not look right to
    begin with in LibreOffice, Menu: "Styles" → "Manage Styles")

-   With a custom-reference.docx modified to number section headings,
    `# References {-}` came out numbered, too; i.e., `{-}` was ignored.
    (A proper fix would probably require pandoc to attach a docx style
    like "Heading (unnumbered) 1" to such headings.)

-   uses default Microsoft fonts (could probably be fixed easily using a
    custom-reference.docx, but why doesn't pandoc use something more
    neutral, such as a Times/Helvetica combo - or at least something
    else that doesn't scream "I'm a Word document" straight away)?

-   LibreOffice displays some pandoc docx tables too wide (reported
    before: https://github.com/jgm/pandoc/issues/2576). For me, this
    happens when using simple tables (multiline tables come out ok).

-   With `--toc`, an empty table of contents (ok, can be fixed in LO via
    "Tools" → "Update" → "Update All"); and with a custom-reference.docx
    modified to number section headings, the toc title, again, is
    numbered.

So, my questions:

-   Has anyone been able to come up with a custom-reference.docx that
    solves some or all of these issues, and would be willing to share
    it, or would be interested in collaborating in order to develop one?

-   Any tips or tricks on editing a custom-reference.docx with LO (or
    with a plain text editor, for that matter)?

-   Any ideas on how to generate/update the table of contents without
    user interaction?

    -   I've seen this:https://ask.libreoffice.org/en/question/46586/how-to-automatically-update-indices-in-headless-mode/,
        and spent about an hour on it, but couldn't get it to work.

-   Any ideas on how to generate lists of tables and figures?

-- 
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/RC5rhmsP_qtblfskRIcPZHhdVlJt76IbH1X0a1IN_iFZ_-Q1fwRtQUS16-5M0zfTI0J54Wi9vk5Z8xzTRfAyYrOwpmlUzosE-rH9C1UcK7c%3D%40protonmail.com.


             reply	other threads:[~2019-08-22 12:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-22 12:24 'Nick Bart' via pandoc-discuss [this message]
2019-08-22 13:04 ` K4zuki
     [not found]   ` <32bb05e7-9d7b-47d8-8729-dd7b42281839-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-08-22 13:44     ` BP Jonsson

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='RC5rhmsP_qtblfskRIcPZHhdVlJt76IbH1X0a1IN_iFZ_-Q1fwRtQUS16-5M0zfTI0J54Wi9vk5Z8xzTRfAyYrOwpmlUzosE-rH9C1UcK7c=@protonmail.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).