Changes

by Prof. [[User:Ishamid|Idris Samawi Hamid]] __TOC__

[[Aleph ]] is a typesetting engine derived from Omega and eTeX. Reasons for Aleph:

The ConTeXt module for this setup is called ''Gamma'' ([[source:m-gamma.tex|m-gamma.tex]]); this is a port of the ''Lambda'' (i.e., LaTeX) style files to ConTeXt. The font typescript is called type-omg.

* Make sure you have a very recent version of ConTeXt that supports the engine path mechanism. This mechanism allows <tt>texexec </tt> to manage two, e.g., <tt>cont-en.fmt </tt> files at once, one in <code>texmf/web2c/aleph</code> and one in <code>texmf/web2c/pdfetex</code>

How recent, you ask? Just be safe and get the latest <tt>:-)</tt>

a. Make sure you have the following line in ConTeXt\tex\texmf-local\context\config\texexec.ini set to "true", viz., set UseEnginePath to true b. In texmf-local\web2c\texmf.cnf,texmf-local\web2c\context.cnf, andtexmf\web2c\texmf.cnf, comment this line as follows %extra_mem_bot.context = 2000000 otherwise aleph will crash under some conditions, like overfull boxes and the like... The XeTeX developer found the source to this bug, and a fix; hopefully Giuseppe will get to it-)) 3. Get the omega support files: http://www.ctan.org/get?fn=/systems/win32/fptex/0.7/package/omega.ziphttp://www.ctan.org/get?fn=/systems/win32/fptex/0.7/package/omegafonts.zip 4. Get rid of the following directories from omega.zip (not really necessary but if u want to beefficient): texmf/eomegatexmf/omega/encodings 5. Put support files in texmf-local; 6. Compile the Aleph format: mktexlsr texexec --make en -tex=aleph 7. Here is a test file. Note the preamble % tex=aleph output=dvipdfmx at the beginning of every aleph Aleph file.

'''===omarb.tex'''===

\input m-usemodule[gamma.tex]\input type-omg.tex% perhaps \usetypescriptfile[type-omg] ?

8. * For Arabic script you will probably want to use an [[Encodings_and_Regimes|encoding ]] that supports direct Arabic-script editing. There are three: utf-8, iso-8859-6 (apple-unixApple/Unix), and cp1256 (micro$oftMicrosoft). We can define the following, using ConTeXt macros for managing filter sequences. Maybe I will add these to [[source:m-gamma -tex|m-gamma]] and ask [[User:Hagen|Hans ]] to distribute. In the meantime, here are some definitions, samples of all three encodings, and an example of mixed lr-rl text:

'''===m-arabic-enc.tex'''===

%\input m-usemodule[gamma.tex\input type-omg.tex]

\def\ArabicTextUTF#1{definestartstop [arabictextutf] [commands=% {\textdir TRT\usefiltersequence[UTFArabic]% \switchtobodyfont[omarb]#1\textdir TLT% \clearocplists}usefiltersequence[UTFArabic]}]

\def\ArabicTextISO#1{definestartstop [arabictextiso] [commands=% {\textdir TRT\usefiltersequence[ISOArabic]% \switchtobodyfont[omarb]#1\textdir TLT% \clearocplists}usefiltersequence[ISOArabic]}]

\def\ArabicTextWIN#1{definestartstop [arabictextwin] [commands=% {\textdir TRT% \usefiltersequenceswitchtobodyfont[WINFArabicomarb]% \switchtobodyfontusefiltersequence[omarbWINArabic]}] \def\ArabicTextUTF#1{\textdir TLTstartarabictextutf#1\stoparabictextutf}  \clearocplistsdef\ArabicTextISO#1{\startarabictextiso#1\stoparabictextiso} \def\ArabicTextWIN#1{\startarabictextwin#1\stoparabictextwin}

Here is some mixed {\em Arabic-} (\ArabicTextUTF{عربيعربي}) and

{\em LR} (\ArabicTextUTF{يساريسار-يمينيمين}) and {\em RL}(\ArabicTextUTF{يمينيمين-يساريسار}) texts. \ArabicTextUTF{Ùˆوهنا جملة منقطعة في وسط قرينةهنا جملة منقطعة في وسط قرينةلاتينيةلاتينية}. Aleph even does a great job breaking Arabic

The last example shows how to make and apply your own filter sequences beyond the basic Gamma module. To go further u need to learn some low* [[File:Utilities-level businessaleph. You will also need some working zip|utilities-aleph. I have put together a windows package that you can unzip to C:\ConTeXt. These utilities do work, but they are cobbled together from old fpTeX and MiKTeX versions. just place the tree in C:\ConTeXt\zip]]

