May 2013 - ntg-context - NTG Mailing Lists

Re: [NTG-context] Installing an arabic font
by "H. Özoguz" 09 May '13

09 May '13

> The font is fine with other > OpenType engines as well, e.g. HarfBuzz, so it is probably a ConTeXt > issue. Yes, the font is fine with OpenOffice, too. It would be really great, if this could be fixed in context, so one could typeset quran (and other traditional arabic) professionally. Would be very valuable! Huseyin

2 1

Re: [NTG-context] Installing an arabic font
by "H. Özoguz" 09 May '13

09 May '13

> seems like an issue with liga ... i'm not sure if that's a context problem Hmm, see in the attachment the output of MS-Word, with activated ligatures. So it has to do anything with ConText, or not? Or maybe this font uses in some way properties of Word in handling fonts? Huseyin

3 2

LuaJitTeX, \texenginename, and \texengineversion
by Kip Warner 08 May '13

08 May '13

Hey Luigi, I find the \texenginename and \texengineversion useful for retrieving the backend name and version. They work fine when using the vanilla LuaTeX backend. However, when using LuaJitTeX, the aforementioned macros still seem to retrieve LuaTeX specific information and not LuaJitTeX - unless I'm doing something wrong. I was careful to ensure I passed --engine=luajittex to context as well. -- Kip Warner -- Software Engineer OpenPGP encrypted/signed mail preferred http://www.thevertigo.com

4 5

Re: [NTG-context] Installing an arabic font
by "H. Özoguz" 08 May '13

08 May '13

> Rename the file to have a .ttf extension; it is and OpenType font with > TrueType outlines and those usually have .ttf extension (though the > spec says they can have .otf extension, ConTeXt does not handle this > right now). > > Regards, > Khaled Thanks Khaled, now it works, at least to some degree. I have still problems, which I dont have with MS Word, see this example: \definefont[amiri][file:UthmanTN1Ver10.ttf*arabic at 17 pt] \define[1]\Arab{\setupalign[r2l]\amiri#1} \starttext \Arab{ نَسْتَعِينُ وَلَا الضَّالِّينَ } \stoptext The vocalisations are set wrong, see attachment. Specially with a final "nuun" there are problems. It is not a problem of the font, because in Word they are set correctly. Does this come from the extensions ConTeXt do not support, or is there an easy way to fix? Or asked more generally, if fixing is not possible: Do you know any font, which can correct handled by context, and is capable of typesetting quran? Thanks. Huseyin

2 1

Installing an arabic font
by "H. Özoguz" 08 May '13

08 May '13

Hoping to annoy not everybody here with my arabic-font-questions. I have found I nice free arabic ttf-font, you can download it here: http://fonts.qurancomplex.gov.sa/wp-content/uploads/2012/06/UthmanTN1-Ver10…. One of its types is: "kfgqpcuthmantahanaskhregular" If I type in the cmd C:\Users\Hussein>mtxrun --script font --list --all --pattern=*kf* I get (together with some other lines/fonts): kfgqpcuthmantahanaskhregular kfgqpcuthmantahanaskh c:/windows/fonts/UthmanTN1 Ver10.otf So everything should be ok. But now the following failes: \definefont[amiri][name:kfgqpcuthmantahanaskhregular*arabic at 17 pt] \define[1]\Arab{\setupalign[r2l]\amiri#1} \starttext \Arab{ بِسْمِ ‏للهِ الرَّحْمَـٰنِ الرَّحِيمِ } \stoptext It compiles, but the output is destroyed, the letters have distances between them. See attached pdf. (In other programms, e.g. MS Word that does not happen, and the font is set correctly.) Apart from this mistake, the font is perfect set by context, even the "Allah" and its "Kassra" has a nice distance (see the other thread). Indeed, if this distace-between-letters problem could be solved, I am happy with arabic in context, this font would be enough, and all other threads of mine could be closed (as far as I am concerned :)) Thanks for your help! Huseyin

2 1

Re: [NTG-context] Installing an arabic font
by "H. Özoguz" 08 May '13

08 May '13

Sorry, Link corrected: http://fonts.qurancomplex.gov.sa/wp-content/uploads/2012/06/UthmanTN1-Ver10…

1 0

TEXpage filename
by Alan BRASLAU 08 May '13

08 May '13

Hello, In the production of (scientific) articles for journal submissions, one is often expected to supply the figures as separate files. One workflow can be through the use of \startTEXpage\stopTEXpage followed by an external extraction of single pdf pages to separate files. However, is it possible or would it be possible to directly output to a named file, as in: \startTEXpage{figure1.pdf} \stopTEXpage or perhaps \startTEXpage [file=figure1.pdf] \stopTEXpage ? (I could not find an answer looking at the source.) One could then (optionally) reinclude the figure in a review copy of the full text through the use of \externalfigure [figure1] Alan

5 9

Re: [NTG-context] Problems with arabic font "Amiri"
by "H. Özoguz" 08 May '13

08 May '13

> \setupalign > > works ok here ; maybe you should erease the font cache Works here now too ... Thanks.

1 0

Small bug in the result filename extension in log
by Romain Diss 08 May '13

08 May '13

Hi, I just noticed a small bug in the log of a context job. It has no incidence but maybe this can cause a side effect somewhere. When a file contain several dot in its name, context remove the last part in the result filename in the log: $ context test.foo.bar ... system > files > jobname 'test.foo.bar', input './test.foo.bar', result 'test.foo' ... However, the output is correct and one obtain 'test.foo.bar.pdf' and not 'test.foo.pdf'. All the best. -- Romain Diss <romain.diss(a)yahoo.fr>

2 1

Request for metadata:keywords support in startdocument
by Romain Diss 08 May '13

08 May '13

Hi, This is probably adressed to Hans. Is it possible to add the support for metadata:keywords in \startdocument? scrn-ini.mkvi l. 197 +++ \doifvariable{document}{metadata:keywords} {\setupinteraction[\c!subject=\documentvariable{metadata:keywords}]}% Thank you in advance. -- Romain Diss <romain.diss(a)yahoo.fr>

2 1