[NTG-context] Re: slanted font feature: LMTX vs. MkIV

2023-09-02 Thread Wolfgang Schuster

Hans Hagen schrieb am 02.09.2023 um 11:53:

On 9/2/2023 11:45 AM, Wolfgang Schuster wrote:

Pablo Rodriguez schrieb am 02.09.2023 um 10:25:

Dear list,

I have the following sample (using current latest from 2023.08.27 
13:48):


   \setupinteractionscreen[option=max]
   \definefontfamily[maf][rm][DejaVu Sans]
 [sl={style:tf, features:{default,slanted}}]
   \setupbodyfont[maf, 8pt]
   \setupfittingpage[offset=1ex]
   \starttext
   \startTEXpage
   a {\em b}
   \stopTEXpage
   \startTEXpage[foregroundstyle={\setupbodyfont[100pt]}]
   a {\em b}
   \stopTEXpage
   \stoptext

Using LMTX higher font size gives less slanted text (or not at all).

Using MkIV text is slanted fine, independent from font size.

Could anyone confirm the issue?


I can confirm the slant decreases at larger font sizes.

\starttext

\dostepwiserecurse{10}{100}{1}
{{\switchtobodyfont[#1pt]#1pt:\definedfont[Serif*slanted]\vrule\relax 
S\vrule\relax lanted}\par}


\stoptext

in lpdf-lmt.lmt you can try:

l 593

tmsy = tmsy * sc

l 610

tmsy = tmsy * f_y_scale


I get now with LMTX the same output as I get with MkIV, the slant stays 
the same for all sizes.


Wolfgang

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

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

[NTG-context] Re: slanted font feature: LMTX vs. MkIV

2023-09-02 Thread Hans Hagen

On 9/2/2023 11:45 AM, Wolfgang Schuster wrote:

Pablo Rodriguez schrieb am 02.09.2023 um 10:25:

Dear list,

I have the following sample (using current latest from 2023.08.27 13:48):

   \setupinteractionscreen[option=max]
   \definefontfamily[maf][rm][DejaVu Sans]
 [sl={style:tf, features:{default,slanted}}]
   \setupbodyfont[maf, 8pt]
   \setupfittingpage[offset=1ex]
   \starttext
   \startTEXpage
   a {\em b}
   \stopTEXpage
   \startTEXpage[foregroundstyle={\setupbodyfont[100pt]}]
   a {\em b}
   \stopTEXpage
   \stoptext

Using LMTX higher font size gives less slanted text (or not at all).

Using MkIV text is slanted fine, independent from font size.

Could anyone confirm the issue?


I can confirm the slant decreases at larger font sizes.

\starttext

\dostepwiserecurse{10}{100}{1}
   {{\switchtobodyfont[#1pt]#1pt:\definedfont[Serif*slanted]\vrule\relax 
S\vrule\relax lanted}\par}


\stoptext

in lpdf-lmt.lmt you can try:

l 593

tmsy = tmsy * sc

l 610

tmsy = tmsy * f_y_scale

-
  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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___

[NTG-context] Re: slanted font feature: LMTX vs. MkIV

2023-09-02 Thread Wolfgang Schuster

Pablo Rodriguez schrieb am 02.09.2023 um 10:25:

Dear list,

I have the following sample (using current latest from 2023.08.27 13:48):

   \setupinteractionscreen[option=max]
   \definefontfamily[maf][rm][DejaVu Sans]
 [sl={style:tf, features:{default,slanted}}]
   \setupbodyfont[maf, 8pt]
   \setupfittingpage[offset=1ex]
   \starttext
   \startTEXpage
   a {\em b}
   \stopTEXpage
   \startTEXpage[foregroundstyle={\setupbodyfont[100pt]}]
   a {\em b}
   \stopTEXpage
   \stoptext

Using LMTX higher font size gives less slanted text (or not at all).

Using MkIV text is slanted fine, independent from font size.

Could anyone confirm the issue?


I can confirm the slant decreases at larger font sizes.

\starttext

\dostepwiserecurse{10}{100}{1}
  {{\switchtobodyfont[#1pt]#1pt:\definedfont[Serif*slanted]\vrule\relax 
S\vrule\relax lanted}\par}


\stoptext

Wolfgang

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

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

[NTG-context] slanted font feature: LMTX vs. MkIV

2023-09-02 Thread Pablo Rodriguez
Dear list,

I have the following sample (using current latest from 2023.08.27 13:48):

  \setupinteractionscreen[option=max]
  \definefontfamily[maf][rm][DejaVu Sans]
[sl={style:tf, features:{default,slanted}}]
  \setupbodyfont[maf, 8pt]
  \setupfittingpage[offset=1ex]
  \starttext
  \startTEXpage
  a {\em b}
  \stopTEXpage
  \startTEXpage[foregroundstyle={\setupbodyfont[100pt]}]
  a {\em b}
  \stopTEXpage
  \stoptext

Using LMTX higher font size gives less slanted text (or not at all).

Using MkIV text is slanted fine, independent from font size.

Could anyone confirm the issue?

Many thanks for your help,

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

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


Re: [NTG-context] Odd/even page test

2018-10-17 Thread Procházka Lukáš Ing .

Hello Pablo,

that's it, thank you!

Lukas


On Tue, 16 Oct 2018 17:58:04 +0200, Pablo Rodriguez  wrote:


On 10/16/18 4:25 PM, Procházka Lukáš Ing. wrote:

Hello,

I need to check whether even or odd page is to be printed. I'm starting with 
the following simple code:


\def\T{\ifodd\pagenumber ODD\else EVEN\fi}

\starttext
   \dorecurse{2}{\T\page}
   \startTEXpage[width=50mm,height=150mm]\stopTEXpage
   \dorecurse{2}{\T\page}
\stoptext



Hi Lukáš,

both makeups and fitting pages aren’t numbered by default.

Either you add this to the preamble:

  \setupfittingpage[TEXpage][pagestate=start]

or you add the option "pagestate=start" to \startTEXpage.

I hope it helps,

Pablo



Why "user defined page" #3 is skipped in page numbering, so headers shown are:
1 - 2 - (nothing) - 3 - 4 and "ODD"/"EVEN" and text is "ODD" - "EVEN" - (nothing) - 
"ODD" - "EVEN"
instead of:
1 - 2 - (nothing) - 4 - 5 and "ODD"/"EVEN" and text be "ODD" - "EVEN" - (nothing) - 
"EVEN" - "ODD"?

TIA.

Best regards,

Lukas



--
Ing. Lukáš Procházka | mailto:l...@pontex.cz
Pontex s. r. o.  | mailto:pon...@pontex.cz | http://www.pontex.cz | IDDS: 
nrpt3sn | IČO: 40763439
Bezová 1658
147 14 Praha 4

Mob.: +420 702 033 396

___
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] Odd/even page test

2018-10-16 Thread Pablo Rodriguez
On 10/16/18 4:25 PM, Procházka Lukáš Ing. wrote:
> Hello,
> 
> I need to check whether even or odd page is to be printed. I'm starting with 
> the following simple code:
> 
> 
> \def\T{\ifodd\pagenumber ODD\else EVEN\fi}
> 
> \starttext
>\dorecurse{2}{\T\page}
>\startTEXpage[width=50mm,height=150mm]\stopTEXpage
>\dorecurse{2}{\T\page}
> \stoptext
> 

Hi Lukáš,

both makeups and fitting pages aren’t numbered by default.

Either you add this to the preamble:

  \setupfittingpage[TEXpage][pagestate=start]

or you add the option "pagestate=start" to \startTEXpage.

I hope it helps,

Pablo


> Why "user defined page" #3 is skipped in page numbering, so headers shown are:
>   1 - 2 - (nothing) - 3 - 4 and "ODD"/"EVEN" and text is "ODD" - "EVEN" - 
> (nothing) - "ODD" - "EVEN"
> instead of:
>   1 - 2 - (nothing) - 4 - 5 and "ODD"/"EVEN" and text be "ODD" - "EVEN" - 
> (nothing) - "EVEN" - "ODD"?
> 
> TIA.
> 
> Best regards,
> 
> Lukas
> 
> 
> 
> ___
> 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
> ___
> 


-- 
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] A document composed only of TEXpages

2016-03-04 Thread Hans Hagen

On 3/3/2016 7:49 PM, Chicho Pep wrote:

Hello everybody,

I would like to have a document composed of TEXpages only, where each
TEXpage contains one whole subsection or section. I have achieved that
indeed, but I don't get to understand how the numbering of pages works
in this case. I've tried to use \setcounter[userpage][\pagenumber+1].


TEXpage etc is probably not the best mechanism to use for that as it is 
just a vbox


in the test suite there is a file experiment-001.tex that shows you a 
trick (maybe that should be module)



Here is my document:

***

\setupinteraction[state=start]

\startsetups[myTEXpagesetup]
   \setupwhitespace[line]
   \setuptolerance[space]
\stopsetups

\setupfittingpage[TEXpage]
   [command=\texsetup{myTEXpagesetup},
height=fit,
width=210mm,
offset=10mm]

\starttext

\startTEXpage
\startsection[title={My Section}]
\placecontent
\stopTEXpage

\setcounter[userpage][\pagenumber+1]

\startTEXpage
\startsubsection[title={My First Subsection}]
Contents
\stopsubsection
\stopTEXpage

\setcounter[userpage][\pagenumber+1]

\startTEXpage
\startsubsection[title={My Second Subsection}]
Contents
\stopsubsection
\stopTEXpage

\setcounter[userpage][\pagenumber+1]

\startTEXpage
\startsubsection[title={My Third Subsection}]
Contents
\stopsubsection
\stopTEXpage

\stopsection

\stoptext

***

The PDF browser numbers the pages correctly, and in this case they get
numbers 1 to 4. But the generated list of contents in page 1 says that
section "My Third Subsection" is in page 3 instead of 4, though the link
correctly jumps to page 4. The (sub)section in the last TEXpage of the
document gets always numbered as if it would be in the next to last TEXpage.

To make the list of contents look good, I may add one last empty TEXpage
at the end of the document. But I'd still like to ask how, or if, it
would be possible to make this use case work without that trick.

There's a pair more things:

When the document is composed of only one single TEXpage, then that page
gets number 0 in the PDF browser, instead of number 1.

When I don't use \setcounter[userpage][\pagenumber+1] in between the
TEXpages, they get numbers 1,1,1,2 in the PDF browser, while the list of
contents says my subsections are in pages 1,1,0 (but the links jump
always to the correct page).

Thank you for your help

Pep

p.s. As PDF browsers, I use Evince, Okular and Firefox's built-in PDF Viewer

p.p.s. I love ConTeXt :)



