public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Vin Cent <irakay17-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: LateX to epub -- label rendering
Date: Sun, 5 Sep 2021 22:15:43 -0700 (PDT)	[thread overview]
Message-ID: <5f5cf592-c5cb-42b9-89dd-e718519d57e6n@googlegroups.com> (raw)
In-Reply-To: <0e877773-9a0a-4b4d-8f8b-b2d3f62d9fc6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


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

I have tried the static version of pandoc distributed on the website (so 
this is now pandoc 2.14.2).
For the record, the same problem still shows up with this version.
However, this is no big deal for me, as I have an easy and unintrusive fix 
by simply changing line order of my .tex source

On Monday, September 6, 2021 at 7:10:00 AM UTC+2 Vin Cent wrote:

> For the record, your guess is correct. I'm using debian unstable's 
> version, which is currently 2.9.2.1.
>
>
> On Friday, September 3, 2021 at 6:37:03 PM UTC+2 John MacFarlane wrote:
>
>>
>> I'm guessing you're not using the most recent version of pandoc?
>> (2.14.2) If not, try upgrading.
>>
>>
>> Vin Cent <irak...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>
>> > Hi,
>> >
>> > I'm quite new to pandoc, with some experience in LateX.
>> > I'm trying to convert a book (\documentclass{memoir} ) into a epub 
>> document.
>> >
>> > I have been able to get something quite fine (thanks pandoc! this is 
>> really 
>> > amazing) but now I seem to be stuck on a detail.
>> >
>> > Each chapter from my source starts with a label, such as :
>> >
>> > \chapter{First chapter head}
>> > \markboth{}{I. First chapter head}
>> > \label{ch:un}
>> >
>> > Foo bar
>> >
>> > \chapter{Second chapter head}
>> > \markboth{}{II. Second chapter head}
>> > \label{ch:deux}
>> >
>> > Which I compile with (I have removed a bunch of option in order to just 
>> > isolate my problem) :
>> > pandoc -o ebook.epub epub.tex --epub-metadata=metadata.xml --toc 
>> > --toc-depth=2
>> >
>> > The result of this is a render with my label name being displayed into 
>> > brackets.
>> > [ch:un]
>> >
>> > My expectation is that the label is not displayed, but serves only 
>> > anchors/links/navigation if a ref is defined pointing to it.
>> >
>> > Can you suggest how I can achieve this result ?
>> > I tried to look for this problem and 
>> > found https://github.com/lierdakil/pandoc-crossref/issues/319 but to 
>> be 
>> > honnest, I'm too much a pandoc newb to understand that thread. I have 
>> tried 
>> > quite a number of suggestions (adding the LUA script, adding a similar 
>> yaml 
>> > file, but this has changed nothing as far as my problem is concerned).
>> >
>> > Cheers,
>> >
>> > Vincent
>> >
>> > -- 
>> > 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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/pandoc-discuss/84cefde8-0943-43e2-8b7a-96efe6a0949cn%40googlegroups.com
>> .
>>
>

-- 
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/5f5cf592-c5cb-42b9-89dd-e718519d57e6n%40googlegroups.com.

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

  parent reply	other threads:[~2021-09-06  5:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AQHXoKNoYEHAej8q7UWdpdbA8+V+mauSCKOg///pkQCAADx/1g==>
     [not found] ` <AQHXoKNoYEHAej8q7UWdpdbA8+V+mauSCKOg>
2021-09-03  9:09   ` Vin Cent
     [not found]     ` <84cefde8-0943-43e2-8b7a-96efe6a0949cn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-03  9:21       ` AW: " denis.maier-NSENcxR/0n0
     [not found]         ` <c5aefee88458436f8ef800629a5c7686-NSENcxR/0n0@public.gmane.org>
2021-09-03 10:00           ` Vin Cent
     [not found]             ` <7a388540-5381-4e98-bda9-ebcac91a20a7n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-03 11:38               ` AW: " denis.maier-NSENcxR/0n0
     [not found]                 ` <0a0b065768ca449095035c65e5dabd6c-NSENcxR/0n0@public.gmane.org>
2021-09-03 12:02                   ` Vin Cent
2021-09-06 16:28           ` AW: " John MacFarlane
2021-09-03 16:36       ` John MacFarlane
     [not found]         ` <m2ilzhobts.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-09-06  5:10           ` Vin Cent
     [not found]             ` <0e877773-9a0a-4b4d-8f8b-b2d3f62d9fc6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-06  5:15               ` Vin Cent [this message]
     [not found]                 ` <5f5cf592-c5cb-42b9-89dd-e718519d57e6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-06 16:25                   ` John MacFarlane

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=5f5cf592-c5cb-42b9-89dd-e718519d57e6n@googlegroups.com \
    --to=irakay17-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).