ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Simo Ojala <smsojala@gmail.com>
Subject: Re: Problem with ConTeXt (MkIV), Hebrew and ligatures
Date: Fri, 28 Sep 2012 10:46:54 +0200	[thread overview]
Message-ID: <506563FE.9040607@wxs.nl> (raw)
In-Reply-To: <5064A89F.6030402@gmail.com>

On 27-9-2012 21:27, Simo Ojala wrote:
> This is a problem originally posted in TeX/StackExchange. However, since
> I have not had any luck in finding a solution I post it here too. I am
> confident that somebody here should know the answer.
>
>
> http://tex.stackexchange.com/questions/73970/problem-with-context-mkiv-hebrew-and-ligatures
>
>
> "Since I last played with the latest ConTeXt MkIV, there has been
> introduced this new feature. It now seems to combine Hebrew characters
> automatically when possible to ligatures. So for example. If I have a
> word with following two characters:
>
> U+05D5 (HEBREW LETTER VAV)
> U+05BC (HEBREW POINT DAGESH OR MAPIQ)
>
> ConTeXt will combine these to:
>
> U+FB35 (HEBREW LETTER VAV WITH DAGESH)
>
> However, I would need to disable this feature for a number of reasons.
> For example, this breaks my little database query, because the query key
> is changed before(?) macro gets it.
>
> So if somebody would know how to turn this off and maybe also that what
> has changed."

It depends on the font ... normally you can disable this by *not* using 
the mark and mkmk features

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2012-09-28  8:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-27 19:27 Simo Ojala
2012-09-28  8:46 ` Hans Hagen [this message]
2012-09-28 23:41   ` Simo Ojala
2012-09-29 11:35     ` Hans Hagen
2012-10-01 15:16       ` Simo Ojala
2012-10-01 16:23         ` Philipp Gesang
2012-10-01 16:43           ` Hans Hagen
2012-10-01 17:25             ` Philipp Gesang
2012-10-01 17:39               ` Hans Hagen
2012-10-01 20:18                 ` Philipp Gesang
2012-10-01 20:52                   ` Hans Hagen
2012-10-08 18:51       ` Simo Ojala
2012-10-08 19:10         ` Wolfgang Schuster
2012-10-10  0:17       ` Simo Ojala
2012-10-10  7:36         ` Sietse Brouwer
2012-10-11  0:52       ` Simo Ojala

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=506563FE.9040607@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    --cc=smsojala@gmail.com \
    /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).