1The last example shows how to make and apply your own filter sequences beyond the basic Gamma module. To go further you need to learn some low-level business. You will also need some [[File:Utilities-aleph.zip|working utilities]]. I have put together a windows package that you can unzip to <tt>C:\ConTeXt</tt>. These utilities do work, but they are cobbled together from old fpTeX and MiKTeX versions. ===Example: If you want to get the final Persian kaaf instead of the default Arabic one:===

 C:\ConTeXt\tex\ texmf-local\/fonts\/type1\/public\/omega  omsea1, omsea1b,...omsea3b

 C:\ConTeXt\tex\<tt>texmf-local\/omega\/lambda\/misc</tt>

 <tt>omarab.cfg</tt>

04AA N kafswashfin

%@"E343 => @"04AA;

% remaining Arabic glyphs @"E000-@"E3FF => #(\1 - @"DF00);

Basically, in <tt>uni2cuni.otp </tt> final-kaaf gets mapped to E343. In the font, we want it mapped to kafswashfin, so we did that. Now recompile the otp:

otp2ocp cuni2oar

2. ===Want new fonts (Arabic or Latin). ? Here are the instructions:===

1. * Read the following two papers carefully again and again; they are your friends:-)** [http://omega.enstb.org/papers/tsukuba-methods97.pdf tsukuba-methods]** [http://omega.enstb.org/papers/ridt-omega98.pdf ridt-omega]* Make a pfb file containing the glyphs you need, or use an existing font* Make a cfg file a la <tt>texmf\omega\lambda\misc\omlgc.cfg</tt>. Make sure you list your glyph positions in hexadecimal notation.* Get <tt>makeovp.pl</tt> from the utilities. I made some small changes, <tt>makeovp2.pl</tt>. Try them both and use what works for you. There is a SH file with a sample of its use using omlgc. * Following are instructions for cooking omarab.ovf.** You want your own ovf, say, omlgcch.ovf.** Generate an afm file for your private glyph pfb/pfa plus the afm files that are listed in the SH file (base files for omlgc found in <tt>\texmf\fonts\afm\public\omega</tt>)** Using the instructions below and the SH file ('''ignore''' the kernings.afm file!) you can figure out how to make your own ovp and ovf.** Before making the ovf file, examine the ovp file created, especially the first few lines, to see how the font-metric info from the afm's are concatenated. Very instructive.* Don't forget the rest of the accounting:** adding lines to a map file and pointing dvips/dvipdfm to it;** create a typescript file;** edit your otp's. If you get stuck be sure to read [http://omega.enstb.org/papers/tsukuba-arabic97.pdf tsukuba-arabic]

http====How to cook omarab.ovf====Ingredients://omegaomarab.enstbcfg, omseco.org/papers/tsukuba-methods97.pdfhttp://omegaafm, omsea1.enstbafm, omsea2.org/papers/ridt-omega98afm, omsea3.pdfafm

2 > perl makeovp. Make a pfb file containing the glyphs you need, or use an existing fontpl omarab.cfg omseco.afm omsea1.afm omsea2.afm omsea3.afm omarab.ovp > pltotf omseco.pl omseco.tfm > pltotf omsea1.pl omsea1.tfm > pltotf omsea2.pl omsea2.tfm > pltotf omsea3.pl omsea3.tfm > ovp2ovf omarab.ovp omarab.ovf omarab.ofm

5 > ovp2ovf omarab. Get the following from an old TeXLive distro: \support\makeovpovp omarab.zip, containing makeovp.pl. There is a SH file with a sample of its use using omlgcovf omarab.tfm

4rename omarab. Following are instructions for cooking tfm to omarab.ovf. You want your own ovf, say, omlgcch.ovf (<chofm --> for <cherokee>). Generate an afm file for your private glyph pfb/pfa plus the afm files that are listed in the SH file (base files for omlgc found in \texmf\fonts\afm\public\omega )ofm directory

Using the instructions below and the SH file (IGNORE the kernings====How to distill omarab.afmfile!) you can figure out how to make your own ovp and from omarab.ovf. Before:====making the ovf file, examine Use a different directory or a different name for the output ovp so that omarab.ovp file created, especially thefirst few lines, to see how the font-metric info from the afm's areconcatenated. Very instructiveabove is not overwritten.

6get omarab. Don't forget the rest of the accounting:ofm & rename to omarab.tfm

a) adding lines to a map file and pointing dvips/dvipdfm to it;b) create a typescript file;c) edit your otp's > ovf2ovp omarab. If u get stuck be sure to readovf omarab.tfm omarab.ovp

