ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Cc: jacko <B_Jackowski@gust.org.pl>
Subject: lijgatures in LM
Date: Sat, 21 Jan 2006 01:10:19 +0100	[thread overview]
Message-ID: <6faad9f00601201610y181280dgdcc313393c042744@mail.gmail.com> (raw)

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

Hello, (the Dutch team),

Is it possible to prevent the "IJ" ligature in ec encoding in LM fonts
in ConTeXt somehow (except with manual intervention in every word
containing IJ)? I checked the behaviour in LaTeX with
\usepackage[T1]{inputenc} with the default font (some kind of Type 1
CM, but not LM), but it seems that only LM changes I and J to a
ligature (grrr ...). With the font in LaTeX it works OK.

"pdftotext" only knows how to convert the LaTeX document properly.
With the document prepared by ConTeXt, it fails to recognize the
ligature properly (searching in Acrobat works however). Besides the
fact that I and J separately (without a ligature) look much better, at
least in Slovenian words.

Thanks,
    Mojca

If any expert for ligatures is reading this: is it fair that "ccaron"
+ "k" ("h") have negative kerning, while "c" + "b" has no kerning at
all? I guess that "ck" was made because of the Germans, but at the
same time I guess that they don't need "čk" at all and I have a
feeling that the caron almost "bumps" into the serif. I compared with
LaTeX, but that font uses a smaller caron. (Without EC encoding
there's no negative kerning after ccaron present anyway.)

[-- Attachment #2: Type: text/plain, Size: 139 bytes --]

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

             reply	other threads:[~2006-01-21  0:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-21  0:10 Mojca Miklavec [this message]
2006-01-21  8:49 ` Taco Hoekwater
2006-01-23 16:20   ` Mojca Miklavec

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=6faad9f00601201610y181280dgdcc313393c042744@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --cc=B_Jackowski@gust.org.pl \
    --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).