public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Pablo Rodríguez" <oinos-S0/GAf8tV78@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Ancient Greek in output PDF
Date: Fri, 27 Jan 2017 18:02:23 +0100	[thread overview]
Message-ID: <ec531451-39f0-109f-c64f-be594acedab1@web.de> (raw)
In-Reply-To: <736ec0e9-a251-4e0c-90c6-b9e2c314532b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

On 01/26/2017 01:50 AM, John Muccigrosso wrote:
> The only drawback I see here is that you have to clearly mark out the
> Greek in your markdown, whereas, if you're happy with the appearance of
> the Greek characters in your chosen font, you don't have to do anything
> and they just appear. (The impetus for my question came from someone
> wanting - I think - to turn fairly simple text files into nice-looking
> PDFs automatically.)

You don’t need language tagging in the source text for PDF generation
either with LaTeX or with ConTeXt.

A fallback font works exactly like that: you define the typeface you
need for the Unicode ranges you need (Greek and Greek extended being
just two of them). I provided the right command for polyglossia.

If hyphenation is also desired, in ConTeXt you may load different
hyphenation patterns for one language, such as in:

    \setuplanguage[en][patterns={en, agr}]
    \setupbodyfont[dejavu]
    \starttext
    \hyphenatedword{processor μηχανή}

    \hyphenatedword{processor \agr μηχανή}
    \stoptext

Altought you have the same minimal number of letters for the first and
last hyphen in the word as the “parent” language (as shown in the second
line).

You might achieve this in LaTeX too.

> Here's my ideal (I think): pandoc is smart enough to see a block of
> Greek text and your Greek font gets applied to it. That seems a bit
> unlikely, but I wonder how hard it would be to create a filter that uses
> regex to look for Greek text and surround it with the appropriate tags.

If the filter is required for PDF generation only, I think it isn’t
required. I would love to have proper language tagging in pandoc-2.0,
such as in:

    [καλόν]{:grc} means “beautiful”.

I mean, :lang is way more useful for real language mixing. Of course, I
may type [καλόν]{lang="grc"}, but this isn’t lightweight (see
https://github.com/jgm/pandoc/issues/895).

Just in case it helps,


Pablo
-- 
http://www.ousia.tk

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/ec531451-39f0-109f-c64f-be594acedab1%40web.de.
For more options, visit https://groups.google.com/d/optout.


  parent reply	other threads:[~2017-01-27 17:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19 16:08 John Muccigrosso
     [not found] ` <45028ac1-86cf-40ee-b3b8-7560eb9dce47-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-19 19:14   ` John MacFarlane
     [not found]     ` <20170119191417.GD96884-l/d5Ua9yGnxXsXJlQylH7w@public.gmane.org>
2017-01-20  4:33       ` John Muccigrosso
     [not found]         ` <20f5af55-daf5-443c-9c5f-085b4b816ce1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-20  9:04           ` John MacFarlane
2017-01-24 17:36   ` Pablo Rodríguez
     [not found]     ` <91f1b15e-860d-8b35-1451-aca9fdf4ec45-S0/GAf8tV78@public.gmane.org>
2017-01-24 18:53       ` John Muccigrosso
     [not found]         ` <67ea3fe7-0d6b-4ad2-8010-d69295cba0b8-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-25  8:41           ` Scot Mcphee
2017-01-24 19:15       ` John Muccigrosso
     [not found]         ` <631d8a2d-12a0-4dbd-ad98-6988e9db6d54-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-24 19:49           ` Pablo Rodríguez
2017-01-25 17:46           ` BP Jonsson
     [not found]             ` <920a0f68-a164-53aa-b3bb-224307772512-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-01-26  0:50               ` John Muccigrosso
     [not found]                 ` <736ec0e9-a251-4e0c-90c6-b9e2c314532b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-26 13:32                   ` Melroch
2017-01-27 17:02                   ` Pablo Rodríguez [this message]
     [not found]                     ` <ec531451-39f0-109f-c64f-be594acedab1-S0/GAf8tV78@public.gmane.org>
2017-01-28 18:52                       ` John Muccigrosso
     [not found]                         ` <3177084b-b814-4bf5-859f-c74650df775a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-28 19:29                           ` Andrew Dunning
     [not found]                             ` <e2f300d1-b5dd-41df-b81f-11d05516bc00-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-01-29 13:38                               ` BP Jonsson
     [not found]                                 ` <CAFC_yuQLyx_dUoMkY32OXT=-CmX9US5veLZdo87mvoD-OaUfzA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-29 16:53                                   ` John Muccigrosso
2017-01-29 16:51                               ` John Muccigrosso

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=ec531451-39f0-109f-c64f-be594acedab1@web.de \
    --to=oinos-s0/gaf8tv78@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).