ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Jan U. Hasecke" <juh+ntg-context@mailbox.org>
To: ntg-context@ntg.nl
Subject: Re: \replaceword and \setreplacements with xml files
Date: Sat, 16 Jan 2016 15:58:36 +0100	[thread overview]
Message-ID: <569A5A9C.3080605@mailbox.org> (raw)
In-Reply-To: <90554673-5F43-40A6-8288-B23C9F125887@uni-bonn.de>

[-- Attachment #1: Type: text/plain, Size: 456 bytes --]

Am 16.01.2016 um 13:31 schrieb Schmitz Thomas A.:
> 
> Please provide a minimal example of your problem. It’s impossible to
> help when we have no clue what you’re doing.

Sorry, of course.

After setting up a mwe I found that it is a font related issue.

When I don't specify a font, it works. --> example.tex

When I choose EB Garamond, it does not work. -- example-Garamond.tex

I confirmed this behaviour in my real setup.

juh



[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: example.tex --]
[-- Type: text/x-tex; name="example.tex", Size: 427 bytes --]

\startbuffer[demo]
<p>auflösen, fließend</p>
\stopbuffer

\startxmlsetups xml:initialize
         \xmlsetsetup{#1}{p}{xml:*}
    \stopxmlsetups

\xmlregistersetup{xml:initialize}

\startxmlsetups xml:p
    \xmlflush{#1}
\stopxmlsetups

\setupbodyfont
    [mainface, 16pt]

\replaceword[sellig][auflösen][au{fl}ösen]
\setreplacements[sellig]

\starttext
     \xmlprocessbuffer{main}{demo}{}
\stoptext

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: example-Garamond.tex --]
[-- Type: text/x-tex; name="example-Garamond.tex", Size: 493 bytes --]

\startbuffer[demo]
<p>auflösen, fließend</p>
\stopbuffer

\startxmlsetups xml:initialize
         \xmlsetsetup{#1}{p}{xml:*}
    \stopxmlsetups

\xmlregistersetup{xml:initialize}

\startxmlsetups xml:p
    \xmlflush{#1}
\stopxmlsetups

\definefontfamily
    [mainface]
    [rm]
    [EB Garamond]

\setupbodyfont
    [mainface, 16pt]

\replaceword[sellig][auflösen][au{fl}ösen]
\setreplacements[sellig]

\starttext
     \xmlprocessbuffer{main}{demo}{}
\stoptext

[-- Attachment #4: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2016-01-16 14:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-16 11:24 Jan U. Hasecke
2016-01-16 12:31 ` Schmitz Thomas A.
2016-01-16 14:58   ` Jan U. Hasecke [this message]
2016-01-17 19:05     ` Hans Hagen
2016-01-18  6:31       ` Jan U. Hasecke
2016-01-18 10:12         ` Hans Hagen
2016-01-18  9:16       ` Ligatures in EB Garamond (was: \replaceword and \setreplacements with xml files) Jan U. Hasecke
2016-01-18 10:09         ` Ligatures in EB Garamond Hans Hagen
2016-01-18 12:46           ` Jan U. Hasecke
2016-01-18 19:22             ` 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=569A5A9C.3080605@mailbox.org \
    --to=juh+ntg-context@mailbox.org \
    --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).