ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: arab (omega)
Date: Sun, 25 Jun 2006 18:01:03 +0200	[thread overview]
Message-ID: <449EB33F.5000704@wxs.nl> (raw)
In-Reply-To: <op.tbnuoz06nx1yh1@walayah-main>

Idris Samawi Hamid wrote:
> I found the problem:
>
> In uni2cuni.otp the numbering handling does two things:
>
> It DOES isolate non-numerals as separators within a given expression. So  
> placing an Arabic letter between two numbers
>
> 5792ر684
>
> processes fine; each individual number gets reversed.
>
> But the otp makes exceptions for the following punctuation:
>
> + - .
>
> If we get rid of those exceptions the separator problem will go away. But  
> then math will be messed up. The problem is that the
>
> + - .
>
> are ambiguous; sometimes they have a mathematical significance; sometimes  
> a separator significance. We need the exception for math (generally done  
> the usual l-r way) but don't need it for separators (done in the r-l way).
>   
isn't it simplier then to disable otp's in math mode
> What I could do is define two filter sequences: UTFArabic and  
> UTFArabicMath. Hans, could you do a conditional that calls up one in math  
> mode and the other everywhere else?
>   

\appendtoks
    < reset otps >
   < intialize other sequence of thenm> 
\to \everymathematics
> This is a stop-gap solution until we replace otp's with something smarter.  
> Taco, Hans, let me know what you think before I work on this.
>
> It is really inefficient to have to define an entire ot stack just to  
> change one otp. There must be a better way to abtract things so we can  
> plug a given otp without redoing the entire stack.
>   
i suppose that switching is fast, so using a different stack was what came on my mind first

Hans 

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------

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

  parent reply	other threads:[~2006-06-25 16:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23 18:59 Hans Hagen
2006-06-24 16:37 ` Idris Samawi Hamid
2006-06-24 17:25   ` Idris Samawi Hamid
2006-06-25  8:08     ` Taco Hoekwater
2006-06-25 17:38       ` Idris Samawi Hamid
2006-06-25 19:54         ` Idris Samawi Hamid
2006-06-25 16:01     ` Hans Hagen [this message]
2006-06-25 18:34       ` Idris Samawi Hamid
2006-06-25  6:37   ` Taco Hoekwater
2006-06-25 15:57   ` Hans Hagen
     [not found] <mailman.196.1151291766.1824.ntg-context@ntg.nl>
2006-06-26  7:56 ` Duncan Hothersall
2006-06-26 20:14   ` Idris Samawi Hamid
2006-06-26  9:59 ` Duncan Hothersall
2006-06-26 14:21   ` 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=449EB33F.5000704@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    --cc=taco@elvenkind.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).