http====How to cook omarabb.ovf====Ingredients://omegaomarab.cfg, omsecob.afm, omsea1b.enstbafm, omsea2b.org/papers/tsukuba-arabic97afm, omsea3b.pdfafm

<code >[How to cook omarabperl makeovp.ovf:][Ingredients: pl omarab.cfg, omsecoomsecob.afm, omsea1omsea1b.afm, omsea2omsea2b.afm, omsea3omsea3b.afm]omarabb.ovp > pltotf omsecob.pl omsecob.tfm > pltotf omsea1b.pl omsea1b.tfm > pltotf omsea2b.pl omsea2b.tfm > pltotf omsea3b.pl omsea3b.tfm > ovp2ovf omarabb.ovp omarabb.ovf omarabb.ofm

[If the last line does not work, try#ovp2ovf omarab.ovp omarab.ovf omarab.tfmrename omarab.tfm to omarab.ofm ===> ofm directory]

-----------------------------[How to distill omarab > ovp2ovf omarabb.ovp from omarabomarabb.ovf:]omarabb.tfm

[Use a different directory or a different name forthe output ovp so that rename omarab.tfm to omarab.ovp created above is not overwritten]ofm --> ofm directory

[get omarab====How to distill omarabb.ofm & rename to omarabovp from omarabb.ovf====Use a different directory or a different name for the output ovp so that omarabb.tfm]ovp created above is not overwritten

#ovf2ovp get omarab.ovf ofm & rename to omarab.tfm omarab.ovp=========================================================[How to cook omarabb.ovf:][Ingredients: omarab.cfg, omsecob.afm, omsea1b.afm, omsea2b.afm, omsea3b.afm]

#perl makeovp > ovf2ovp omarabb.pl omarab.cfg omsecob.afm omsea1b.afm omsea2b.afm omsea3b.afm ovf omarabb.ovp#pltotf omsecob.pl omsecob.tfm#pltotf omsea1b.pl omsea1b.tfm#pltotf omsea2b.pl omsea2b.tfm#pltotf omsea3b.pl omsea3b.tfm#ovp2ovf omarabb.ovp omarabb.ovf omarabb.ofm

[If the last line does not work, try#ovp2ovf omarabb.ovp omarabb.ovf omarabb.tfmrename omarab.tfm to omarab.ofm ===> ofm directory]-----------------------------[How to distill omarabb.ovp from omarabb.ovf:] [Use a different directory or a different name forthe output ovp so that omarabb.ovp created above is not overwritten] [get omarab.ofm & rename to omarab.tfm] #ovf2ovp omarabb.ovf omarabb.tfm omarabb.ovp</code> 3. * For more info, there is also the (mostly cryptic) Omega manual [http://omega.enstb.org/roadmap/doc-1.12.ps in PS-Format]. Don't ask me why it's not in PDF. <tt>:-(</tt> See also [http://omega.enstb.org/papers/tsukuba-arabic97.pdftsukuba-arabic]

# * Some people have gotten large OpenType fonts to work in Aleph/Omega. Probably they used [http://fontforge.sourceforge.net FontForge ] to convert to CFF-enriched type1. FF can produce ofm files (large tfms) so that's a help too.# * Me, I'm working on an advanced Arabic-script typesetting system that really pushes Aleph to the max. At present I don't actually use [[source:m-gamma.tex|m-gamma]], etc, but my own macros. I really hope to release something this year...#* See also [http://www.dtek.chalmers.se/~d97ost/omega-example.htmlOmega example]

# * The otp mechanism does not seem well suited to support, e.g., opentype OpenType GPOS tables, important for really advanced Arabic (though GDEF and GSUB should work fine with the present mechanism for most purposes). We need a better model for horizontal and vertical glyph substitutions.# * The low-level filtersequence mechanism needs to abstract language processing from font mapping. Right now both are hardwired into a single sequence, so setting up more than one font for a single language is more of a pain than it should be.# * The otp language is a bit cryptic. Hans has suggested switching otp's to a new language (like lua or io) but I don't know how hard that will be...# * One very important feature which may work better at the primitive/engine level by extending the pdfetex pdfeTeX engine:glyph substitution that depends on the paragraph. For example: In traditional Arabic typography, one way to compensate for "underfull" paragraphs is to substitute a "swash" version of a letter. Another way is bystretching the cursive tie between joining characters (which is already implemented in my own Arabicsystem). Combined with HZ we can get some pretty interesting high-level options, effects, etc. that the user can choose etc. {{Installation navbox}}