[NTG-context] Linespacing modified across document

2022-01-22 Thread Alexandre Christe via ntg-context
Dear list,

I've noticed that in my document the linespacing (verified
with \the\baselineskip) is not consistent across the whole document.

In the first section, it's fine (no maths). Later on, it gets increased by
some amount, which tends to depend on what kind of mathematics are in
between, so it's not constant.

Has anyone else noticed this too?

BR
Alex
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] \installpagearrangement doublesided stickers

2022-01-22 Thread Willi Egger via ntg-context
Hello Jigé,

Adapt your layout to the following and it works.

\setuplayout
[%]
margin=0mm,
topspace=0mm,
backspace=1mm,
width=80mm,
height=50mm,
nx=2,
ny=5,
dx=0mm,
dy=0mm,
location=middle,
marking=on,
]

Kind regards
Willi

> On 16 Jan 2022, at 15:18, Jigé via ntg-context  wrote:
> 
> Greetings everyone.
> 
> Well, it's not exactly about double-sided stickers but sort of. Imagine 
> printing a double-sided sheet and using a so-called plastifying device to 
> make tokens.
> I began with the File Card and Labels examples from the wiki, then tried to 
> change the \installpagearrangement example from the 'imposition' wiki page.
> 
> My question is:
> how to position everything in the middle of the sheet, so that double-siding 
> actually works?
> As is, it's all in the top left corner. Changing the location argument for 
> "location=middle" in \setuplayout doesn't work here. What should it be?
> 
> By the way, I'm not sure about the 3rd, 4th and 6th arguments in the 
> dosetuparrangement command.
> 
> Thanks a lot!
> 
> Here it is:
> 
> \installpagearrangement 2*5*double*2*5
> {\dosetuparrangement{5}{2}{10}{3}{6}% X,Y,Total,hcutmarks,vcutmarks
>  \pusharrangedpageTWOFIVEDOUBLESIDED\poparrangedpagesAB\relax}
> 
> \def\pusharrangedpageTWOFIVEDOUBLESIDED#1%
> {\advancearrangedpageN
> \reportarrangedpage\arrangedpageN
> \ifcase\arrangedpageN
> \or \handlearrangedpageXandY{#1}000\arrangedpageA %  1 rot,hskip,vskip
> \or \handlearrangedpageXandY{#1}010\arrangedpageB %  2
> \or \handlearrangedpageXandY{#1}010\arrangedpageA %  3
> \or \handlearrangedpageXandY{#1}000\arrangedpageB %  4
> \or \handlearrangedpageXandY{#1}001\arrangedpageA %  5
> \or \handlearrangedpageXandY{#1}011\arrangedpageB %  6
> \or \handlearrangedpageXandY{#1}011\arrangedpageA %  7
> \or \handlearrangedpageXandY{#1}001\arrangedpageB %  8
> \or \handlearrangedpageXandY{#1}002\arrangedpageA %  9
> \or \handlearrangedpageXandY{#1}012\arrangedpageB %  10
> \or \handlearrangedpageXandY{#1}012\arrangedpageA %  ...
> \or \handlearrangedpageXandY{#1}002\arrangedpageB %  
> \or \handlearrangedpageXandY{#1}003\arrangedpageA %  
> \or \handlearrangedpageXandY{#1}013\arrangedpageB %  
> \or \handlearrangedpageXandY{#1}013\arrangedpageA %  
> \or \handlearrangedpageXandY{#1}003\arrangedpageB %  
> \or \handlearrangedpageXandY{#1}004\arrangedpageA %  
> \or \handlearrangedpageXandY{#1}014\arrangedpageB %  
> \or \handlearrangedpageXandY{#1}014\arrangedpageA %  
> \or \handlearrangedpageXandY{#1}004\arrangedpageB %  
>   \poparrangedpages
> \fi}
> 
> \definepapersize[Etiquette][width=80.0mm,height=50.0mm]
> \setuppapersize [Etiquette][A4]
> \setuparranging [2*5*double*2*5]
> %\setuplayout [margin=0pt, width=fit]
> \setuplayout[
> %location=middle,%nx=2,ny=5,
> %location=middle,
> location=left,
> marking=on,
> margin=0mm,
> topspace=0mm,
> backspace=0mm,
> width=fit,
> %header=0mm,
> %footer=0mm,
> %align=middle,
> ]
> 
> \showframe
> %\setuppagenumbering[state=stop]
> \setuppagenumbering[alternative=doublesided]
> 
> \starttext
> \dorecurse{20}{\vbox to \textheight{\vfill\midaligned{\tfd ABC}\vfill}\page}
> \stoptext
> ___
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
> 
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> ___

___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] new upload

2022-01-22 Thread Richard Mahoney via ntg-context
Thank you Kauśika, these details are v. helpful.


Best, Richard



-- 
T +6433121699  M +64210640216
rmaho...@indica-et-buddhica.org
https://indica-et-buddhica.org/

Indica et Buddhica
Littledene  Bay Road  Oxford  NZ




-Original Message-
From: kauśika via ntg-context 
Reply-To: mailing list for ConTeXt users 
To: mailing list for ConTeXt users 
Cc: kauśika 
Subject: Re: [NTG-context] new upload
Date: Sat, 22 Jan 2022 18:01:42 +0530
X-Spam-Score: 0.0

On Saturday, January 22, 2022 12:58:05 AM IST Hans Hagen via ntg-
context 
wrote:
> - initial indic transliteration support .. recent indic (font)
> experiences and transliteration tricks will be eplained by kauśika

Recently when we were troubled by incorrect rendering of certain
conjuncts in 
malayalam, Hans added a new font-feature. More below*, but first some 
background: from my testing, the main reason for the problems with
fonts seems 
to come from the varied interpretations and/or implementations of OTF 
specification. To add to this complexity there are two script tags
(v1, v2 in 
OTF and -one, -two in ConTeXt) for each writing system (script). While
there 
are fonts which work very well right away many others have issues and
the 
feature was added to somewhat alleviate these issues.

*The feature is 'indic'. It has two aspects: 'movematra' and
'conjuncts'.

conjuncts takes values: mixed | continue | quit | auto
movematra takes values: default | leftbeforebase | auto

By default 
indic=auto 
for indic scripts. So this "should work" in most cases. 

In case there are issues, I have seen that the following approach
usually 
yields best result in debugging:
 • try to switch between the -one and -two version of the features
(i.e. use 
the v1 or v2 OTF script tag): some fonts may have some rules defined
only under 
one of the script tags. (I am not an expert in fonts but with my
testing of 
free fonts I have seen this). 
 • if that does not fix (the particular issue), revert to a working
feature and 
then set the indic feature as indic={movematra=default,conjuncts=quit}
to see
 • Please see:
 https://www.mail-archive.com/ntg-context@ntg.nl/msg99691.html
 issues usually have a pattern (across languages/scripts so some hacks
might 
work)

For conjuncts, 'mixed' and 'auto' are synonymous. Setting
conjuncts=mixed 
ensures that for some fonts conjuncts with the reph forms are rendered
correctly. (This was tested with a relatively new font in malayalam
using the 
mlm2 script tag).

For problematic fonts, if one can identify which conjuncts work under
which 
script tag and/or with what settings for indic, then, using ConTeXt
feature 
sets one can easily fix rendering in documents by doing, for instance
 {\feature[=][devanagari-two] …}, and/or
 {\feature[=][devanagari-one] …} accordingly
 See the comprehensive wiki page: 
 https://wiki.contextgarden.net/Featuresets 
for more details on how such feautresets might be built and applied.

Now, a brief note on the transliterations macros. First, one specifies
that 
indic transliteration is desired with:
\usetransliteration[indic]

Now, one can transliterate sanskrit to and from various forms by using

\transliterate[scheme]{ … }
where scheme is one of:
    • iast to deva
    • deva to iast
    • deva to mlym
which are respectively the following schemes :
    • IAST → Devanagari
    • Devanagari → IAST
    • Devanagari → Malayalam
More schemes will be added in the near future for various other indic
scripts 
as well. Currently there is only support for sanskrit language, which
we can 
extend to other languages (wherever the script allows).

Additionally, there is also 
\definetransliteration[…][…]
which can be used to define a specific transliteration block.

So, one just sets vector accordingly to get the desired
transliteration block. 
Please see below a minimal example for both:

% SOF
\usetransliteration[indic]
\definetransliteration
    [MyIASTtoDeva]
    [color=blue,
 style=bold,
 language=sa,
 vector={iast to deva}]

\starttransliteration[MyIASTtoDeva]%[color=green]   can set a new
color here 
idaṁ śarīraṁ kaunteya kṣetramityabhidīyate.
etadyo vetti taṁ prāhuḥ kṣetrajña iti tadvidaḥ. 
\stoptransliteration

\transliteration[MyIASTtoDeva]{idaṁ śarīraṁ kaunteya
kṣetramityabhidīyate}

% or directly 
\transliterate[iast to deva]{idaṁ śarīraṁ kaunteya
kṣetramityabhidīyate}
% EOF

kauśika


__
_
If your question is of interest to others as well, please add an entry
to the Wiki!

maillist : ntg-context@ntg.nl /
http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
__
_

___
If your question is of interest to 

Re: [NTG-context] new upload

2022-01-22 Thread kauśika via ntg-context
On Saturday, January 22, 2022 12:58:05 AM IST Hans Hagen via ntg-context 
wrote:
> - initial indic transliteration support .. recent indic (font)
> experiences and transliteration tricks will be eplained by kauśika

Recently when we were troubled by incorrect rendering of certain conjuncts in 
malayalam, Hans added a new font-feature. More below*, but first some 
background: from my testing, the main reason for the problems with fonts seems 
to come from the varied interpretations and/or implementations of OTF 
specification. To add to this complexity there are two script tags (v1, v2 in 
OTF and -one, -two in ConTeXt) for each writing system (script). While there 
are fonts which work very well right away many others have issues and the 
feature was added to somewhat alleviate these issues.

*The feature is 'indic'. It has two aspects: 'movematra' and 'conjuncts'.

conjuncts takes values: mixed | continue | quit | auto
movematra takes values: default | leftbeforebase | auto

By default 
indic=auto 
for indic scripts. So this "should work" in most cases. 

In case there are issues, I have seen that the following approach usually 
yields best result in debugging:
 • try to switch between the -one and -two version of the features (i.e. use 
the v1 or v2 OTF script tag): some fonts may have some rules defined only under 
one of the script tags. (I am not an expert in fonts but with my testing of 
free fonts I have seen this). 
 • if that does not fix (the particular issue), revert to a working feature and 
then set the indic feature as indic={movematra=default,conjuncts=quit} to see
 • Please see:
 https://www.mail-archive.com/ntg-context@ntg.nl/msg99691.html
 issues usually have a pattern (across languages/scripts so some hacks might 
work)

For conjuncts, 'mixed' and 'auto' are synonymous. Setting conjuncts=mixed 
ensures that for some fonts conjuncts with the reph forms are rendered 
correctly. (This was tested with a relatively new font in malayalam using the 
mlm2 script tag).

For problematic fonts, if one can identify which conjuncts work under which 
script tag and/or with what settings for indic, then, using ConTeXt feature 
sets one can easily fix rendering in documents by doing, for instance
 {\feature[=][devanagari-two] …}, and/or
 {\feature[=][devanagari-one] …} accordingly
 See the comprehensive wiki page: 
 https://wiki.contextgarden.net/Featuresets 
for more details on how such feautresets might be built and applied.

Now, a brief note on the transliterations macros. First, one specifies that 
indic transliteration is desired with:
\usetransliteration[indic]

Now, one can transliterate sanskrit to and from various forms by using

\transliterate[scheme]{ … }
where scheme is one of:
• iast to deva
• deva to iast
• deva to mlym
which are respectively the following schemes :
• IAST → Devanagari
• Devanagari → IAST
• Devanagari → Malayalam
More schemes will be added in the near future for various other indic scripts 
as well. Currently there is only support for sanskrit language, which we can 
extend to other languages (wherever the script allows).

Additionally, there is also 
\definetransliteration[…][…]
which can be used to define a specific transliteration block.

So, one just sets vector accordingly to get the desired transliteration block. 
Please see below a minimal example for both:

% SOF
\usetransliteration[indic]
\definetransliteration
[MyIASTtoDeva]
[color=blue,
 style=bold,
 language=sa,
 vector={iast to deva}]

\starttransliteration[MyIASTtoDeva]%[color=green]   can set a new color here 
idaṁ śarīraṁ kaunteya kṣetramityabhidīyate.
etadyo vetti taṁ prāhuḥ kṣetrajña iti tadvidaḥ. 
\stoptransliteration

\transliteration[MyIASTtoDeva]{idaṁ śarīraṁ kaunteya kṣetramityabhidīyate}

% or directly 
\transliterate[iast to deva]{idaṁ śarīraṁ kaunteya kṣetramityabhidīyate}
% EOF

kauśika


___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] new upload

2022-01-22 Thread kauśika via ntg-context
On Saturday, January 22, 2022 3:55:12 PM IST Hans Hagen via ntg-context wrote:
> Is there a font out there that supports all these scripts in one font?

Shobhika font is a free font that has some of the largest number of glyphs 
(i.e has many conjuncts) for the Devanagari script.
https://github.com/Sandhi-IITBombay/Shobhika

The font also has a good Latin component based on PT Serif. This Latin part 
has good support for the roman (IAST) transliteration for Sanskrit. But 
strictly only the IAST spec character for Sanskrit are available.

It also has glyphs for some commonly used mathematical symbols.

Noto Serif Devanagari is also decent for just Devanagari (not sure of the IAST 
part).

As for Sans typefaces, Mukta Devanagari is a free font:
https://github.com/EkType/Mukta

Of these, Shobhika has the best conjunct coverage. I will shortly update the 
wiki with a much more exhaustive list and report here.
 
kauśika


___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] new upload

2022-01-22 Thread Hans Hagen via ntg-context

On 1/21/2022 9:11 PM, Henning Hraban Ramm via ntg-context wrote:

Am 21.01.22 um 20:28 schrieb Hans Hagen via ntg-context:
so we can have fixed values too .. will be explained in due time by 
Mikael (in manual) as we're still experimenting with all this


- initial indic transliteration support .. recent indic (font) 
experiences and transliteration tricks will be eplained by kauśika


I’m hoping for presentations / articles!
dedicated usag emanuals that can be 'articalized' but i'm sure the math 
will become an article anyway because of the (somewhat fundamental) 
extensions to the engine


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] new upload

2022-01-22 Thread Hans Hagen via ntg-context

On 1/22/2022 7:06 AM, Aditya Mahajan via ntg-context wrote:

On Fri, 21 Jan 2022, Hans Hagen via ntg-context wrote:


- initial indic transliteration support .. recent indic (font)
experiences and transliteration tricks will be eplained by kauśika


I finally thought that I'd try out how typesetting Hindi works with ConTeXt, 
but I don't get the correct output.

Input: आदित्य (See complete attached file)

Output: See attached.

Note that ि  "vowel sign I" should be attached to  द "letter  da" but it is attached to  
य "letter ya". Do I need to enable a particular feature?

Is there a font out there that supports all these scripts in one font?

Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] new upload

2022-01-22 Thread Hans Hagen via ntg-context

On 1/22/2022 8:21 AM, kauśika via ntg-context wrote:

On Saturday, January 22, 2022 11:36:57 AM IST Aditya Mahajan via ntg-context
wrote:

I finally thought that I'd try out how typesetting Hindi works with ConTeXt,
but I don't get the correct output.

Input: आदित्य (See complete attached file)

Output: See attached.

Note that ि  "vowel sign I" should be attached to  द "letter  da" but it is
attached to  य "letter ya". Do I need to enable a particular feature?


Unfortunately some fonts don't work properly in ConTeXt. Noto Sans Devanagari
is one of them. The accompanying serif font (Noto Serif Devanagari) works just
fine (mostly, there are problems with that as well).

In this specific case, there does not seem to be any fix (at least that I could
find).

I am trying to test many fonts and come up with a list of fonts which work,
partially work, don't work, etc. and fixes wherever possible.
Side note: we tested a lot and could find some hacks around font issues 
but in the end decided that adding some heuristics for (maybe whatever 
historic issues) makes no sense because eventually one ends up fighting 
heuristics. So, in the end we removed these fixing features and instead 
just do as announced above: tell what works and not with what fonts (and 
as some fonts are in development we can just wait till things work).


(it is a bit of a pity that support for indic scripts is such a weird 
mix of font technology and engine dependent reshuffling ... probably 
also driven by limitations of open type at that time)


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___


Re: [NTG-context] Engine mismatch in Windows 8.1 (32 bits)

2022-01-22 Thread Hans Hagen via ntg-context

On 1/22/2022 7:45 AM, Jairo A. del Rio via ntg-context wrote:
Hi everyone! I've just installed ConTeXt on an old machine running 
Windows 8.1 (x86) and I've noticed the format is regenerated each time I 
process a file. It can be read on the log (third line):


warning: engine mismatch (luv: This is LuaMetaTeX 2.09.36 <> bin: This 
is LuaMetaTeX 2.09.34), forcing remake


grep -r '09.34' finds a coincidence in mtxrun.exe. Is anyone else facing 
this issue?
Are mtxrun.exe and context.exe copies of luametatex.exe (or links to 
it)? They all should be the same.


Hans

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
   tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___