From: Shigeru Kobayashi <mayfair-+k8b35VvZrR3+QwDJ9on6Q@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Issues with Quotation Marks in Pandoc When Mixing Japanese and English Texts
Date: Mon, 10 Apr 2023 16:30:37 -0700 (PDT) [thread overview]
Message-ID: <602edc59-8983-4459-bbbb-85cee5f013b3n@googlegroups.com> (raw)
In-Reply-To: <D44375EB-4058-4C5F-AF39-461B38B30EE7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 4666 bytes --]
Dear Bastien DUMONT and John MacFarlane,
Thank you very much for your reply.
Regarding issue 1, I will use Unicode curly quotes instead of strait quotes
to avoid misinterpretation.
Regarding issue 2, I tried marking the English text as [That person said,
"Hello, world!"]{lang=en}, but the result was the same (i.e., quotes are
typeset with the Japanese font instead of the English font). I also tried
Unicode curly quotes.
I have confirmed that "pandoc input.md -t input.tex" generates a code as
expected as follows:
\foreignlanguage{english}{That person said, ``Hello, world!''}
Therefore, this is puzzling to me...
Best regards,
Shigeru KOBAYASHI
On Tuesday, April 11, 2023 at 2:34:40 AM UTC+9 John MacFarlane wrote:
> I would recommend using unicode curly quotes in the markdown when you're
> working in a language without interword spacing. We rely on interword
> spacing for heuristics about smart quotes.
>
> > On Apr 9, 2023, at 4:53 PM, Shigeru Kobayashi <may...-+k8b35VvZrR3+QwDJ9on6Q@public.gmane.org>
> wrote:
> >
> > Dear Pandoc community,
> >
> > I have encountered two issues regarding Pandoc's handling of quotation
> marks in cases where Japanese and English texts are mixed.
> >
> > I am using Pandoc version 3.1.2 on macOS 12.6.3, and I can reproduce
> these issues. If these are indeed bugs, I am planning to submit them as
> issues on GitHub. However, I would appreciate any guidance if these issues
> arise from my incorrect usage.
> >
> > Issue 1: Conversion of English phrases within Japanese text
> >
> > I have observed the following issue. "input.md" is the input file, and
> "input.tex" is the output file.
> >
> > $ pandoc input.md -o input.tex
> >
> > input.md:
> > その人は"Hello, world!"と言いました。
> >
> > input.tex:
> > その人は''Hello, world!{}``と言いました。
> >
> > However, the conversion is correct when spaces are added before and
> after the double quotation marks.
> >
> > input.md:
> > その人は "Hello, world!" と言いました。
> >
> > input.tex:
> > その人は ``Hello, world!'' と言いました。
> >
> >
> > Issue 2: The quotation marks are treated as Japanese text
> >
> > When converting with Pandoc, the quotation marks are treated as Japanese
> text, resulting in an unnaturally wide gap. I have confirmed this using two
> files, "preamble.tex" and "input.md," and specifying as follows:
> >
> > $ pandoc input.md -o input.pdf --pdf-engine=xelatex -H preamble.tex.
> >
> > preamble.tex:
> > \usepackage{fontspec}
> >
> > \setmainfont{Georgia}
> > \setjamainfont{BIZ UDMincho Medium}
> >
> >
> > input.md:
> > ---
> > documentclass: bxjsarticle
> > classoption: pandoc
> > papersize: a4
> > fontsize: 10pt
> > ---
> >
> > # はじめに
> >
> > その人は "Hello, world!" と言いました。
> >
> > That person said, "Hello, world!"
> >
> > <pandoc test 2023-04-10 8.47.43.png>
> >
> > In contrast, when I directly write the content in TeX and output it
> using $ xelatex test.tex, the quotation marks are treated as English text,
> and the expected output is obtained.
> >
> > test.tex:
> > \documentclass[a4paper,xelatex,ja=standard]{bxjsarticle}
> >
> > \usepackage{fontspec}
> > \setmainfont{Georgia}
> > \setjamainfont{BIZ UDMincho Medium}
> >
> > \title{テスト}
> > \begin{document}
> > \maketitle
> >
> > \section{はじめに}
> >
> > その人は ``Hello, world!'' と言いました。
> >
> > That person said, ``Hello, world!''
> >
> > \end{document}
> >
> > <xelatex test 2023-04-10 8.46.44.png>
> >
> > Shigeru Kobayashi
> >
> >
> > --
> > 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/4a0eafdc-b4a2-4a6a-9488-d2a1c9ef8351n%40googlegroups.com
> .
> > <xelatex test 2023-04-10 8.46.44.png><pandoc test 2023-04-10 8.47.43.png>
>
>
--
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/602edc59-8983-4459-bbbb-85cee5f013b3n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 6316 bytes --]
next prev parent reply other threads:[~2023-04-10 23:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-09 23:53 Shigeru Kobayashi
[not found] ` <4a0eafdc-b4a2-4a6a-9488-d2a1c9ef8351n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-04-10 7:40 ` Bastien DUMONT
2023-04-10 17:34 ` John MacFarlane
[not found] ` <D44375EB-4058-4C5F-AF39-461B38B30EE7-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-04-10 23:30 ` Shigeru Kobayashi [this message]
[not found] ` <602edc59-8983-4459-bbbb-85cee5f013b3n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-04-11 5:32 ` Bastien DUMONT
2023-04-11 5:50 ` Shigeru Kobayashi
[not found] ` <bad8035a-d12b-4ec2-be89-788476948a56n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-04-11 22:01 ` BPJ
[not found] ` <CADAJKhC8hggDWF93mdtd2kYhUhjuBGJ7Jk-q1qx7omm+dCsMXw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-04-11 22:26 ` Shigeru Kobayashi
[not found] ` <94d4f547-ec9b-44bf-9cf0-122d1eea1f02n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-04-12 17:33 ` BPJ
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=602edc59-8983-4459-bbbb-85cee5f013b3n@googlegroups.com \
--to=mayfair-+k8b35vvzrr3+qwdj9on6q@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).