public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Header attributes and docx
Date: Sat, 06 May 2023 08:41:16 +0200	[thread overview]
Message-ID: <87r0ru9ce8.fsf@zeitkraut.de> (raw)
In-Reply-To: <d9a83a0b-50b4-46fb-9b7e-4f0855cf0599n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Conversions are generally lossy; some info cannot be preserved. In this
case here the issue is that the docx reader ignores "bookmark" entries
in the input document. Changing this would require updates to the docx
reader:
https://github.com/jgm/pandoc/blob/main/src/Text/Pandoc/Readers/Docx.hs

Miguel <bagnon-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Say you have the following file:
>
> # This is a section {#section}
>
> Converting this to html/docbook/latex and back to markdown properly
> handles and keeps the header attribute:
>
>> pandoc -t docbook test.md | pandoc -f docbook -t markdown
>
> # This is a section {#section}
>
> But when converting and reversing from docx, the header attribute is
> lost:
>
>> pandoc -t docx test.md | pandoc -f docx -t markdown
>
> # This is a section
>
> How can this be fixed, and convert back from docx without losing the
> given header id? 


-- 
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124

-- 
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/87r0ru9ce8.fsf%40zeitkraut.de.


  parent reply	other threads:[~2023-05-06  6:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06  5:51 Miguel
     [not found] ` <d9a83a0b-50b4-46fb-9b7e-4f0855cf0599n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-06  6:41   ` Albert Krewinkel [this message]
     [not found]     ` <87r0ru9ce8.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-05-06  7:18       ` Miguel

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=87r0ru9ce8.fsf@zeitkraut.de \
    --to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@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).