From: BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Setting the document language on the HTML tag in epub3
Date: Wed, 30 Oct 2019 21:21:41 +0100 [thread overview]
Message-ID: <CADAJKhBQcOf8L00adQhWSd6PH8iF9TD7gbzNB0sJCnksN8_5pg@mail.gmail.com> (raw)
In-Reply-To: <b0afa24e-6be4-47a0-af2a-d36eeee469af-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 5742 bytes --]
That's really strange since it works for me! What happens if you use -V
lang=ja on the command line?
I hope any of the developers has a clue what is going on, because I
haven't. Sorry!
Den ons 30 okt. 2019 19:13Patrick Kenny <ptmkenny-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> skrev:
> Ok, here's some more information. I'm running Pandoc 2.7.3 on macOS
> 10.14.6.
>
> My custom template hasn't been modified in the header area:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE html>
> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="
> http://www.idpf.org/2007/ops"$if(lang)$ xml:lang="$lang$"$endif$>
> <head>
> <meta charset="utf-8" />
> <meta name="generator" content="pandoc" />
> <title>$pagetitle$</title>
>
> I have a file called book-variables.yaml that looks like this:
>
> ---
> lang: ja
> title:
> - type: main
> text: "Wow a book"
> creator:
> - role: author
> text: "Me"
> language: ja
> identifier:
> - scheme: DOI
> text: doi:10.234234.234/33
> ibooks:
> version: 1.3.4
> page-progression-direction: ltr
> ---
>
> And I am using the command:
>
> /usr/local/bin/pandoc mybook_epub_apple_4pandoc /Users/me/Library/
> MobileDocuments/com~apple~CloudDocs/book-variables.yaml -o mybook.epub --
> from=markdown-smart --to=epub-smart --toc --toc-depth=3 --epub-
> chapter-level=2 -M date=2019-10-31 --css epub.css --
> resource-path .:/Users/me/Library/MobileDocuments/com~apple~CloudDocs/audio
> --epub-cover-image=cover.jpg --template mytemplate.epub3 &>
> epub_apple_pandoc_errors.txt
>
> With this setup, cover.xhtml and title_page.xhtml have the language set on
> the HTML tag, but none of the chapter files do. (ch001.xhtml, etc.)
>
>
>
> On Thursday, October 31, 2019 at 12:14:13 AM UTC+9, BP wrote:
>>
>> I just tried to generate an epub (something I don't usually do) having
>> set the `lang` variable to `sv` and as far as I can see every .xhtml
>> file in the archive has an attribute `xml:lang="sv"`, and the default
>> templates for both epub3 and epub2 have an `$if(lang)$
>> xml:lang="$lang$"$endif$` in the `html` tag. So one or both of the
>> following must be the case:
>>
>> - Your version of pandoc is outdated.
>> - You are using a custom template which lacks the `$if(lang)$
>> xml:lang="$lang$"$endif$` in the `html` tag.
>>
>> I suggest upgrading pandoc and/or adding the needed bit to you template.
>>
>>
>>
>> On 2019-10-30 01:39, Patrick Kenny wrote:
>> > Thank you for the response.
>> >
>> > When I use
>> >
>> > lang:ja
>> >
>> > Then
>> >
>> > * cover.xhtml
>> > * title_page.xhtml
>> >
>> > get
>> >
>> > xml:lang="ja"
>> >
>> > as expected, but none of the chapter files do. (ch001.xhtml, etc.) Is
>> this
>> > the expected behavior? How can I also modify the chapter files?
>> >
>> >
>> > On Wednesday, October 30, 2019 at 1:42:15 AM UTC+9, BP Jonsson wrote:
>> >>
>> >> The metadata key is exactly like the placeholder in the template, no
>> more,
>> >> no less, i.e. `lang: ja`. This is true generally, and you can easily
>> define
>> >> your own variables in your own templates. That wouldn't work if Pandoc
>> >> meddled with the variable names so that the names used in metadata and
>> >> those used in templates were somehow different.
>> >>
>> >>
>> >> Den tis 29 okt. 2019 15:40Patrick Kenny <ptmk...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
>> <javascript:>>
>> >> skrev:
>> >>
>> >>> Going from markdown to epub3, how do I set the language on the HTML
>> tag
>> >>> in the epub?
>> >>>
>> >>> For epub3, the template looks like this:
>> >>>
>> >>> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="
>> >>> http://www.idpf.org/2007/ops"$if(lang)$ xml:lang="$lang$"$endif$>
>> >>>
>> >>> In my YAML metadata block, I have this:
>> >>>
>> >>> language: ja
>> >>>
>> >>> This sets the language in content.opf:
>> >>>
>> >>> <dc:language>ja</dc:language>
>> >>>
>> >>> But it doesn't set the language on the HTML tag.
>> >>>
>> >>> I also tried adding
>> >>>
>> >>> language: ja
>> >>>
>> >>> to the metadata, but this didn't change the value on the HTML tag,
>> either.
>> >>>
>> >>> --
>> >>> 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-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>.
>> >>> To view this discussion on the web visit
>> >>>
>> https://groups.google.com/d/msgid/pandoc-discuss/c500692e-7472-40fa-991e-378b7ab173d5%40googlegroups.com
>> >>> <
>> https://groups.google.com/d/msgid/pandoc-discuss/c500692e-7472-40fa-991e-378b7ab173d5%40googlegroups.com?utm_medium=email&utm_source=footer>
>>
>> >>> .
>> >>>
>> >>
>> >
>>
>> --
> 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/b0afa24e-6be4-47a0-af2a-d36eeee469af%40googlegroups.com
> <https://groups.google.com/d/msgid/pandoc-discuss/b0afa24e-6be4-47a0-af2a-d36eeee469af%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
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/CADAJKhBQcOf8L00adQhWSd6PH8iF9TD7gbzNB0sJCnksN8_5pg%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 14455 bytes --]
next prev parent reply other threads:[~2019-10-30 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 14:40 Patrick Kenny
[not found] ` <c500692e-7472-40fa-991e-378b7ab173d5-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-10-29 16:41 ` BP Jonsson
[not found] ` <CAFC_yuTob=pKyjGrQ3tT8SNp+o7E2hbpz3MZRqy_52=mfy5wJw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-10-30 0:39 ` Patrick Kenny
[not found] ` <92867006-1219-4139-9aff-1bc7345c09c5-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-10-30 14:00 ` BP Jonsson
[not found] ` <CAFC_yuShZKiXOcyR2A3QPO6R=0s2m5SkbYKDwm=DP+Y8pWRwvw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-10-30 14:15 ` Daniel Staal
2019-10-30 15:13 ` Benct Philip Jonsson
[not found] ` <bcba4331-6848-78df-39b4-66027098c757-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-10-30 18:12 ` Patrick Kenny
[not found] ` <b0afa24e-6be4-47a0-af2a-d36eeee469af-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-10-30 20:21 ` BPJ [this message]
2019-11-03 22:59 ` John MacFarlane
2019-11-03 23:11 ` 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=CADAJKhBQcOf8L00adQhWSd6PH8iF9TD7gbzNB0sJCnksN8_5pg@mail.gmail.com \
--to=melroch-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).