___
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___




--

-
  Hans Hagen | PRAGMA ADE
  Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: 038 477 53 69 | www.pragma-ade.com | 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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

[NTG-context] A document composed only of TEXpages

2016-03-04 Thread Chicho Pep
Hello everybody,

I would like to have a document composed of TEXpages only, where each
TEXpage contains one whole subsection or section. I have achieved that
indeed, but I don't get to understand how the numbering of pages works in
this case. I've tried to use \setcounter[userpage][\pagenumber+1]. Here is
my document:

***

\setupinteraction[state=start]

\startsetups[myTEXpagesetup]
  \setupwhitespace[line]
  \setuptolerance[space]
\stopsetups

\setupfittingpage[TEXpage]
  [command=\texsetup{myTEXpagesetup},
   height=fit,
   width=210mm,
   offset=10mm]

\starttext

\startTEXpage
\startsection[title={My Section}]
\placecontent
\stopTEXpage

\setcounter[userpage][\pagenumber+1]

\startTEXpage
\startsubsection[title={My First Subsection}]
Contents
\stopsubsection
\stopTEXpage

\setcounter[userpage][\pagenumber+1]

\startTEXpage
\startsubsection[title={My Second Subsection}]
Contents
\stopsubsection
\stopTEXpage

\setcounter[userpage][\pagenumber+1]

