From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug with ligatures (EBGaramond) and \mainlanguage[es]
Date: Thu, 26 Mar 2015 07:10:03 +0100 [thread overview]
Message-ID: <5513A2BB.2040205@gmx.es> (raw)
In-Reply-To: <551397CD.8040807@chiquitico.org>
On 03/26/2015 06:23 AM, Andrés Conrado wrote:
> Hello, list. When I try to use the EBGaramond font
> (http://www.georgduffner.at/ebgaramond/) in spanish (using
> \mainlanguage[es]), ligatures disappear. But they only disappear when
> they belong to a word (when alone, they look fine). See MWE, if you
> remove the comment in the \mainlanguage command, ligatures get screwed up:
Hi Andrés,
I’m afraid this is a proper bug.
It isn’t related to Spanish as language. The bug is triggered when a the
ligature has a hyphenation point at the end.
Here is another mininmal example with German as main language:
\mainlanguage[de]
\loadtypescriptfile[ebgaramond]
\setupbodyfont[ebgaramond,24pt]
\starttext
\hsize\zeropoint
figura afigura
\es figura afigura
\en figura afigura
\stoptext
German only inserts a hyphenation point after three characters (and
before other three characters). This is why the first word has the
ligature and the second word doesn’t have it.
English doesn’t show the bug, because it doesn’t find any hyphenation
point in the words.
Until this is fixed, you may use the new hyphenator. You need a fairly
new beta. Add the following lines at the top of your preamble:
\setuphyphenation[method=traditional]
\sethyphenationfeatures[strict]
I hope it helps,
Pablo
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> % remove the comment below to see the effect on ligatures.
> %\mainlanguage[es]
>
> \loadtypescriptfile[ebgaramond]
>
> \setupbodyfont[ebgaramond,48pt]
>
> \starttext
>
> flagrantemente y figurativamente ff fl fi ffi ffl ffii figura ffla fflego
>
> \stoptext
> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>
>
> Thanks for any ideas you may have, I'm clueless, and really need to use
> those ligatures. I can edit whatever needs to be edited, but I can't
> find any ideas in the source, nor the mailing list.
>
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
>
--
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2015-03-26 6:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.113.1420704407.2429.ntg-context@ntg.nl>
2015-03-26 5:23 ` Andrés Conrado
2015-03-26 6:10 ` Pablo Rodriguez [this message]
2015-03-26 13:47 ` Hans Hagen
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=5513A2BB.2040205@gmx.es \
--to=oinos@gmx.es \
--cc=ntg-context@ntg.nl \
/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).