ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with ConTeXt (MkIV), Hebrew and ligatures
Date: Mon, 8 Oct 2012 21:10:28 +0200	[thread overview]
Message-ID: <251A28C0-7761-49EC-BC73-E6D7CEFA506C@gmail.com> (raw)
In-Reply-To: <5073209B.2000605@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1534 bytes --]


Am 08.10.2012 um 20:51 schrieb Simo Ojala <smsojala@gmail.com>:

>> On 1-10-2012 19:25, Philipp Gesang wrote:
>> 
>>>> utilities.sequencers.disableaction(resolvers.openers.helpers.textfileactions,"characters.filters.utf.collapse")
>>> 
>>> Doesn’t work. What helps is to comment out the “appendaction” in
>>> char-utf.lua or the corresponding table for U0xfb35 in
>>> char-def.lua. My guess is that this is the case because the .tex
>>> file is processed *before* you can disable it.
>> 
>> so we need a directive (as they can be given on the commandline)
>> 
>> local textfileactions = resolvers.openers.helpers.textfileactions
>> 
>> directives.register("filters.utf.collapse", function(v)
>>     utilities.sequencers[v and "enableaction" or
>> "disableaction"](textfileactions,"characters.filters.utf.collapse")
>> end)
>> 
>> 
>> 
>> Hans
> 
> Sorry to still bother you with this. I just could not get this working. Hopefully it is just that I could not figure out right command line stuff. (I tried out several different ways.) So could somebody tell me how it should be run.
> 
> My guess is something like..
> 
> context --directives=filters.utf.collapse=what_should_i_put_here? testcase.tex
> 
> Thanks,
> 
> Simo
> 
> PS: Both Context setups I tried to get this working (Ubuntu PPA and standalone) should have had code updated. So that should have not been the problem.

Does it work when you add

  \enabledirectives[filters.utf.collapse]

at the begin of your document.

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 2302 bytes --]

[-- Attachment #2: 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:[~2012-10-08 19:10 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
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 [this message]
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=251A28C0-7761-49EC-BC73-E6D7CEFA506C@gmail.com \
    --to=wolfgang.schuster@gmail.com \
    --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).