Le 8 mai 13 à 06:56, Wolfgang Schuster a écrit :
Am 07.05.2013 um 22:28 schrieb Roland Thiers
roland.thi...@gmail.com:
Thank you very much for this precision, Wolfgang. I tried with two
variables and it works with this
syntax :
\startuniqueMPgraphic{polygoneregulier}
numeric u ;
On 2013–05–07 Kip Warner wrote:
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
On Wed, May 8, 2013 at 2:49 AM, Kip Warner k...@thevertigo.com wrote:
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
On Wed, May 8, 2013 at 9:32 AM, luigi scarso luigi.sca...@gmail.com wrote:
yes, it's known and it's ok, because luajittex is not different from
luatex as luatex is different from pdftex/xetex/etex
(and if it's so, then it is an error).
(and if it's not so, then it is an error).
--
On 5/8/2013 9:29 AM, Marco Patzer wrote:
On 2013–05–07 Kip Warner wrote:
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
On 5/8/2013 7:41 AM, H. Özoguz wrote:
Hello,
I tried to type with the arabic font Amiri by K. Hosny. You can
download it here: http://sourceforge.net/projects/amiri/
In this download-page you find a nice example of the font, setting the
sura Al-Fatiha (first section of the Holy Qur'an). I
On 5/8/2013 7:35 AM, H. Özoguz wrote:
\usemodule[fnt-20,art-01]
\starttext
\def\sample{اللهِ\quad اللَّـهِ}
\setvariables
[otftracker]
[font=name:traditionalarabicnormal,
size=24pt,
features=arabic,
direction=-1,
title=Feature Check,
sample=\sample]
\page
works ok here (in latest beta)
Sorry, my fault. Of course it works, but it was not r2l (and so not
readably), this one is the not working:
\definefont[amiri][file:amiri-regular.ttf*arabic at 17pt]
\define[1]\Arab{\setuplayout[r2l] \amiri#1}
\starttext
\Arab{بِسْمِ اللَّـهِ الرَّحْمَـٰنِ
On 5/8/2013 9:18 AM, Meer, H. van der wrote:
\startxmlsetups xmlcommon:mpgraphic
\unprotect\input{\foundfilewithsuffix}\protect
\stopxmlsetups
unprotected regime:
\starttexcode
... % e.g. \input
\stoptexcode
regular context regime:
\startcontextcode
... % e.g.\input
\stopcontextcode
On 5/8/2013 10:34 AM, H. Özoguz wrote:
works ok here (in latest beta)
Sorry, my fault. Of course it works, but it was not r2l (and so not
readably), this one is the not working:
\definefont[amiri][file:amiri-regular.ttf*arabic at 17pt]
\define[1]\Arab{\setuplayout[r2l] \amiri#1}
\starttext
On 5/2/2013 7:00 PM, Sietse Brouwer wrote:
Hi Hans,
How do I enable the output of for example:
report_typescripts(unknown library %a or %a,name_one,name_two)
`logs.reporter(fonts,typescripts)` returns a function for writing
to the log. Calling that function produces this sort of output:
On 5/1/2013 8:50 AM, Romain Diss wrote:
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}]}%
On 5/1/2013 11:31 AM, Romain Diss wrote:
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
\setupalign
works ok here ; maybe you should erease the font cache
Works here now too ... Thanks.
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist :
Thanks, Thomas. This is good to have for many purposes. But, for the task
of generating PDFs of components that are part of a larger product, the
problem of cross-references is but one of several issues—especially if one
wants ConTeXt to do most (if not all) of the work.
Alan
On Sun, May 5,
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.zip.
One of its types is: kfgqpcuthmantahanaskhregular
If I type in the cmd
Sorry, Link corrected:
http://fonts.qurancomplex.gov.sa/wp-content/uploads/2012/06/UthmanTN1-Ver10.zip
___
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist :
On Wed, May 08, 2013 at 05:38:35PM +0200, H. Özoguz wrote:
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.zip.
One of its
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
On 5/8/2013 9:23 PM, H. Özoguz wrote:
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
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
On 5/8/2013 10:58 PM, H. Özoguz wrote:
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
On Wed, 2013-05-08 at 09:32 +0200, luigi scarso wrote:
On Wed, May 8, 2013 at 2:49 AM, Kip Warner k...@thevertigo.com wrote:
Hey Luigi,
I find the \texenginename and \texengineversion useful for retrieving
the backend name and version. They work fine when using the vanilla
LuaTeX
Hi,
With AdobeMyungjoStd-Medium.otf, I cannot typeset some chinese
characters. Here is a simple tex source:
\starttext
\definedfont[name:adobemyungjostdmedium]
黃金빛
\stoptext
U+9EC3 黃 and U+91D1 金 are missing in the pdf.
Incidentally, during font cache I get a bunch of warning messages as
24 matches
Mail list logo
