public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Milan Bracke <milan.bracke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: docx: PAGEREF fields with hyperlink switch
Date: Thu, 3 Jun 2021 06:23:22 -0700 (PDT)	[thread overview]
Message-ID: <5e2ae841-6cd5-4c6c-bb58-acbb2aa428ben@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1020 bytes --]

Hi,

In a docx, we can have a PAGEREF field like this (omitting the surrounding
fldChar tags):
<w:instrText xml:space="preserve"> PAGEREF _Toc293064234 \h </w:instrText>
where the '\h' switch indicates that it's a hyperlink (as specified by
ECMA-376-1:2016, §17.16.5.45). I've encountered this feature in a table of
contents. Pandoc currently processes the similar HYPERLINK fields but not 
the
PAGEREF fields (see module Text.Pandoc.Readers.Docx.Fields).

I would like to implement treating the PAGEREF fields as hyperlinks when 
they
have a hyperlink switch. Any feedback or 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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/5e2ae841-6cd5-4c6c-bb58-acbb2aa428ben%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1329 bytes --]

             reply	other threads:[~2021-06-03 13:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 13:23 Milan Bracke [this message]
     [not found] ` <5e2ae841-6cd5-4c6c-bb58-acbb2aa428ben-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-06-07  6:56   ` Milan Bracke

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=5e2ae841-6cd5-4c6c-bb58-acbb2aa428ben@googlegroups.com \
    --to=milan.bracke-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).