\startTEXpage
\startsubsection[title={My Third Subsection}]
Contents
\stopsubsection
\stopTEXpage

\stopsection

\stoptext

***

The PDF browser numbers the pages correctly, and in this case they get
numbers 1 to 4. But the generated list of contents in page 1 says that
section "My Third Subsection" is in page 3 instead of 4, though the link
correctly jumps to page 4. The (sub)section in the last TEXpage of the
document gets always numbered as if it would be in the next to last TEXpage.

To make the list of contents look good, I may add one last empty TEXpage at
the end of the document. But I'd still like to ask how, or if, it would be
possible to make this use case work without that trick.

There's a pair more things:

When the document is composed of only one single TEXpage, then that page
gets number 0 in the PDF browser, instead of number 1.

When I don't use \setcounter[userpage][\pagenumber+1] in between the
TEXpages, they get numbers 1,1,1,2 in the PDF browser, while the list of
contents says my subsections are in pages 1,1,0 (but the links jump always
to the correct page).

Thank you for your help

Pep

p.s. As PDF browsers, I use Evince, Okular and Firefox's built-in PDF Viewer

p.p.s. I love ConTeXt :)
___
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___

Re: [NTG-context] tolerance and whitespace settings inside a TEXpage

2012-09-20 Thread Wolfgang Schuster

