ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Andreas Harder <aharder@uni-koblenz.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Ligatures
Date: Sat, 26 Dec 2009 15:33:30 +0100	[thread overview]
Message-ID: <A7E30113-E6C5-4468-9077-3A8C565AD7CB@uni-koblenz.de> (raw)
In-Reply-To: <alpine.DEB.1.00.0912261508120.10209@hahepc1.hahe>

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

Hi,

can someone confirm the misbehaviour with ligatures in my example? It’s there since the last three or four betas, perhaps longer.


[-- Attachment #2: test-ligatures2.tex --]
[-- Type: application/octet-stream, Size: 791 bytes --]


%\mainlanguage[de]

\definefontfeature[default][default][mode=node] % -> not OK
% \definefontfeature[default][default][mode=base] % -> OK

\usetypescript[palatino]
\setupbodyfont[palatino]

\startbuffer
  Begriff, Begriffsbestimmung, Integrationsbegriff, Öffentlichkeit,
  Eröffnung, erhoffte, die Betroffenen, getroffenen, ergriffen,
  auffällig, trifft, hoffen, Aufforderung, Begrifflichkeit.
  
  Häufig, Wohlbefinden, offiziell, Identifikation, signifikant,
  modifiziert, qualifiziert, offiziell.
  
  Pflicht, dörflich, höflich, fliegen, pflanzen, Einfluss, pflegen,
  behilflich.
  
\stopbuffer


\starttext 

\startTEXpage[offset=1em]
  \getbuffer
\stopTEXpage

\stoptext

%%% Local Variables: 
%%% mode: context
%%% TeX-master: t
%%% End: 

[-- Attachment #3: test-ligatures2.pdf --]
[-- Type: application/pdf, Size: 15617 bytes --]

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



Greetings
	Andreas

[-- Attachment #5: Type: text/plain, Size: 486 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
___________________________________________________________________________________

  parent reply	other threads:[~2009-12-26 14:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-25 16:31 font expansion Wolfgang Schuster
2009-12-26 13:10 ` Hans Hagen
2009-12-26 13:20   ` Taco Hoekwater
2009-12-26 13:44   ` luigi scarso
2009-12-26 13:52     ` Hartmut Henkel
2009-12-26 14:03       ` luigi scarso
2009-12-26 14:09         ` Hartmut Henkel
2009-12-26 14:18           ` luigi scarso
2009-12-26 14:27             ` Hartmut Henkel
2009-12-26 14:30               ` luigi scarso
2009-12-26 14:32               ` Hans Hagen
2009-12-26 19:24                 ` luigi scarso
2009-12-26 14:33           ` Andreas Harder [this message]
2009-12-26 14:39             ` Ligatures Khaled Hosny
2009-12-26 14:45               ` Ligatures Andreas Harder
2009-12-26 14:46             ` Ligatures Hans Hagen
2009-12-26 15:25   ` font expansion Wolfgang Schuster
2009-12-26 14:50 Ligatures Andreas Harder

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=A7E30113-E6C5-4468-9077-3A8C565AD7CB@uni-koblenz.de \
    --to=aharder@uni-koblenz.de \
    --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).