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>
Subject: Re: Arabic script bug in MKIV
Date: Fri, 17 Oct 2008 21:48:31 +0200	[thread overview]
Message-ID: <48F8EC0F.7010507@wxs.nl> (raw)
In-Reply-To: <6048c4180810170204s39cb8d58i649105df49a63ed3@mail.gmail.com>

Mehdi Omidali wrote:
> Hi everyone
> At last I could install minimal context to use the latest luatex
> (0.30.1) with latest cont-tmf release. Thanks.
> I don't know if the following is a luatex or Context bug. Sorry if
> here is not the right place to report this.
> After compiling the following lines I faced two problems in the output.
> 1- In the first line words get mixed.
> 2- In the second line only 456 appeared but it should be 0123456789.
> The second problem occurs for the specific font that I have used and I
> can resolve it by using another font. The problem is that in the font,
> the character ۱ for example is assigned to two unicode characters, one
> for U+0661 (arabic digit one) and also for U+06F1 (farsi digit one).
> But MKIV doesn't know this approach. In fact, only digits 4,5, and 6
> are different in farsi and arabic so they appeared in the output
> correctly. XeTeX knows this kind of character assignment.

so, how does the font communicate this dual usage?

> \definestartstop
>   [farsidocument]
>   [commands={\usetypescript[Farsi]%
> 	\setupbodyfont[Farsi,12pt]%
> 	\FarsiGlobalDir}]
> 

way more efficient

\usetypescript[Farsi]

\definestartstop[farsidocument][commands={\switchtobodyfont[Farsi]\FarsiGlobalDir}]



-----------------------------------------------------------------
                                           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
-----------------------------------------------------------------
___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      parent reply	other threads:[~2008-10-17 19:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17  9:04 Mehdi Omidali
2008-10-17 13:36 ` Taco Hoekwater
2008-10-17 19:48 ` Hans Hagen [this message]

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=48F8EC0F.7010507@wxs.nl \
    --to=pragma@wxs.nl \
    --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).