Re: [NTG-context] Yet another cornercase of ^^ handling in LuaMetaTeX

2020-06-17 Thread Marcel Fabian Krüger
gt; > again > > > > > > > Beside that, I noticed a smaller weird thing when using LuaMetaTeX in > > > > ini > > > > mode without Context: The default mathcodes for digits and letters have > > > > their class and family values switched. So e.

Re: [NTG-context] Yet another cornercase of ^^ handling in LuaMetaTeX

2020-06-17 Thread Hans Hagen
: The default mathcodes for digits and letters have their class and family values switched. So e.g. "A" has a default mathcode of 119537729=0x7200041, indicating class 1 and family 7, instead of the expected 31457345=0x1E00041, indicating class 7 and family 1. Of course this isn't really a probl

Re: [NTG-context] Changed behavior of ^^ in csname

2020-06-12 Thread Marcel Fabian Krüger
Hi, thank you for fixing this in the latest version. I found another problem with ^^, this time when followed by hexadecimal digits: \starttext \normalsupmarkmode\zerocount \catcode\circumflexasciicode=\superscriptcatcode% Ensure correct catcodes \let\ß\relax \show\ß % Shows "> \

Re: [NTG-context] Use \unit for value and uncertainty

2020-05-09 Thread Otared Kavian
min Buchmuller > wrote: > > I know this is quite an old thread, but here is a minimal parser (\units with > an “s”) that wraps around \digits and \unit to produce an acceptable output. > > As I frequently need to write ranges (or measures of uncertainty), I find it > co

Re: [NTG-context] Use \unit for value and uncertainty