Am 20.09.2012 um 11:56 schrieb Marco Patzer home...@lavabit.com:

 Hi,
 
 inside a TEXpage the tolerance and the whitespace settings are not
 applied. The whitespace can be set in a setup and the tolerance can
 be set directly with \spaceskip, but that seems a bit hackish.
 
 Is that intended and is there a cleaner solution? Example:
 
 \setuplayout   [width=8cm]
 \setupbodyfont [mono]
 \startsetups [myset]
  \setupwhitespace [big]
  \setuptolerance  [space]
 \stopsetups
 \setups{myset}
 
 \starttext
  \startTEXpage [setups=myset]
%% \spaceskip .5em plus .25em minus .25em
\input knuth
  \stopTEXpage
 
  \input knuth
 \stoptext


The problem here is that your setups are used but the value from the align
key overwrite them which can’t be changed. One solution is to put 
\texsetup{myset}
after \startTEXpage but this has to be done for each page, the better solution 
is
to misuse the command key to flush the setups content.

\setuplayout   [width=8cm]
\setupbodyfont [mono]

\startsetups [myset]

  \setupwhitespace [big]
  \setuptolerance  [space]

\stopsetups

\setupfittingpage[TEXpage][command=\texsetup{myset}]

\starttext

\startTEXpage
\input knuth
\stopTEXpage

\input knuth

\stoptext

Wolfgang
___
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] MetaFUN's \setupMPpage broken? [SOLVED]

2011-12-28 Thread Verhaag, G.C.H.M.

On 12/27/2011 04:07 PM, Wolfgang Schuster wrote:

Am 27.12.2011 um 14:26 schrieb Verhaag, G.C.H.M.:

   

Hi Wolfgang and John,

Both ways work well, thanks a lot! Does this mean that the setupMPpage command 
will become obsolete in near future?

Are both suggestions documented somewhere or is this mailing list the only way 
to find out?
 

It’s already obsolete as you noticed by the “undefined control sequence” 
warning.

The reason for this is that \startMPpage and \startTEXpage are now defined in a 
different
way than they had been in MkII. In MkII both commands are defined with 
\def\startMPpage{…}
and \def\startTEXpage{…} but in MkIV both are a instance of fittingpage and the 
definition
for them is \definefittingpage[MPpage] and \definefittingpage[TEXpage]. As a 
consequence
the old \setupMPpage command is also gone and you have to set global settings 
with
\setupfittingpage[environment][settings].

