From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/2753 Path: main.gmane.org!not-for-mail From: "Behnam Tabatabai" Newsgroups: gmane.comp.tex.context Subject: Re: Example for Persian Date: Mon, 18 Sep 2000 16:08:08 CEST Sender: owner-ntg-context@let.uu.nl Message-ID: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Trace: main.gmane.org 1035393529 11564 80.91.224.250 (23 Oct 2002 17:18:49 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 17:18:49 +0000 (UTC) Cc: ntg-context@ntg.nl Original-To: pragma@wxs.nl Xref: main.gmane.org gmane.comp.tex.context:2753 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:2753 Hi Hans! Thank you for having examined my Persian exmaple! >Your file says: > >\font\OMARAB=omarab > >far better is a definition like > >\definefont[OMARAB][omarab sa 1] > That's right. I have still very little experience in Context, that's why I chose the most straightforward way of switching to "omarab". In the next examples I'll use this construct. > >Then there is the OTP mechanism, which chains a series of filters. Whet we >need there is something similar, like (maybe we can leave the synonym here, >and auto resolve indirect mappings) > >\definefiltersynonym [OTF8 to UNICODE16] [inutf8] >\definefiltersynonym [farsi to arabic] [FarsiToArabic] >\definefiltersynonym [preprocess arabic] [uni2cuni] >\definefiltersynonym [build arabic glyphs] [cuni2oar] > >next there is: > >\definefiltersequence[Farsi][OTF8 to UNICODE16, farsi to arabic, preprocess >arabic, build arabic glyphs] > Besides "normal" OTP's Omega can also use so called "external" OPT's, which are any executables (perl scripts, ...) acting as filters. These can also be interfaced by similar macros. >[what is the 1000 in \ocplist\OCPListFarsiUTF=\addbeforeocplist 1000 >\OCPutf ?] > This a positive value which can be used to fine tune the bahavior of \pushocplist in respect of the final placement of ocp's in the list. A detailed description can be found in the Omega documentation doc-1.8.dvi, pp. 31-34. Personally I have not seen any real examples using this feature: All examples I have seen so far use 1 or 1000 uniquely for all ocp's added to the list. >now we can say: > >\Farsi\OMARABIC > >and get thoce nice sequences of glyphs. In this way we can hide the otp >interface and protect macros. > Well, this example was a more or less brute force hack for getting Farsi with the help of Omega primitives. Relying on these Omega features (direction switching commands and OTP's) do you see any chances for a more structured support in future versions of Context (e.g., a "lang-far.tex")? Regards, Behnam _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com.