Re: [NTG-context] font expansion MkXL vs. MkIV

[Hans Hagen]

On 2/16/2020 9:22 PM, Pablo Rodriguez wrote:

Hi Wolfgang and Hans,

I have the following sample:

 \setuppapersize[A5]
 \definefontfeature[default][default]
 [protrusion=quality, expansion=quality]
 \definefontfamily[mainface][rm][Source Serif Pro]
 \setupalign[hanging, hz]
 \setupbodyfont[mainface, 17pt]
 %~ \setupbodyfont[helvetica, 17pt]
 \starttext
 \input zapf
 \stoptext

hz doesn’t work fine in MkXL, but it works fine in MkIV.

I think the flow of characters is broken in MKXL. Some

With TeX Gyre Heros (https://pdf.ousia.tk/mkiv-hz.pdf and
https://pdf.ousia.tk/mkxl-hz.pdf):

- "computer": line 5.
- "basic": line 8.
- "showing": line 10.

With Source Serif Pro, also (https://pdf.ousia.tk/ssp-mkiv-hz.pdf and
https://pdf.ousia.tk/ssp-mkxl-hz.pdf):

- "publishing": line 2.
- "about": line 4.
- "between": line 10.

I’m experiencing this wherever I use hz with MkXL.

Sorry, but cannot the default values for quality font expansion be the
same in MkIV and MkXL?

Many thanks for your help,
in lmtx there is more precise handling of edge cases (protrusion) that 
are ignored in mkiv ... so any difference that you observe can simply be 
a side effect of tex deciding otherwise (because these calculations do 
influence linebreaks)


anyway, you should use 'stretch' to because otherwise expansion and 
protrusion has not enough options to do better (the linebreak third pass 
that is)


\setupalign[hanging, stretch, hz]

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
___

[NTG-context] font expansion MkXL vs. MkIV

[Pablo Rodriguez]

Hi Wolfgang and Hans,

I have the following sample:

\setuppapersize[A5]
\definefontfeature[default][default]
[protrusion=quality, expansion=quality]
\definefontfamily[mainface][rm][Source Serif Pro]
\setupalign[hanging, hz]
\setupbodyfont[mainface, 17pt]
%~ \setupbodyfont[helvetica, 17pt]
\starttext
\input zapf
\stoptext

hz doesn’t work fine in MkXL, but it works fine in MkIV.

I think the flow of characters is broken in MKXL. Some

With TeX Gyre Heros (https://pdf.ousia.tk/mkiv-hz.pdf and
https://pdf.ousia.tk/mkxl-hz.pdf):

- "computer": line 5.
- "basic": line 8.
- "showing": line 10.

With Source Serif Pro, also (https://pdf.ousia.tk/ssp-mkiv-hz.pdf and
https://pdf.ousia.tk/ssp-mkxl-hz.pdf):

- "publishing": line 2.
- "about": line 4.
- "between": line 10.

I’m experiencing this wherever I use hz with MkXL.

Sorry, but cannot the default values for quality font expansion be the
same in MkIV and MkXL?

Many thanks for your help,

Pablo
--
http://www.ousia.tk
___
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] Chapter in header, but not on title page

[Henning Hraban Ramm]

> Am 2020-02-15 um 23:20 schrieb Pablo Rodriguez :
> 
> 
> On 2/15/20 9:16 PM, Henning Hraban Ramm wrote:
>> I guess I’m stupid.
>> I’d like to have my chapter title in the header on right pages, but
>> not on the first page of a chapter, that always is a right page.
>> Since I’d like to keep the page number in the header on these pages,
>> I can’t use header=empty.
>> What’s the right setup for me?
> 
> Hi Hraban,
> 
> I think this is what you intend:
>\definetext[chapter-first][header][][pagenumber]
> 
>\setuphead[chapter][%
>  page={yes, header, right},
>  header=chapter-first,
>]
> 
> Just in case it helps,

Thank you, that works in the example, but not in my actual project, and I 
didn’t find why.
But I found a workaround (used \setupheadertexts before and in the middle of 
the chapter).
In the end there was just one chapter left where the problem arose, since the 
other chapters use a different setup (double page intro).

Best, Hraban
___
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] Lucida small caps

[Hans Hagen]

On 2/15/2020 10:02 PM, Mikael P. Sundqvist wrote:
On Sat, Feb 15, 2020 at 9:50 PM Hans Hagen > wrote:


On 2/15/2020 4:34 PM, Mikael P. Sundqvist wrote:
 > Hi,
 >
 > One can easily enable small caps when using lucida, see the old mail
 > https://mailman.ntg.nl/pipermail/ntg-context/2018/090997.html .
 >
 > Could this be added to the type script file?

best use \smallcaps or somethign equivalent



Ah, so it was the \sc that was the problem. Thanks!
\sc is more somthing mkii ... when type1 fonts (in an 8 bit universum) 
smallcaps and oldstyle and such meant using a different font


nowadays one can turn them on/off as features and when you need them a 
lot you can even define an extra bodyfont variant from them and switch 
to that one when needed


now, when smallcaps and oldstyle etc became features instead of font 
properties that didn't mean it always became easier because when 
opentype came around there was no 'recipe' or possibility to define what 
is default; for instance some fonts default to oldstyle in the sense 
that these shapes are in the default slots and you need to turn them off 
instead; also one needs to keep in mind that some features are language 
/ script dependent and fonts differ in what they do default


summary: see smallcaps as features but always look at what the font 
assumes and does by default; be prepared for inconsistencies (after all 
this is why we want/need control over what context does with a 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] zip downloads / mirror

[Philipp Gesang]

2020-02-09 (Sunday), j.ha...@xs4all.nl (Hans Hagen):

> On 2/9/2020 1:07 PM, Philipp Gesang wrote:
> > I take it the “current” vs. “beta” model has been retired?
> 
> indeed, we're always latest now (as 'current' was mostly what ended up on
> tex live)

Thanks for clarifying. I’ve set up the mirror so the “beta”
branch will be continued from “latest”.

> > PS: I’m out of the loop; is the mirror actually still needed or
> >  is there an official repo now?
> Mojca is working on a repository setup for sources (what we have now but
> also including luametatex sources), installation (including binaries taken
> from the compile farm), extras (like modules taken from the garden
> repository) so at some point we can make those official. Till then it's nice
> to have the existing one.

Ok, I’ll keep it running.

Philipp



signature.asc
Description: PGP signature
___
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
___