2020-05-09 Thread Benjamin Buchmuller
I know this is quite an old thread, but here is a minimal parser (\units with an “s”) that wraps around \digits and \unit to produce an acceptable output. As I frequently need to write ranges (or measures of uncertainty), I find it convenient to able to type \units{4.0 to 5.0 centi meter

Re: [NTG-context] mkiv digits/units zero padding not working

2020-05-07 Thread Benjamin Buchmuller
of optimization. What I like about this approach however is that one could read the two arguments from a CSV file, which would save a lot of typing (and to manually specify the padding). \def\mpm#1#2{ \doifsomethingelse{#2}{ \startxcell[align=left] \digits{#1} \stopxcell \startxcell

[NTG-context] mkiv \digits{2.0=} zero padding feature request

2020-05-07 Thread Benjamin Buchmuller
Hi, As Wolfgang has figured out, zero padding in \digits only works for trailing (and omitted) zeroes when immediately preceded by the decimal separator. It would be nice if this would work even if there is a number preceding, so that \digits{3.1=}x\crlf \digits{3.==}x\crlf \digits{3.14}x

Re: [NTG-context] mkiv digits/units zero padding not working

2020-05-07 Thread Benjamin Buchmuller
igit separator of >> the first and second number respectively and overall at the ± sign. I’m >> working in an xtable, where I have entries such as >> \startxcell \mpm{14.0==}{_1.5==} \stopxcell >> \startxcell \mpm{_0.034}{_0.013} \stopxcell >> and defined >&

Re: [NTG-context] mkiv digits/units zero padding not working

2020-05-07 Thread Wolfgang Schuster
at the ± sign. I’m working in an xtable, where I have entries such as \startxcell \mpm{14.0==}{_1.5==} \stopxcell \startxcell \mpm{_0.034}{_0.013} \stopxcell and defined \def\mpm#1#2{ \ifsecondargument \digits{#1}\,±\,\digits{#2}% \else \digits{#1}% \fi

Re: [NTG-context] mkiv digits/units zero padding not working

2020-05-07 Thread Benjamin Buchmuller
such as \startxcell \mpm{14.0==}{_1.5==} \stopxcell \startxcell \mpm{_0.034}{_0.013} \stopxcell and defined \def\mpm#1#2{ \ifsecondargument \digits{#1}\,±\,\digits{#2}% \else \digits{#1}% \fi } Since I was hoping that I could exploit the zeropadding

Re: [NTG-context] mkiv digits/units zero padding not working

2020-05-07 Thread Wolfgang Schuster
Benjamin Buchmuller schrieb am 07.05.2020 um 17:31: Hi, I’m trying to get \digits{15.0=}±\digits{1.00} \digits{_8.12}±\digits{0.34} horizontally aligned as 15.0 ±1.00 8.12±0.34 But I get 15.0±1.00 8.12±0.34 instead. From the source (phys-dim.mkiv), I can see that “=“ should expand

[NTG-context] mkiv digits/units zero padding not working

2020-05-07 Thread Benjamin Buchmuller
Hi, I’m trying to get \digits{15.0=}±\digits{1.00} \digits{_8.12}±\digits{0.34} horizontally aligned as 15.0 ±1.00 8.12±0.34 But I get 15.0±1.00 8.12±0.34 instead. From the source (phys-dim.mkiv), I can see that “=“ should expand to \hphantom{0}. (I think \zeropoint in the table

Re: [NTG-context] Why does this METAPOST vardef 'save' statement fail?

2020-03-14 Thread Gerben Wierda
Answering myself: pth2 is not a valid variable name. Digits are not allowed. > On 14 Mar 2020, at 15:45, Gerben Wierda wrote: > > I have this vardef: > > vardef Foo(expr w, h) = >save pth; path pth; >%save pth2; path pth2; >save pic; picture pic; >pth

[NTG-context] setup according to total numbers

2019-11-20 Thread Pablo Rodriguez
be: - Set a different width in list if their total number of items is more than 9 and another one if items are more than 19. - List iwith alphabetic numbering when it contains fewer items than 5 and with digits in other case. - Stretch xtable to width, if it contains more than 4 columns. - Stretch

[NTG-context] configure \digits errata

2019-08-25 Thread Damien Thiriet
Hi, I made a mistake in my previous mail. I am looking for an alternativ to \setdigitmode \starttext \setdigitmode 3 \digits 1314000 \stoptext with an output points or thinmuskip Sorry for the noise, Damien Thiriet

[NTG-context] configure \digits

2019-08-25 Thread Damien Thiriet
Hi, According to the wiki and 2003 article Pasting Digits together, to get 1314000 typeset as 1\,314\,000, I should do \setdigits 3 \digits{1314000} unfortunatly, the \setdigits command looks obsolete (MkII command? Could not find in my ConTeXt help information server (http://localhost:8088/mtx

[NTG-context] No menu bar option for Adobe Reader

2019-04-27 Thread Paul Schalck
nd prints = pdfarray(flattened(pages.toranges(marked))) end end if fit or fixed or duplex or copies or paper or prints or title or direction or nomenubar then addtocatalog("ViewerPreferences",pdfdictionary { FitWindow = fit and tr

Re: [NTG-context] follow up

2019-04-03 Thread Hans Hagen
t; >> On 4/2/2019 4:18 PM, Ulrike Fischer wrote: >>> Am Tue, 2 Apr 2019 15:58:18 +0200 schrieb Floris van Manen: >>>>> indeed on preview no x shows up but it does in other viewers >>>>> >>>> >>>> N

Re: [NTG-context] follow up

2019-04-02 Thread Christoph Reller
; >> On 4/2/2019 4:18 PM, Ulrike Fischer wrote: > >>> Am Tue, 2 Apr 2019 15:58:18 +0200 schrieb Floris van Manen: > >>>>> indeed on preview no x shows up but it does in other viewers > >>>>> > >>>> > >>>> Not

Re: [NTG-context] follow up

2019-04-02 Thread Hans Hagen
example the s will disappear, be shows up if you add some extra digits, and then dropping the 2 I don't have a mac and can't reproduce the problem. But the missing char seems to be always the last one in the beginbfchar/endbfchar list. The OSX preview is flaky but i’d assume the output of both context

Re: [NTG-context] follow up

2019-04-02 Thread Taco Hoekwater
;>> Not just the x. >>> In the second example the s will disappear, be shows up if you add some >>> extra digits, and then dropping the 2 >> I don't have a mac and can't reproduce the problem. But the missing >> char seems to be always the last one in the beginbfchar/en

Re: [NTG-context] follow up

2019-04-02 Thread Hans Hagen
On 4/2/2019 4:18 PM, Ulrike Fischer wrote: Am Tue, 2 Apr 2019 15:58:18 +0200 schrieb Floris van Manen: indeed on preview no x shows up but it does in other viewers Not just the x. In the second example the s will disappear, be shows up if you add some extra digits, and then dropping the 2

Re: [NTG-context] follow up

2019-04-02 Thread Hans Hagen
On 4/2/2019 4:18 PM, Ulrike Fischer wrote: Am Tue, 2 Apr 2019 15:58:18 +0200 schrieb Floris van Manen: indeed on preview no x shows up but it does in other viewers Not just the x. In the second example the s will disappear, be shows up if you add some extra digits, and then dropping the 2

Re: [NTG-context] follow up

2019-04-02 Thread Hans Hagen
On 4/2/2019 3:58 PM, Floris van Manen wrote: indeed on preview no x shows up but it does in other viewers Not just the x. In the second example the s will disappear, be shows up if you add some extra digits, and then dropping the 2 The OSX preview is flaky but i’d assume the output of both

Re: [NTG-context] follow up

2019-04-02 Thread Ulrike Fischer
Am Tue, 2 Apr 2019 15:58:18 +0200 schrieb Floris van Manen: >> indeed on preview no x shows up but it does in other viewers >> > > Not just the x. > In the second example the s will disappear, be shows up if you add some extra > digits, and then dropping the 2 I do

Re: [NTG-context] follow up

2019-04-02 Thread Floris van Manen
> indeed on preview no x shows up but it does in other viewers > Not just the x. In the second example the s will disappear, be shows up if you add some extra digits, and then dropping the 2 The OSX preview is flaky but i’d assume the output of both context version would be similar (

Re: [NTG-context] Bad names

2019-02-09 Thread Marco Patzer
always normalize > (az09-). So every file name containing something else than lowercase, digits and a dash is “bad” (and dots obviously)? Doesn't seem to be true: a.1.png %% bad name Names are read from a database i

Re: [NTG-context] Typing Unicode subscript and superscript numbers

2018-12-06 Thread Wolfgang Schuster
is normally of a different design that a scaled down 2, so one then has to replace them all. Then there is the question of scale and move (up/down). This issue shows up with the STIX and STIX2 fonts, as the former has the superscript digits ¹ ² ³, but not the other which came to Unicode later

Re: [NTG-context] Typing Unicode subscript and superscript numbers

2018-12-06 Thread Hans Åberg
ifferent design > that a scaled down 2, so one then has to replace them all. Then there is the > question of scale and move (up/down). This issue shows up with the STIX and STIX2 fonts, as the former has the superscript digits ¹ ² ³, but not the other which came to Unicode later in a different

Re: [NTG-context] Issues with RGB to CMYK conversion with color profiles

2018-11-21 Thread luigi scarso
but at least I found transicc to > calculate color conversions. > > What precision is useful in the wild? > > I now use three digits after the decimal point, eg.: > > \definecolor [hs-logoblau] [c=0.976, m=0.665, y=0.028, k=0.116] > > It's safe to specify a color as 8bit p

Re: [NTG-context] Issues with RGB to CMYK conversion with color profiles

2018-11-21 Thread Jan U. Hasecke
I now use three digits after the decimal point, eg.: \definecolor [hs-logoblau] [c=0.976, m=0.665, y=0.028, k=0.116] juh ___ If your question is of interest to others as well, please add an entry to the Wiki! ma

Re: [NTG-context] open type feature "frac"

2018-09-28 Thread Hans Hagen
On 9/28/2018 10:56 PM, Ulrike Fischer wrote: Due to a question on tex.sx (https://tex.stackexchange.com/questions/452969/luatex-fontfeaturefractions-on-turns-first-digits-into-superscripts) I looked again (see https://www.mail-archive.com/ntg-context@ntg.nl/msg84822.html) at the frac feature

[NTG-context] open type feature "frac"

2018-09-28 Thread Ulrike Fischer
Due to a question on tex.sx (https://tex.stackexchange.com/questions/452969/luatex-fontfeaturefractions-on-turns-first-digits-into-superscripts) I looked again (see https://www.mail-archive.com/ntg-context@ntg.nl/msg84822.html) at the frac feature. The output is still not really satisfactory

[NTG-context] SHA512 for LuaTeX-5.2

2018-07-22 Thread Pablo Rodriguez
Dear list, I have the following sample (adapted from https://stackoverflow.com/q/50442185): ✂️ \starttext \startlua -- -- UTILITY FUNCTIONS -- -- transform a string of bytes in a string of hexadecimal digits local function str2hexa (s

Re: [NTG-context] Some questions about the presentation of a book

2018-07-21 Thread Fabrice Couvreur
t; \setupheadertexts[{\getmarking[section]}] > [pagenumber] > [{\getmarking[chapter]}] > [pagenumber] > > > \setuppagenumbering[alternative=,location=] > > > \setuplabeltext[fr][chapter=Chapitre ] > > \definestructureconversionset >

[NTG-context] Some questions about the presentation of a book

2018-07-20 Thread Fabrice Couvreur
n, R, n, n, n] \definestructureconversionset [digits] [n, n, n, n, n] \setupheads[sectionconversionset=structure] \setuplist[chapter][style=bold,width=5mm] \starttext \starttitle[title={\bf Sommaire}] \placelist [chapter,section,subsection] [criterium=all, alternative=c]

Re: [NTG-context] OT: Pexeso (one missing rule)

2018-06-12 Thread Otared Kavian
code in order to get cards with an alphabet on them, or numbers and digits, or even Chinese characters, directly within ConTeXt (that is not creating first a set of images with the alphabet, or the numbers or the characters). Best regards: OK > On 11 Jun 2018, at 16:31, Procházka Lukáš Ing. wr

Re: [NTG-context] Conversion of \newcounts

2018-05-19 Thread Idris Samawi Hamid ادريس سماوي حامد
ext \NUM{Numbered Text} } \stopTEXpage === How can one make a conversion of the numerals output by the \newcount? That is, how so we replace the default U+0030-U+0039 digits (0 1 2 3..) with some defined conversion (e.g., \romannumerals)? Is there a ConTeXt way to setup new counts so that they

Re: [NTG-context] Conversion of \newcounts

2018-05-19 Thread Wolfgang Schuster
by the \newcount? That is, how so we replace the default U+0030-U+0039 digits (0 1 2 3..) with some defined conversion (e.g., \romannumerals)? Is there a ConTeXt way to setup new counts so that they can automatically use the conversion mechanism? \definecounter[idris]%[numberconversio

[NTG-context] Conversion of \newcounts

2018-05-19 Thread Idris Samawi Hamid ادريس سماوي حامد
\NR \NC #1 \NR \stoptabulate}% \advance\MQT by 1 \hbox{}} \startTEXpage \dorecurse{5}{Unnumbered Text \NUM{Numbered Text} } \stopTEXpage === How can one make a conversion of the numerals output by the \newcount? That is, how so we replace the default U+0030-U+0039 digits (0 1 2 3..) with so

Re: [NTG-context] Feature request: \digits command

2018-04-29 Thread Peter Münster
On Wed, Jun 25 2008, Flavien Lambert wrote: > did not found a way to cut a number by group of three digits like the > numprint command, e.g. 100 becomes 1 000 000. With the digits > option 3, dots become thinmuskips. I would like to do something > similar but automatically for gro

Re: [NTG-context] Some questions about my document

2017-08-27 Thread Fabrice Couvreur
set=numbers] and a different one for > \defineenumeration[remark][prefixconversionset=digits]. > > If there is no different conversion set for the enumeration, you get the > default for the head. > > Here is the full sample: > > \mainlanguage[fr] > \setuphead[chapter][command

Re: [NTG-context] Some questions about my document

2017-08-27 Thread Pablo Rodriguez
eads[sectionconversionset=numbers] and a different one for \defineenumeration[remark][prefixconversionset=digits]. If there is no different conversion set for the enumeration, you get the default for the head. Here is the full sample: \mainlanguage[fr] \setuphead[chapter][commandbe

Re: [NTG-context] Some questions about my document

2017-08-27 Thread Fabrice Couvreur
I think it would be better to use French: > > \mainlanguage[fr] > \setuplabeltext[fr][chapter=Chapitre ] > > > But for this > > > > Remark 1.1. > > Remark 1.2 > > Remark 1.3 > > > > I do not find ! > > You have to define a new

Re: [NTG-context] Some questions about my document

2017-08-27 Thread Pablo Rodriguez
I do not find ! You have to define a new conversion set and use it for the prefix segments (I added the section to the numbering): \definestructureconversionset [digits] [n, n, a, n, n] [numbers] \defineenumeration [remark] [ text=Re

Re: [NTG-context] how to hyphenate SHA512?

2017-07-08 Thread Hans Hagen
On 7/8/2017 10:20 AM, josephcan...@gmail.com wrote: If I am not mistaken SHA is only hexadecimal digits, so you probably need only to have a « language » that hyphenates between any pair of those. Should be much simpler I guess, but I do not really know how to add such setting I am afraid. you

Re: [NTG-context] how to hyphenate SHA512?

2017-07-08 Thread josephcanedo
If I am not mistaken SHA is only hexadecimal digits, so you probably need only to have a « language » that hyphenates between any pair of those. Should be much simpler I guess, but I do not really know how to add such setting I am afraid. Joseph De : Pablo Rodriguez Envoyé le :samedi 8

Re: [NTG-context] mathdigits no longer works

2017-05-15 Thread Mohammad Hossein Bateni
la Math] >> >> \startttext >> >> \switchtobodyfont[minionmath] >> >> \startformula >> {\tf xyz} xyz {\bf xyz} {\bi xyz}, 2+3, {\bf 2+3} >> \stopformula >> >> \stoptext >> >> >> With beta version 2017.01.17 17:37 it use

Re: [NTG-context] mathdigits no longer works

2017-05-15 Thread Otared Kavian
t; > > \switchtobodyfont[minionmath] > > > > \startformula > > {\tf xyz} xyz {\bf xyz} {\bi xyz}, 2+3, {\bf 2+3} > > \stopformula > > > > \stoptext > > > > > > With beta version 2017.01.17 17 <tel:2017.01.17%2017>:37 it used to work >

Re: [NTG-context] mathdigits no longer works

2017-05-15 Thread Hans Hagen
] \definefontfamily [minionmath] [mm] [TeX Gyre Pagella Math] \startttext \switchtobodyfont[minionmath] \startformula {\tf xyz} xyz {\bf xyz} {\bi xyz}, 2+3, {\bf 2+3} \stopformula \stoptext With beta version 2017.01.17 17:37 it used to work and change the digits to Indic inside math. With beta

Re: [NTG-context] mathdigits no longer works

2017-05-15 Thread Mohammad Hossein Bateni
onmath] > > > > \startformula > > {\tf xyz} xyz {\bf xyz} {\bi xyz}, 2+3, {\bf 2+3} > > \stopformula > > > > \stoptext > > > > > > With beta version 2017.01.17 17:37 it used to work and change the > digits to Indic inside math. With beta

Re: [NTG-context] mathdigits no longer works

2017-05-15 Thread Otared Kavian
nionmath] > > \startformula > {\tf xyz} xyz {\bf xyz} {\bi xyz}, 2+3, {\bf 2+3} > \stopformula > > \stoptext > > > With beta version 2017.01.17 17:37 it used to work and change the digits to > Indic inside math. With beta version 2017.04.27 01:00, the digits do not

Re: [NTG-context] mathdigits no longer works

2017-05-14 Thread Mohammad Hossein Bateni
] \startttext \switchtobodyfont[minionmath] \startformula {\tf xyz} xyz {\bf xyz} {\bi xyz}, 2+3, {\bf 2+3} \stopformula \stoptext With beta version 2017.01.17 17:37 it used to work and change the digits to Indic inside math. With beta version 2017.04.27 01:00, the digits do not change

[NTG-context] mathdigits no longer works

2017-05-12 Thread Mohammad Hossein Bateni
Hi, The example for replacing Arabic numerals by Indic digits inside math used to work (at least) until version 2017.01.17 17:37. tex/texmf-context/tex/context/fonts/mkiv/type-imp-mathdigits.mkiv Now in version 2017.04.27 01:00, this does not produce the desired output: it's all "Latin&qu

Re: [NTG-context] Real number with Lua

2017-04-19 Thread Aditya Mahajan
On Wed, 19 Apr 2017, Procházka Lukáš Ing. wrote: Hello, do you mean this? - It shows EXACTLY 3 digits after the decimal point: \cldcontext{string.format("\letterpercent.3f", 5.8/1.6)} \cldcontext{string.format(string.char(37) .. ".3f", 5.8/1.6)} \startluacode c

Re: [NTG-context] Real number with Lua

2017-04-19 Thread Herbert Voss
Am 19.04.2017 um 15:25 schrieb Fabrice Couvreur: I do not know Lua but I'll learn later. How to display only 3 digits after the decimal point ? The default is 3 digits \startluacode function round(a,dec) local dec = dec or 3 local b = math.pow(10,dec) return math.floor(a*b)/b end

Re: [NTG-context] Real number with Lua

2017-04-19 Thread Procházka Lukáš Ing .
Hello, do you mean this? - It shows EXACTLY 3 digits after the decimal point: \cldcontext{string.format("\letterpercent.3f", 5.8/1.6)} \cldcontext{string.format(string.char(37) .. ".3f", 5.8/1.6)} \startluacode context(string.format("%.3f", 5.8/1.6)) \

Re: [NTG-context] Real number with Lua

2017-04-19 Thread Otared Kavian
later. How to display only 3 digits after > the decimal point ? > thank you, > Fabrice > > \starttext > \startlinecorrection[blank] > \startmidaligned > \bTABLE[width=2cm,offset=0.8ex,align={lohi,middle}] > \bTR > \bTD \math{P} \eTD &g

[NTG-context] Real number with Lua

2017-04-19 Thread Fabrice Couvreur
Hello, I do not know Lua but I'll learn later. How to display only 3 digits after the decimal point ? thank you, Fabrice \starttext \startlinecorrection[blank] \startmidaligned \bTABLE[width=2cm,offset=0.8ex,align={lohi,middle}] \bTR \bTD \math{P} \eTD \bTD

Re: [NTG-context] pdfboxes

2017-02-13 Thread Peter Rolf
gt;> <> 250]/CropBox [ 0 0 150 250 ] /TrimBox [ 0 0 150 250 ]/Parent 13 0 R>> >> endobj >> [..] >> >> >> >> One additional note. The Mediabox precision seems to be 5 now (and not >> 4). Taken from my latest table using TeXpage (/MediaBox[0 0 1655.3

Re: [NTG-context] pdfboxes

2017-02-10 Thread Hans Hagen
eXpage (/MediaBox[0 0 1655.39105 969.22291]). The precision value for the other boxes should be adjusted to avoid rounding problems (?Box < MediaBox). [lpdf-mis.lua] [..] -- temp hack: the mediabox is not under our control and has a precision of 4 digits local factor = number.dimenfactors.bp loca

[NTG-context] pdfboxes

2017-02-10 Thread Peter Rolf
(?Box < MediaBox). [lpdf-mis.lua] [..] -- temp hack: the mediabox is not under our control and has a precision of 4 digits local factor = number.dimenfactors.bp local f_value = formatters["%0.4F"] [..] Not in a hurry, fix (or advice) is welcome at any time :D Best wishes,

Re: [NTG-context] Bold italic font in Math (\definefallbackfamily)

2016-09-10 Thread Wolfgang Schuster
But I lose upright numbers this way. How can I solve this issue. I've tried without success: \definefallbackfamily[...][math][...][preset=math:digitsitalic] Math symbols in MkIV are (mostly?) restricted to Unicode which doesn’t define italic digits (but you can choose between regular, bold, sans

Re: [NTG-context] Opentype feature and "aligncharacter=yes"

2016-09-04 Thread Hans Hagen
that oldstyle fixed width digits would fail \definefontfeature [system:tabnum] [system:tabnum] [onum=no] \definefontfeature[default][default][onum=yes] \setupbodyfont[pagella] \starttext \enabledirectives[typesetters.characteralign.autofont] \bTABLE \setupTABLE[alignmentcharacter={text

Re: [NTG-context] Bug in CONTEXT/LuaTeX or just buggy font

2016-08-10 Thread Hans Hagen
Serif][Samim] \stoptypescript \definetypeface [myfont][rm] [serif][samim][default] \setupbodyfont [myfont] \starttext %\definedfont[Samim*arabic] ۱۲۳\high{۴}۵۶. \stoptext I am using Persian digits because the font lacks Latin

Re: [NTG-context] Bug in CONTEXT/LuaTeX or just buggy font

2016-08-10 Thread Mohammad Hossein Bateni
>> >> \definetypeface [myfont][rm] [serif][samim][default] >> \setupbodyfont [myfont] >> >> \starttext >> %\definedfont[Samim*arabic] >> ۱۲۳\high{۴}۵۶. >> \stoptext >> >> >> I am using Persian digits because the font lacks Latin d

Re: [NTG-context] Bug in CONTEXT/LuaTeX or just buggy font

2016-08-10 Thread Hans Hagen
the MWE below. \starttypescript [serif][samim][name] \definefontsynonym[Serif][Samim] \stoptypescript \definetypeface [myfont][rm] [serif][samim][default] \setupbodyfont [myfont] \starttext %\definedfont[Samim*arabic] ۱۲۳\high{۴}۵۶. \stoptext I am using Persian digits because the font lacks

[NTG-context] Bug in CONTEXT/LuaTeX or just buggy font

2016-08-09 Thread Mohammad Hossein Bateni
] \definefontsynonym[Serif][Samim] \stoptypescript \definetypeface [myfont][rm] [serif][samim][default] \setupbodyfont [myfont] \starttext %\definedfont[Samim*arabic] ۱۲۳\high{۴}۵۶. \stoptext I am using Persian digits because the font lacks Latin digits as I mentioned. If I use the \definedfont

Re: [NTG-context] Changing decimals points to Persian ones via font features

2016-08-08 Thread Hans Hagen
On 8/8/2016 5:24 PM, Mohammad Hossein Bateni wrote: Thanks, Hans! I see; this does work except for the trouble of annotating with \digits macro. Would it be possible if I wrote a processor in Lua to do the work? nodes.tasks.appendaction ("processors", "before", "fix_

Re: [NTG-context] Changing decimals points to Persian ones via font features

2016-08-08 Thread Mohammad Hossein Bateni
Thanks, Hans! I see; this does work except for the trouble of annotating with \digits macro. Would it be possible if I wrote a processor in Lua to do the work? nodes.tasks.appendaction ("processors", "before", "fix_persian_mathperiod") Can I find out if a n

Re: [NTG-context] Changing decimals points to Persian ones via font features

2016-08-08 Thread Hans Hagen
On 8/2/2016 9:54 PM, Mohammad Hossein Bateni wrote: Could the problem be because math fonts use mode=base instead of mode=node? Or is it because in math fonts, the digits and/or full-stop have different codes? math fonts are defined and then don't change i.e. they are quite static and all

Re: [NTG-context] Changing decimals points to Persian ones via font features

2016-08-08 Thread Hans Hagen
On 8/1/2016 3:46 PM, Mohammad Hossein Bateni wrote: Dear list, I want to add a customized font feature to the math font, to automatically change the decimal point (unicode 0x2E) to the Arabic/Farsi version (unicode 0x66B). This will go well with the mapping from Latin digits to Farsi digits

[NTG-context] OTF feature for a math font

2016-08-05 Thread Mohammad Hossein Bateni
nts but not in math mode. Thanks, MHB On Tue, Aug 2, 2016 at 3:54 PM, Mohammad Hossein Bateni <bat...@gmail.com> wrote: > Could the problem be because math fonts use mode=base instead of > mode=node? Or is it because in math fonts, the digits and/or full-stop > have different codes?

Re: [NTG-context] Changing decimals points to Persian ones via font features

2016-08-02 Thread Mohammad Hossein Bateni
Could the problem be because math fonts use mode=base instead of mode=node? Or is it because in math fonts, the digits and/or full-stop have different codes? —MHB On Mon, Aug 1, 2016 at 9:46 AM, Mohammad Hossein Bateni <bat...@gmail.com> wrote: > Dear list, > > I want to add a

[NTG-context] Changing decimals points to Persian ones via font features

2016-08-01 Thread Mohammad Hossein Bateni
Dear list, I want to add a customized font feature to the math font, to automatically change the decimal point (unicode 0x2E) to the Arabic/Farsi version (unicode 0x66B). This will go well with the mapping from Latin digits to Farsi digits (done in a sample with mathdigits fallback

Re: [NTG-context] Tabulate \NN not working

2016-05-29 Thread Hans Åberg
t; http://wiki.contextgarden.net/Tabulate > The description is wrong, the \NN command calls the \digits command at the > begin of the cell, i.e. > > \NN … > > is the same as > > \NC \digits … OK. Perhaps a \NM … command call $…$, then. The output on the \digit

Re: [NTG-context] Tabulate \NN not working

2016-05-29 Thread Wolfgang Schuster
umns, though, as in the second table below. What do you expect? The pages [1], "Using math mode” suggests \NN is equivalent to \NC $$ 1. http://wiki.contextgarden.net/Tabulate The description is wrong, the \NN command calls the \digits command at the begin of the cell, i.e. \

Re: [NTG-context] xml expression error

2016-05-12 Thread Hans Hagen
On 5/12/2016 1:49 PM, Meer, Hans van der wrote: I think I have the problem nailed down to the fact that in the comparison: something >= -1234 the parser in question separates the minus in the negative number into a separate child node, apart from the digits; witness the errormessage in the

Re: [NTG-context] xml expression error

2016-05-12 Thread Meer, Hans van der
I think I have the problem nailed down to the fact that in the comparison: something >= -1234 the parser in question separates the minus in the negative number into a separate child node, apart from the digits; witness the errormessage in the log below. Changing the number -1

Re: [NTG-context] font features in math

2016-05-04 Thread Hans Hagen
the math is normal digits because the font is pass as-is Hans - Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.prag

Re: [NTG-context] RTL section heads

2016-04-13 Thread Hans Hagen
On 4/13/2016 4:15 AM, Otared Kavian wrote: Hi Hans and Mohammad Reza, I can confirm that the wrong behaviour of numbers and digits in Right to Left (more specifically Persian) is recent: indeed with ConTeXt ver: 2015.05.18 12:26 MKIV current fmt: 2015.6.18 int: english/english

Re: [NTG-context] RTL section heads

2016-04-12 Thread Mohammad Hossein Bateni
As far as I remember, it was working fine with betas in December 2015 and January 2016. On Tue, Apr 12, 2016 at 10:15 PM, Otared Kavian <ota...@gmail.com> wrote: > Hi Hans and Mohammad Reza, > > I can confirm that the wrong behaviour of numbers and digits in Right to > Left

Re: [NTG-context] RTL section heads

2016-04-12 Thread Otared Kavian
Hi Hans and Mohammad Reza, I can confirm that the wrong behaviour of numbers and digits in Right to Left (more specifically Persian) is recent: indeed with ConTeXt ver: 2015.05.18 12:26 MKIV current fmt: 2015.6.18 int: english/english from TeXLive 2015 the numbers and digits

Re: [NTG-context] RTL section heads

2016-04-12 Thread Mohammad Hossein Bateni
اعداد ۱، ۲، ۳ و ۴ را در نظر بگیرید. >>> >>> اعداد 1، 2، 3 و 4 را در نظر بگیرید. >>> >>> اعداد 1, 2, 3 و 4 را در نظر بگیرید. >>> >>> \stoptext >>> >>> >>> I expect the numbers 1, 2, 3 and 4 to appear in the same or

Re: [NTG-context] RTL section heads

2016-04-11 Thread Mohammad Hossein Bateni
> اعداد ۱، ۲، ۳ و ۴ را در نظر بگیرید. >> >> اعداد 1، 2، 3 و 4 را در نظر بگیرید. >> >> اعداد 1, 2, 3 و 4 را در نظر بگیرید. >> >> \stoptext >> >> >> I expect the numbers 1, 2, 3 and 4 to appear in the same order from >> right to left. H

Re: [NTG-context] RTL section heads

2016-04-11 Thread Hans Hagen
sual order that I observe (regardless of whether I use Persian digits or English digits, or whether I use Persian or English commas) is 4, 1, 2, 3 (from left to right). Is this a bug in the bidi code? If so, are there any workarounds? method=two Thanks, Hossein On Fri, Apr 8, 2016 at 5:2

Re: [NTG-context] RTL section heads

2016-04-10 Thread Mohammad Hossein Bateni
use Persian digits or English digits, or whether I use Persian or English commas) is 4, 1, 2, 3 (from left to right). Is this a bug in the bidi code? If so, are there any workarounds? Thanks, Hossein On Fri, Apr 8, 2016 at 5:20 PM, Mohammad Hossein Bateni <bat...@gmail.com> wr

[NTG-context] RTL section heads

2016-04-08 Thread Mohammad Hossein Bateni
and section numbers should be separated with a dash. (This is ignored in this email and I will follow up about it in another thread. To get a minimal working example, I also do not try to change the numbers to use Persian digits.) In particular, the headings will be visually something like

Re: [NTG-context] ConTeXt vs Beamer

2016-01-26 Thread Saša Janiška
allation, and begin with s-pre-, followed by > digits and mkii or mkiv suffix. > The examples by Aditya and Thomas are to be found in  > > /tex/texmf-modules/tex/context/third/simpleslides After some additonal install, I was able to localize both type of examples. :-) Now let

Re: [NTG-context] ConTeXt vs Beamer

2016-01-25 Thread Otared Kavian
to use such and such features. A good start is to begin with the examples set up by Hans and by Aditya and Thomas Schmitz. The examples by Hans are in the directory /tex/texmf-context/tex/context/modules/mkiv of your Context installation, and begin with s-pre-, followed by digits and mkii

Re: [NTG-context] (mashriqi) Arabic-Hindi Numerals

2016-01-19 Thread Wolfgang Schuster
compilations. \persiandecimals and \arabicdecimals are very similar. The difference is (almost) only in digits for 0,4,5,6. However, Ibn Saeed most probably needs \arabicdecimals to typeset "mashiriqi" numerals. The important thing is that neither one exists in TeXLive Context.

Re: [NTG-context] (mashriqi) Arabic-Hindi Numerals

2016-01-19 Thread Mohammad Hossein Bateni
imilar. The difference is (almost) only in digits for 0,4,5,6. However, Ibn Saeed most probably needs \arabicdecimals to typeset "mashiriqi" numerals. The important thing is that neither one exists in TeXLive Context. It was there in MkII but not in MkIV for some reason. It was added

Re: [NTG-context] (mashriqi) Arabic-Hindi Numerals

2016-01-19 Thread Ibn Saeed
re very similar.  The difference is (almost) only in digits for 0,4,5,6.  However, Ibn Saeed most probably needs \arabicdecimals to typeset "mashiriqi" numerals. > > The important thing is that neither one exists in TeXLive Context.  It was there in MkII but not in MkIV for some reason.

Re: [NTG-context] (mashriqi) Arabic-Hindi Numerals

2016-01-19 Thread Ibn Saeed
re very similar.  The difference is (almost) only in digits for 0,4,5,6.  However, Ibn Saeed most probably needs \arabicdecimals to typeset "mashiriqi" numerals. > > The important thing is that neither one exists in TeXLive Context.  It was there in MkII but not in MkIV for some reason.

Re: [NTG-context] (mashriqi) Arabic-Hindi Numerals

2016-01-19 Thread Ibn Saeed
re very similar.  The difference is (almost) only in digits for 0,4,5,6.  However, Ibn Saeed most probably needs \arabicdecimals to typeset "mashiriqi" numerals. > > The important thing is that neither one exists in TeXLive Context.  It was there in MkII but not in MkIV for some reason.

Re: [NTG-context] r2l alignment and linenumbering conflict?

2015-08-03 Thread tala...@fastmail.fm
Just to note: all numbers in the body text are having their digits placed individually right-to-left. Notice, in the attached PDF, how the ١٤ is displayed as ٤١, and how ١٨٧٢ is ٢٧٨١ … but also the footnote marker is ٣١ instead of ١٣ as it correctly is below in the footnote itself

Re: [NTG-context] r2l alignment and linenumbering conflict?

2015-08-03 Thread tala...@fastmail.fm
(١٨٧٢—١٩٢٣)} مرحباً باعالم . ١٢٣٤٥٦٧٨٩٠ مرحباً بالعالم. ولد عام ١٩٣٤. \footnote{تعليقة لطيفة.} \pagebreak } \stoptext == Best wishes, Talal On 3 Aug 2015, at 17:29, tala...@fastmail.fm wrote: Just to note: all numbers in the body text are having their digits placed

Re: [NTG-context] r2l alignment and linenumbering conflict?

2015-08-03 Thread tala...@fastmail.fm
عام ١٩٣٤. \footnote{تعليقة لطيفة.} \pagebreak } \stoptext == Best wishes, Talal On 3 Aug 2015, at 17:29, tala...@fastmail.fm wrote: Just to note: all numbers in the body text are having their digits placed individually right-to-left. Notice, in the attached PDF, how the ١٤ is displayed

Re: [NTG-context] footnotes when using RtL (Arabic)

2015-08-03 Thread tala...@fastmail.fm
In a separate thread ("r2l alignment and linenumbering conflict?"), we've gotten numerals in an Arabic RTL document to (a) display as Arabic numerals, and (b) to order their digits in the right order (e.g. 2015 instead of 5102). By defining the headstyle of linenotes, we can even get

Re: [NTG-context] Arabic/Hindi numerals in layout structures (headers, page numbers, etc.)

2015-08-03 Thread Idris Samawi Hamid ادريس سماوي حامد
. entries), and to have this automated when declaring the main language to be Arabic, for example. Ultimately this workaround is overkill. conversion=arabicnumerals needs to be fixed. It's a matter of glyph mapping exactly ten digits, should be trivial... Wassalaam Idris -- Idris Samawi Hamid

  1   2   3   4   >