Such a changes do happen with many commands in MkIV and the setup-commands
for them are moved to the underlying mechanism (e.g. fittingpage).

Wolfgang
...
   


Hi Wolfgang,

Thank you very much for your prompt explanation!

Regards,
Gerard Verhaag
___
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] MetaFUN's \setupMPpage broken? [SOLVED]

2011-12-27 Thread Verhaag, G.C.H.M.

On 12/27/2011 12:24 PM, Wolfgang Schuster wrote:

Am 27.12.2011 um 11:35 schrieb Verhaag, G.C.H.M.:

   

Hi ConTeXt user's,

A few weeks ago I upgraded to the 11-11-29 version (MkIV) and today installed 
the 11-12-23 version (MkIV). The \setupMPpage command in the basic example 
below:

 \setupMPpage[offset=1pt]

  \startuseMPgraphic{test}
   fill fullsquare rotated 45 ;
  \stopuseMPgraphic

  \starttext
   \startMPpage
\includeMPgraphic{test}
   \stopMPpage
  \stoptext

yields the following error in both versions mentioned above:

 ! Undefined control sequence.
 system  tex  error on line 1 in file test.tex: Undefined control 
sequence ...

All this worked just fine in the version of last August!
 

Use \setupfittingpage[MPpage][…=…].

Wolfgang

..
   

Hi Wolfgang and John,

Both ways work well, thanks a lot! Does this mean that the setupMPpage 
command will become obsolete in near future?


Are both suggestions documented somewhere or is this mailing list the 
only way to find out?


Regards,
Gerard Verhaag
___
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] MetaFUN's \setupMPpage broken?

2011-12-27 Thread Wolfgang Schuster

Am 27.12.2011 um 11:35 schrieb Verhaag, G.C.H.M.:

 Hi ConTeXt user's,
 
 A few weeks ago I upgraded to the 11-11-29 version (MkIV) and today installed 
 the 11-12-23 version (MkIV). The \setupMPpage command in the basic example 
 below:
 
 \setupMPpage[offset=1pt]
  
  \startuseMPgraphic{test}
   fill fullsquare rotated 45 ;
  \stopuseMPgraphic
  
  \starttext
   \startMPpage
\includeMPgraphic{test}
   \stopMPpage
  \stoptext
 
 yields the following error in both versions mentioned above:
 
 ! Undefined control sequence.
 system   tex  error on line 1 in file test.tex: Undefined 
 control sequence ...
 
 All this worked just fine in the version of last August!

Use \setupfittingpage[MPpage][…=…].

Wolfgang
___
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] MetaFUN's \setupMPpage broken? [SOLVED]

2011-12-27 Thread Wolfgang Schuster

Am 27.12.2011 um 14:26 schrieb Verhaag, G.C.H.M.:

 Hi Wolfgang and John,
 
 Both ways work well, thanks a lot! Does this mean that the setupMPpage 
 command will become obsolete in near future?
 
 Are both suggestions documented somewhere or is this mailing list the only 
 way to find out?

It’s already obsolete as you noticed by the “undefined control sequence” 
warning.

The reason for this is that \startMPpage and \startTEXpage are now defined in a 
different
way than they had been in MkII. In MkII both commands are defined with 
\def\startMPpage{…}
and \def\startTEXpage{…} but in MkIV both are a instance of fittingpage and the 
definition
for them is \definefittingpage[MPpage] and \definefittingpage[TEXpage]. As a 
consequence
the old \setupMPpage command is also gone and you have to set global settings 
with
\setupfittingpage[environment][settings].

Such a changes do happen with many commands in MkIV and the setup-commands
for them are moved to the underlying mechanism (e.g. fittingpage). 

Wolfgang
___
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___