[NTG-context] removing many lines about font in log.

[Jeong Dal]

Hi,

The following example creates so many lines of messages about fonts in the log.

\definefontfeature [default] [default] [script=hang,language=kor]

\starttext
\definedfont[file:notoserifcjkkrregular*default]
Korean sentences.

한글이 아름답습니다.
\stoptext

fonts   > 'fallback modern-designsize rm 12pt' is loaded
fonts   > defining > font 'notoserifcjkkrregular', feature 'vert', 
script 'grek', no language 'kor'
fonts   > defining > font 'notoserifcjkkrregular', feature 'vert', 
script 'latn', no language 'kor'
fonts   > defining > font 'notoserifcjkkrregular', feature 'vert', 
script 'kana', no language 'kor'
fonts   > defining > font 'notoserifcjkkrregular', feature 'vert', 
script 'cyrl', no language 'kor'
fonts   > defining > font 'notoserifcjkkrregular', feature 'vert', 
script 'dflt', no language 'kor'
fonts   > defining > f
...

Is there a way to suppress messages?
Of course, there is no problem to get the output.

Best regards,

Dalyoung

___
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] \type{...} as macro argument

[Sylvain Hubert]

On Sun, 8 Nov 2020 at 18:27, Wolfgang Schuster <
wolfgang.schuster.li...@gmail.com> wrote:

> Sylvain Hubert schrieb am 08.11.2020 um 17:56:
> > Hi Wolfgang,
> >
> > I'm sorry that the question was not clear enough. Let me ask in this way:
> > how to define a \dorecurse, such that \dorecurse{10}{\type{ab c}}
> > does not squash the spaces?
>
> Verbatim in arguments of other commands is tricky because in case with
> \dorecurse the loop reads the content before it is passed to type, as a
> result of this process all spaces are collapsed.
>
> One way to work around this is to use a buffer for the content of the loop.
>
> \startbuffer[type]
> \type{ab c}
> \stopbuffer
>
> \starttext
> \dorecurse{10}{\inlinebuffer[type]\par}
> \stoptext
>

Many thanks for the answer!
It seems that the buffer mechanism is quite a powerful resort for the macro
language.

Sylvain
___
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] \type{...} as macro argument

[Wolfgang Schuster]

Sylvain Hubert schrieb am 08.11.2020 um 17:56:

Hi Wolfgang,

I'm sorry that the question was not clear enough. Let me ask in this way:
how to define a \dorecurse, such that \dorecurse{10}{\type{a    b c}} 
does not squash the spaces?


Verbatim in arguments of other commands is tricky because in case with 
\dorecurse the loop reads the content before it is passed to type, as a 
result of this process all spaces are collapsed.


One way to work around this is to use a buffer for the content of the loop.

\startbuffer[type]
\type{ab c}
\stopbuffer

\starttext
\dorecurse{10}{\inlinebuffer[type]\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 / 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] \type{...} as macro argument

[Sylvain Hubert]

Hi Wolfgang,

I'm sorry that the question was not clear enough. Let me ask in this way:
how to define a \dorecurse, such that \dorecurse{10}{\type{ab c}} does
not squash the spaces?

Sylvain

On Sun, 8 Nov 2020 at 15:03, Wolfgang Schuster <
wolfgang.schuster.li...@gmail.com> wrote:

> Sylvain Hubert schrieb am 08.11.2020 um 14:47:
> > Dear List,
> >
> > I would like to ask how to define a command, \same, such that
> >
> >  \same{\type{a   b c}}
> >
> > produces the same result as its argument does
> >
> >  \type{a   b c}
> >
> > The naive way doesn't work because it makes all the spaces collapse:
> >
> >  \define[1]\same{#1}
>
>
> \definetype [typeTEX] [option=tex]
>
> \starttext
>
> \type{\startsection[title=\tex{type}]}
>
> \typeTEX{\startsection[title=\tex{typeTEX}]}
>
> \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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] \type{...} as macro argument

[Wolfgang Schuster]

Sylvain Hubert schrieb am 08.11.2020 um 14:47:

Dear List,

I would like to ask how to define a command, \same, such that

     \same{\type{a   b c}}

produces the same result as its argument does

     \type{a   b c}

The naive way doesn't work because it makes all the spaces collapse:

     \define[1]\same{#1}



\definetype [typeTEX] [option=tex]

\starttext

\type{\startsection[title=\tex{type}]}

\typeTEX{\startsection[title=\tex{typeTEX}]}

\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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] "page i/n" in footer

[Sylvain Hubert]

On Sun, 8 Nov 2020 at 13:44, Pablo Rodriguez  wrote:

> On 11/8/20 11:48 AM, Sylvain Hubert wrote:
> > Indeed, \setupfooterexts is much clearer for page numbering. Thanks for
> > the help!.
> >
> > Btw, do you know whether there is any difference between \lastpagenumber
> > and \lastuserpagenumber mentioned both by Wolfgang and by the excursion
> > book ?
>
> Besides Wolfgang’s reply (way far more authoritative than mine), my
> approach is basic.
>
> grep the and read the source:
>
>   $ grep -irl lastpagenumber ~/lmtx
> ~/lmtx/mlib-int.lua
> ~/lmtx/mlib-int.lmt
> ~/lmtx/meta-pag.mkiv
> ~/lmtx/mult-def.lua
> ~/lmtx/strc-pag.mkxl
> ~/lmtx/strc-pag.mkiv
>
> ~/lmtx is only a symlink for
> ~/context/tex/texmf-context/tex/context/base/mkiv/.
>
> I created that symlink, because grepping for commands or options is a
> way to learn by reading the code.
>
> Not that I understand the whole, but I see which options are available
> and I can check some samples included.
>
> strc-pag.mkxl is your friend here. There are three page series. You
> could even create more page series (not normally needed).
>

Thank you very much for the pointers. It does save me from drowning in the
code base as I have been for multiple occasions.

Sylvain
___
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] \type{...} as macro argument

[Sylvain Hubert]

Dear List,

I would like to ask how to define a command, \same, such that

\same{\type{a   b c}}

produces the same result as its argument does

\type{a   b c}

The naive way doesn't work because it makes all the spaces collapse:

\define[1]\same{#1}

I would also like to ask whether this could be achieved using the lua
interface:

\startluacode
interfaces.definecommand {
   name="same",
   -- catcode/mode/arguments = ???
}

Thanks in advance.

Best,
Sylvain
___
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] issues with fonts and font effects

[Pablo Rodriguez]

On 11/8/20 11:36 AM, Wolfgang Schuster wrote:
> Pablo Rodriguez schrieb am 08.11.2020 um 11:22:
>> [...]
>> With all features defined, paragraph width is wrong using
>> "effect={width=1.0}".
>
> Add auto=yes: \definefontfeature [ef1] [effect={width=1.0,auto=yes}]

Many thanks for your explanation, Wolfgang.

The "auto" key is news to me. I thought this was the default before.

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] "page i/n" in footer

[Pablo Rodriguez]

On 11/8/20 11:48 AM, Sylvain Hubert wrote:
> Indeed, \setupfooterexts is much clearer for page numbering. Thanks for
> the help!.
>
> Btw, do you know whether there is any difference between \lastpagenumber
> and \lastuserpagenumber mentioned both by Wolfgang and by the excursion
> book ?

Besides Wolfgang’s reply (way far more authoritative than mine), my
approach is basic.

grep the and read the source:

  $ grep -irl lastpagenumber ~/lmtx
~/lmtx/mlib-int.lua
~/lmtx/mlib-int.lmt
~/lmtx/meta-pag.mkiv
~/lmtx/mult-def.lua
~/lmtx/strc-pag.mkxl
~/lmtx/strc-pag.mkiv

~/lmtx is only a symlink for
~/context/tex/texmf-context/tex/context/base/mkiv/.

I created that symlink, because grepping for commands or options is a
way to learn by reading the code.

Not that I understand the whole, but I see which options are available
and I can check some samples included.

strc-pag.mkxl is your friend here. There are three page series. You
could even create more page series (not normally needed).

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] temporarily move up a section title

[Sylvain Hubert]

On Sun, 8 Nov 2020 at 10:12, Wolfgang Schuster <
wolfgang.schuster.li...@gmail.com> wrote:

> Sylvain Hubert schrieb am 08.11.2020 um 03:19:
> > Dear List,
> >
> > I'm trying to move up a section title (section b) 2cm upward:
> >
> >  \starttext
> >  \section{a}
> >  \blank[-2cm,force]\
>
> \blank[back,disable]
>
> Wolfgang
>

Works as a charm! Thanks!

Sylvain
___
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] weird behavior of font.feature.effect

[Wolfgang Schuster]

Sylvain Hubert schrieb am 08.11.2020 um 13:02:
On Sun, 8 Nov 2020 at 11:24, Pablo Rodriguez > wrote:


Hi Sylvain,

this is the same as:

   \definefontfamily[face1][rm][gabriola]

Just in case, "slanted" is an already defined feature. It slants the
font.

 >     \definefontfamily[face2][rm][gabriola][it={features:{default,
 > effect={}}}]
 >     \definefontfamily[face3][rm][gabriola][it={features:{default,
 > effect={width=1.0}}}]

BTW, the documentation is clear

(http://texdoc.net/texmf-dist/doc/context/presentations/bachotex/2018/bachotex-2018-fonteffects.pdf#search=fontfeature):
font features should be defined as such before being deployed.

 > Could someone explain:

I will try from what I understand.

 > 1. What does "effect" mean?

A ConTeXt (and not OpenType) font feature?

 > Why does "effect={}" embolden the fonts even though nothing ({}) is
 > given as arguments?
"effect={}" may be reading default values (it might be intended behavior
or not).

But it also could be reading or calculating from previously defined
values.

 > 2. Similarly, what does "width" do? Why does "width=1.0" shrink the
 > width of the line instead of doing nothing?

This might be a bug, because of all the code improvements.

I’m reporting a proper bug.


Thank you very much for the explanation and the bug report!

Just in case it helps: the line shrinking disappears with an additional 
"delta=0":


     \definefontfamily[face3][rm][gabriola][it={features:{default, 
effect={width=1.0, delta=0}}}]



Don't set the values within \definefontfamily:

\definefontfeature [myfeature] [effect={width=1.0, delta=0}]

\definefontfamily[face3][rm][gabriola][it={features:{default,myfeature}}]

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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] temporarily move up a section title

[Sylvain Hubert]

Hi Hraban,

On Sun, 8 Nov 2020 at 07:57, Henning Hraban Ramm  wrote:

>
>
> > Am 08.11.2020 um 03:19 schrieb Sylvain Hubert :
> >
> > Dear List,
> >
> > I'm trying to move up a section title (section b) 2cm upward:
> >
> > \starttext
> > \section{a}
> > \blank[-2cm,force]\
> > \section{b}
> > \section{c}
> > \stoptext
> >
> > The empty space (\ ) after the \blank is necessary here, without which
> the \blank does nothing.
> > I would like to ask whether there is a less hacky way to let \blank work
> than the hidden space.
>
> You could use the low level method of \vskip-2cm
>

Indeed this is a clearer hack.
Thank you for the suggestion!

Sylvain
___
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] \switchtobodyfont behaves differenctly with splitted parameters

[Sylvain Hubert]

On Sun, 8 Nov 2020 at 12:52, Hans Hagen  wrote:

> On 11/8/2020 12:46 PM, Sylvain Hubert wrote:
> > On Sun, 8 Nov 2020 at 12:14, Hans Hagen  > > wrote:
> >
> > when yyou use several bodyfonts you can do this before \starttext:
> >
> > \usebodyfont[face,24pt]
> > \usebodyfont[deface]
> >
> > \starttext
> > 
> > \stoptext
> >
> >
> > Thank you for the information, Hans!
> >
> > Could you please also shed some light on the relation/difference among
> > \{setup,switchto,use}bodyfont?
> > There seems to be not much documentation on this. Can one conclude, from
> > the wiki  and
> > the source code
> > <
> https://source.contextgarden.net/tex/context/base/mkiv/font-ini.mklx#l2287>,
>
> > that they are mostly the same, except that \switchtobodyfont is
> > restricted to the content area, and \usebodyfont is a helper to call
> > \setupbodyfont in the beginning?
> >
> > If this is the case, is it recommended to always put a
> > \setupbodyfont[...] in the beginning, even if it's just a
> > \setupbodyfont[modern]?
> > One reason might be that the following example somehow enlarges the page
> > number in the header, intuitively contradicting what is claimed by the
> > wiki :
> >
> >  \switchtobodyfont[dejavu]
> >  \starttext \switchtobodyfont[dejavu, 24pt]a\stoptext
>
> \setup  is document wide
> \switch is for local usage
>

So \switchtobodyfont before \starttext is semantically an error then.
Thanks for the confirmation!


> (has to do with picking up font/space related issues after page breaks
> and when typesetting page ornaments like headers and footers)
>
>
>
> -
>Hans Hagen | PRAGMA ADE
>Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -
>

Sylvain
___
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] weird behavior of font.feature.effect

[Sylvain Hubert]

On Sun, 8 Nov 2020 at 11:24, Pablo Rodriguez  wrote:

> Hi Sylvain,
>
> this is the same as:
>
>   \definefontfamily[face1][rm][gabriola]
>
> Just in case, "slanted" is an already defined feature. It slants the font.
>
> > \definefontfamily[face2][rm][gabriola][it={features:{default,
> > effect={}}}]
> > \definefontfamily[face3][rm][gabriola][it={features:{default,
> > effect={width=1.0}}}]
>
> BTW, the documentation is clear
> (
> http://texdoc.net/texmf-dist/doc/context/presentations/bachotex/2018/bachotex-2018-fonteffects.pdf#search=fontfeature
> ):
> font features should be defined as such before being deployed.
>
> > Could someone explain:
>
> I will try from what I understand.
>
> > 1. What does "effect" mean?
>
> A ConTeXt (and not OpenType) font feature?
>
> > Why does "effect={}" embolden the fonts even though nothing ({}) is
> > given as arguments?
> "effect={}" may be reading default values (it might be intended behavior
> or not).
>
> But it also could be reading or calculating from previously defined values.
>
> > 2. Similarly, what does "width" do? Why does "width=1.0" shrink the
> > width of the line instead of doing nothing?
>
> This might be a bug, because of all the code improvements.
>
> I’m reporting a proper bug.
>

Thank you very much for the explanation and the bug report!

Just in case it helps: the line shrinking disappears with an additional
"delta=0":

\definefontfamily[face3][rm][gabriola][it={features:{default,
effect={width=1.0, delta=0}}}]

Sylvain
___
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] \switchtobodyfont behaves differenctly with splitted parameters

[Hans Hagen]

On 11/8/2020 12:46 PM, Sylvain Hubert wrote:
On Sun, 8 Nov 2020 at 12:14, Hans Hagen > wrote:


when yyou use several bodyfonts you can do this before \starttext:

\usebodyfont[face,24pt]
\usebodyfont[deface]

\starttext
    
\stoptext


Thank you for the information, Hans!

Could you please also shed some light on the relation/difference among 
\{setup,switchto,use}bodyfont?
There seems to be not much documentation on this. Can one conclude, from 
the wiki  and 
the source code 
, 
that they are mostly the same, except that \switchtobodyfont is 
restricted to the content area, and \usebodyfont is a helper to call 
\setupbodyfont in the beginning?


If this is the case, is it recommended to always put a 
\setupbodyfont[...] in the beginning, even if it's just a 
\setupbodyfont[modern]?
One reason might be that the following example somehow enlarges the page 
number in the header, intuitively contradicting what is claimed by the 
wiki :


     \switchtobodyfont[dejavu]
     \starttext \switchtobodyfont[dejavu, 24pt]a\stoptext


\setup  is document wide
\switch is for local usage

(has to do with picking up font/space related issues after page breaks 
and when typesetting page ornaments like headers and footers)




-
  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] \switchtobodyfont behaves differenctly with splitted parameters

[Sylvain Hubert]

On Sun, 8 Nov 2020 at 12:14, Hans Hagen  wrote:

> when yyou use several bodyfonts you can do this before \starttext:
>
> \usebodyfont[face,24pt]
> \usebodyfont[deface]
>
> \starttext
>
> \stoptext
>

Thank you for the information, Hans!

Could you please also shed some light on the relation/difference among
\{setup,switchto,use}bodyfont?
There seems to be not much documentation on this. Can one conclude, from the
wiki  and the source
code
,
that they are mostly the same, except that \switchtobodyfont is restricted
to the content area, and \usebodyfont is a helper to call \setupbodyfont in
the beginning?

If this is the case, is it recommended to always put a \setupbodyfont[...]
in the beginning, even if it's just a \setupbodyfont[modern]?
One reason might be that the following example somehow enlarges the page
number in the header, intuitively contradicting what is claimed by the wiki
:

\switchtobodyfont[dejavu]
\starttext \switchtobodyfont[dejavu, 24pt]a\stoptext

Thanks!

Sylvain
___
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] \setupindenting[first] not working

[Denis Maier]

Use\setupheads[indentnext=yes]BestDenis
 Ursprüngliche Nachricht Von: Sylvain Hubert 
 Datum: 08.11.20  03:44  (GMT+01:00) An: mailing list 
for ConTeXt users  Betreff: [NTG-context] 
\setupindenting[first] not working Dear List,The first paragraph of the 
following example is not indented.    \setupindenting[yes,first,4cm]    
\starttext    \section{a}        \dorecurse{84}{abc }        \dorecurse{84}{abc 
}        \stoptextDoes anyone know how to actually get the first paragraph 
indented?Thanks!Best,Sylvain
___
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] "page i/n" in footer

[Wolfgang Schuster]

Sylvain Hubert schrieb am 08.11.2020 um 12:19:
On Sun, 8 Nov 2020 at 12:07, Wolfgang Schuster 
> wrote:


Sylvain Hubert schrieb am 08.11.2020 um 11:48:
> On Sun, 8 Nov 2020 at 10:31, Pablo Rodriguez mailto:oi...@gmx.es>
> >> wrote:
>
>     Hi Sylvain,
>
>        \setupfootertexts[\pagenumber/\lastpagenumber]
>        \starttext
>        \dorecurse{25}{\null\page}
>        \stoptext
>
>
> Indeed, \setupfooterexts is much clearer for page numbering.
Thanks for
> the help!.
>
> Btw, do you know whether there is any difference between
\lastpagenumber
> and \lastuserpagenumber mentioned both by Wolfgang and by the
excursion
> book ?

\defineconversionset [bodypart:pagenumber] [] [Romannumerals]

\startsetups [footer]
     \starttabulate[|l|c|c|]
     \NC \bf Command          \NC \bf Current page \NC \bf Last page
   \NC\NR
     \NC \tex{pagenumber}     \NC \pagenumber      \NC
\lastpagenumber
   \NC\NR
     \NC \tex{userpagenumber} \NC \userpagenumber  \NC
\lastuserpagenumber \NC\NR
     \stoptabulate
\stopsetups

\setupfootertexts[\directsetup{footer}]

\starttext

\dorecurse{10}{\dontleavehmode\page}
\stoptext


Thanks, so basically \(last-)userpagenumber is a configurable 
descendent  of \(last-)pagenumber if I've got the right message from 
this example?


\pagenumber and \lastpagenumber are the raw values which can be used to 
calculate
the difference between both etc. while \userpagenumber and 
\lastuserpagenumber
are the formatted result of these values. The latter are needed when you 
apply

a conversion to the page number (e.g. roman numberals in the frontmatter).

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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] "page i/n" in footer

[Sylvain Hubert]

On Sun, 8 Nov 2020 at 12:07, Wolfgang Schuster <
wolfgang.schuster.li...@gmail.com> wrote:

> Sylvain Hubert schrieb am 08.11.2020 um 11:48:
> > On Sun, 8 Nov 2020 at 10:31, Pablo Rodriguez  > > wrote:
> >
> > Hi Sylvain,
> >
> >\setupfootertexts[\pagenumber/\lastpagenumber]
> >\starttext
> >\dorecurse{25}{\null\page}
> >\stoptext
> >
> >
> > Indeed, \setupfooterexts is much clearer for page numbering. Thanks for
> > the help!.
> >
> > Btw, do you know whether there is any difference between \lastpagenumber
> > and \lastuserpagenumber mentioned both by Wolfgang and by the excursion
> > book ?
>
> \defineconversionset [bodypart:pagenumber] [] [Romannumerals]
>
> \startsetups [footer]
>  \starttabulate[|l|c|c|]
>  \NC \bf Command  \NC \bf Current page \NC \bf Last page
>\NC\NR
>  \NC \tex{pagenumber} \NC \pagenumber  \NC \lastpagenumber
>\NC\NR
>  \NC \tex{userpagenumber} \NC \userpagenumber  \NC
> \lastuserpagenumber \NC\NR
>  \stoptabulate
> \stopsetups
>
> \setupfootertexts[\directsetup{footer}]
>
> \starttext

\dorecurse{10}{\dontleavehmode\page}
> \stoptext
>

Thanks, so basically \(last-)userpagenumber is a configurable descendent
of \(last-)pagenumber if I've got the right message from this example?

Sylvain
___
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] \switchtobodyfont behaves differenctly with splitted parameters

[Hans Hagen]

On 11/8/2020 12:02 PM, Sylvain Hubert wrote:
On Sun, 8 Nov 2020 at 11:37, Pablo Rodriguez > wrote:


On 11/8/20 11:18 AM, Sylvain Hubert wrote:
 > Hi Pablo,
 >
 > thanks for the suggestion. Here's the minimal example which shows the
 > difference:
 >
 >     \definefontfamily[face][rm][dejavuserif]
 >     \starttext\switchtobodyfont[face, 24pt]ɑ\stoptext
 >
 > this should warn:
 >
 >     fonts           > checking > char ɑ (U+00251) in font
 > 'LatinModernMath-Regular-4' with id 10: missing

Well, you are switching before setting up a body font.

I don’t know whether this might be a bug in ConTeXt (see previous
report), but I would set up the body font always first:

     \definefontfamily[face][rm][dejavuserif]
     \definefontfamily[deface][rm][dejavusans]
     \setupbodyfont[deface]
     \starttext a\switchtobodyfont[face, 24pt]ɑ\stoptext


Thanks, it works!

And I agree that it probably indicates the existence of a bug, since by 
changing "\setupbodyfont[deface]" to "\setupbodyfont[dejavu]" in your 
example, the problem reappears:


     \definefontfamily[face][rm][dejavuserif]
     \setupbodyfont[dejavu]
     \starttext a\switchtobodyfont[face, 24pt]ɑ\stoptext

when yyou use several bodyfonts you can do this before \starttext:

\usebodyfont[face,24pt]
\usebodyfont[deface]

\starttext
  
\stoptext


-
  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] "page i/n" in footer

[Wolfgang Schuster]

Sylvain Hubert schrieb am 08.11.2020 um 11:48:
On Sun, 8 Nov 2020 at 10:31, Pablo Rodriguez > wrote:


Hi Sylvain,

   \setupfootertexts[\pagenumber/\lastpagenumber]
   \starttext
   \dorecurse{25}{\null\page}
   \stoptext


Indeed, \setupfooterexts is much clearer for page numbering. Thanks for 
the help!.


Btw, do you know whether there is any difference between \lastpagenumber 
and \lastuserpagenumber mentioned both by Wolfgang and by the excursion 
book ?


\defineconversionset [bodypart:pagenumber] [] [Romannumerals]

\startsetups [footer]
\starttabulate[|l|c|c|]
\NC \bf Command  \NC \bf Current page \NC \bf Last page 
  \NC\NR
\NC \tex{pagenumber} \NC \pagenumber  \NC \lastpagenumber 
  \NC\NR
\NC \tex{userpagenumber} \NC \userpagenumber  \NC 
\lastuserpagenumber \NC\NR

\stoptabulate
\stopsetups

\setupfootertexts[\directsetup{footer}]

\starttext
\dorecurse{10}{\dontleavehmode\page}
\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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] \switchtobodyfont behaves differenctly with splitted parameters

[Wolfgang Schuster]

Sylvain Hubert schrieb am 08.11.2020 um 12:02:
On Sun, 8 Nov 2020 at 11:37, Pablo Rodriguez > wrote:


On 11/8/20 11:18 AM, Sylvain Hubert wrote:
 > Hi Pablo,
 >
 > thanks for the suggestion. Here's the minimal example which shows the
 > difference:
 >
 >     \definefontfamily[face][rm][dejavuserif]
 >     \starttext\switchtobodyfont[face, 24pt]ɑ\stoptext
 >
 > this should warn:
 >
 >     fonts           > checking > char ɑ (U+00251) in font
 > 'LatinModernMath-Regular-4' with id 10: missing

Well, you are switching before setting up a body font.

I don’t know whether this might be a bug in ConTeXt (see previous
report), but I would set up the body font always first:

     \definefontfamily[face][rm][dejavuserif]
     \definefontfamily[deface][rm][dejavusans]
     \setupbodyfont[deface]
     \starttext a\switchtobodyfont[face, 24pt]ɑ\stoptext


Thanks, it works!

And I agree that it probably indicates the existence of a bug, since by 
changing "\setupbodyfont[deface]" to "\setupbodyfont[dejavu]" in your 
example, the problem reappears:


     \definefontfamily[face][rm][dejavuserif]


Add here: \definebodyfont[24pt]

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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] \switchtobodyfont behaves differenctly with splitted parameters

[Sylvain Hubert]

On Sun, 8 Nov 2020 at 11:37, Pablo Rodriguez  wrote:

> On 11/8/20 11:18 AM, Sylvain Hubert wrote:
> > Hi Pablo,
> >
> > thanks for the suggestion. Here's the minimal example which shows the
> > difference:
> >
> > \definefontfamily[face][rm][dejavuserif]
> > \starttext\switchtobodyfont[face, 24pt]ɑ\stoptext
> >
> > this should warn:
> >
> > fonts   > checking > char ɑ (U+00251) in font
> > 'LatinModernMath-Regular-4' with id 10: missing
>
> Well, you are switching before setting up a body font.
>
> I don’t know whether this might be a bug in ConTeXt (see previous
> report), but I would set up the body font always first:
>
> \definefontfamily[face][rm][dejavuserif]
> \definefontfamily[deface][rm][dejavusans]
> \setupbodyfont[deface]
> \starttext a\switchtobodyfont[face, 24pt]ɑ\stoptext
>

Thanks, it works!

And I agree that it probably indicates the existence of a bug, since by
changing "\setupbodyfont[deface]" to "\setupbodyfont[dejavu]" in your
example, the problem reappears:

\definefontfamily[face][rm][dejavuserif]
\setupbodyfont[dejavu]
\starttext a\switchtobodyfont[face, 24pt]ɑ\stoptext

Sylvain
___
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] "page i/n" in footer

[Sylvain Hubert]

On Sun, 8 Nov 2020 at 10:31, Pablo Rodriguez  wrote:

> Hi Sylvain,
>
>   \setupfootertexts[\pagenumber/\lastpagenumber]
>   \starttext
>   \dorecurse{25}{\null\page}
>   \stoptext
>

Indeed, \setupfooterexts is much clearer for page numbering. Thanks for the
help!.

Btw, do you know whether there is any difference between \lastpagenumber
and \lastuserpagenumber mentioned both by Wolfgang and by the excursion book
?


>
> I never used you approach with \setuppagenubering (all being said).
>
> This might help,
>
___
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] "page i/n" in footer

[Sylvain Hubert]

Many thanks for the help!

On Sun, 8 Nov 2020 at 10:20, Wolfgang Schuster <
wolfgang.schuster.li...@gmail.com> wrote:

> Sylvain Hubert schrieb am 08.11.2020 um 02:58:
> > Dear List,
> >
> > Does anyone know how to set the footer to be "page i/n" where i=current
> > page number, n=total number of page? I've tried
> >
> >  \setuppagenumbering[location=footer, command=\groupedcommand{page
> > }{/\lastcounter[userpage]}]
> >
> > but \lastcounter[userpage] results in empty string.
>
>
> \setuppagenumbering
>[ left={Page },
> right={/\lastuserpagenumber}]
>
> \starttext
> \unknown
> \stoptext
>
> or
>
>
> \setuppagenumbering
>[location=]
>
> \setupfootertexts
>[Page \userpagenumber/\lastuserpagenumber]
>
> \starttext
> \unknown
> \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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] issues with fonts and font effects

[Wolfgang Schuster]

Pablo Rodriguez schrieb am 08.11.2020 um 11:22:

Hans,

this sample comes from Sylvain’s message:

 %~ \definefontfeature[ef1][effect={width=1.0}]
 \definefontfeature[ef2][effect={width=}]
 \definefontfamily[face1][rm][gabriola]
 [features={default, ef1}]
 \definefontfamily[face2][rm][gabriola]
 [features={default, ef2}]
 \starttext
 \switchtobodyfont[face1]\dorecurse{100}{a b c }

 \switchtobodyfont[face2]\dorecurse{100}{a b c }

 \switchtobodyfont[palatino]\dorecurse{100}{a b c }
 \stoptext

\setupbodyfont[palatino] or \switchtobodyfont[palatino] don’t seem to
work at all.

Results are different if feature ef1 is defined or not.


It's best to check these things first with \definefont to ensure it 
isn't a problem of \definefontfamily.



With all features defined, paragraph width is wrong using
"effect={width=1.0}".


Add auto=yes: \definefontfeature [ef1] [effect={width=1.0,auto=yes}]

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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] \switchtobodyfont behaves differenctly with splitted parameters

[Pablo Rodriguez]

On 11/8/20 11:18 AM, Sylvain Hubert wrote:
> Hi Pablo,
>
> thanks for the suggestion. Here's the minimal example which shows the
> difference:
>
>     \definefontfamily[face][rm][dejavuserif]
>     \starttext\switchtobodyfont[face, 24pt]ɑ\stoptext
>
> this should warn:
>
>     fonts           > checking > char ɑ (U+00251) in font
> 'LatinModernMath-Regular-4' with id 10: missing

Well, you are switching before setting up a body font.

I don’t know whether this might be a bug in ConTeXt (see previous
report), but I would set up the body font always first:

\definefontfamily[face][rm][dejavuserif]
\definefontfamily[deface][rm][dejavusans]
\setupbodyfont[deface]
\starttext a\switchtobodyfont[face, 24pt]ɑ\stoptext

> while
>
>     \definefontfamily[face][rm][dejavuserif]
>     \starttext\switchtobodyfont[face, 24pt]ɑ\stoptext
>
> produces the expected result despite a harmless warning.

I guess the command reads:

\switchtobodyfont[face]ɑ

This might also be related to the issue just reported.

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] \switchtobodyfont behaves differenctly with splitted parameters

[Sylvain Hubert]

On Sun, 8 Nov 2020 at 11:18, Sylvain Hubert  wrote:

> Hi Pablo,
>
> thanks for the suggestion. Here's the minimal example which shows the
> difference:
>
> \definefontfamily[face][rm][dejavuserif]
> \starttext\switchtobodyfont[face, 24pt]ɑ\stoptext
>
> this should warn:
>
> fonts   > checking > char ɑ (U+00251) in font
> 'LatinModernMath-Regular-4' with id 10: missing
>
> while
>
> \definefontfamily[face][rm][dejavuserif]
> \starttext\switchtobodyfont[face, 24pt]ɑ\stoptext
>

sorry, this should read

\definefontfamily[face][rm][dejavuserif]
\starttext\switchtobodyfont[face]\switchtobodyfont[24pt]ɑ\stoptext



> produces the expected result despite a harmless warning.
>
> Sylvain
>
>
___
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] issues with fonts and font effects

[Pablo Rodriguez]

Hans,

this sample comes from Sylvain’s message:

%~ \definefontfeature[ef1][effect={width=1.0}]
\definefontfeature[ef2][effect={width=}]
\definefontfamily[face1][rm][gabriola]
[features={default, ef1}]
\definefontfamily[face2][rm][gabriola]
[features={default, ef2}]
\starttext
\switchtobodyfont[face1]\dorecurse{100}{a b c }

\switchtobodyfont[face2]\dorecurse{100}{a b c }

\switchtobodyfont[palatino]\dorecurse{100}{a b c }
\stoptext

\setupbodyfont[palatino] or \switchtobodyfont[palatino] don’t seem to
work at all.

Results are different if feature ef1 is defined or not.

With all features defined, paragraph width is wrong using
"effect={width=1.0}".

Could you check this?

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] weird behavior of font.feature.effect

[Pablo Rodriguez]

On 11/8/20 12:57 AM, Sylvain Hubert wrote:
> Dear List,
>
> I'm confused by the result of the following example (see attached):
>
>     \definefontfamily[face1][rm][gabriola][it={features:{default}}]

Hi Sylvain,

this is the same as:

  \definefontfamily[face1][rm][gabriola]

Just in case, "slanted" is an already defined feature. It slants the font.

>     \definefontfamily[face2][rm][gabriola][it={features:{default,
> effect={}}}]
>     \definefontfamily[face3][rm][gabriola][it={features:{default,
> effect={width=1.0}}}]

BTW, the documentation is clear
(http://texdoc.net/texmf-dist/doc/context/presentations/bachotex/2018/bachotex-2018-fonteffects.pdf#search=fontfeature):
font features should be defined as such before being deployed.

> Could someone explain:

I will try from what I understand.

> 1. What does "effect" mean?

A ConTeXt (and not OpenType) font feature?

> Why does "effect={}" embolden the fonts even though nothing ({}) is
> given as arguments?
"effect={}" may be reading default values (it might be intended behavior
or not).

But it also could be reading or calculating from previously defined values.

> 2. Similarly, what does "width" do? Why does "width=1.0" shrink the
> width of the line instead of doing nothing?

This might be a bug, because of all the code improvements.

I’m reporting a proper bug.

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] \switchtobodyfont behaves differenctly with splitted parameters

[Sylvain Hubert]

Hi Pablo,

thanks for the suggestion. Here's the minimal example which shows the
difference:

\definefontfamily[face][rm][dejavuserif]
\starttext\switchtobodyfont[face, 24pt]ɑ\stoptext

this should warn:

fonts   > checking > char ɑ (U+00251) in font
'LatinModernMath-Regular-4' with id 10: missing

while

\definefontfamily[face][rm][dejavuserif]
\starttext\switchtobodyfont[face, 24pt]ɑ\stoptext

produces the expected result despite a harmless warning.

Sylvain

On Sun, 8 Nov 2020 at 10:41, Pablo Rodriguez  wrote:

> On 11/8/20 2:35 AM, Sylvain Hubert wrote:
> > Dear List,
> >
> > after hours of debugging, I finally found out that
> > \switchtobodyfont[face, 20pt] does NOT behave the same with
> > \switchtobodyfont[face]\switchtobodyfont[20pt]. In my case the latter is
> > the correct one, while the former does nothing but falling back to
> > latinmodern.
> >
> > Does anyone know when or why \switchtobodyfont behaves differently with
> > splitted and joined parameters?
>
> Hi Sylvain,
>
> as a general rule, it helps when there is a minimal sample that provides
> the problematic behavior.
>
> I don’t get diffferent results:
>
>   \definefontfamily[mainface][rm][TeX Gyre Pagella]
>   \definefontfamily[face][rm][TeX Gyre Heros]
>   \setupbodyfont[mainface]
>   \startbuffer
>   In my case, the latter is the correct one, while the former does
>   nothing but falling back to latinmodern.\par
>   \stopbuffer
>
>   \starttext
>   \getbuffer
>   \switchtobodyfont[face]\switchtobodyfont[20pt]
>   \getbuffer
>   \switchtobodyfont[face, 20pt]
>   \getbuffer
>   \stoptext
>
> Correct the sample to show what I got wrong from your message.
>
> 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
>
> ___
>
___
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] \switchtobodyfont behaves differenctly with splitted parameters

[Pablo Rodriguez]

On 11/8/20 2:35 AM, Sylvain Hubert wrote:
> Dear List,
>
> after hours of debugging, I finally found out that
> \switchtobodyfont[face, 20pt] does NOT behave the same with
> \switchtobodyfont[face]\switchtobodyfont[20pt]. In my case the latter is
> the correct one, while the former does nothing but falling back to
> latinmodern.
>
> Does anyone know when or why \switchtobodyfont behaves differently with
> splitted and joined parameters?

Hi Sylvain,

as a general rule, it helps when there is a minimal sample that provides
the problematic behavior.

I don’t get diffferent results:

  \definefontfamily[mainface][rm][TeX Gyre Pagella]
  \definefontfamily[face][rm][TeX Gyre Heros]
  \setupbodyfont[mainface]
  \startbuffer
  In my case, the latter is the correct one, while the former does
  nothing but falling back to latinmodern.\par
  \stopbuffer

  \starttext
  \getbuffer
  \switchtobodyfont[face]\switchtobodyfont[20pt]
  \getbuffer
  \switchtobodyfont[face, 20pt]
  \getbuffer
  \stoptext

Correct the sample to show what I got wrong from your message.

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] \setupindenting[first] not working

[Wolfgang Schuster]

Sylvain Hubert schrieb am 08.11.2020 um 03:43:

Dear List,

The first paragraph of the following example is not indented.

     \setupindenting[yes,first,4cm]
     \starttext
     \section{a}

     \dorecurse{84}{abc }

     \dorecurse{84}{abc }

     \stoptext

Does anyone know how to actually get the first paragraph indented?


\setuphead
  [section]
  [indentnext=yes]

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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] "page i/n" in footer

[Pablo Rodriguez]

On 11/8/20 2:58 AM, Sylvain Hubert wrote:
> Dear List,
>
> Does anyone know how to set the footer to be "page i/n" where i=current
> page number, n=total number of page? I've tried
>
>     \setuppagenumbering[location=footer, command=\groupedcommand{page
> }{/\lastcounter[userpage]}]
>
> but \lastcounter[userpage] results in empty string.

Hi Sylvain,

  \setupfootertexts[\pagenumber/\lastpagenumber]
  \starttext
  \dorecurse{25}{\null\page}
  \stoptext

I never used you approach with \setuppagenubering (all being said).

This might 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] "page i/n" in footer

[Wolfgang Schuster]

Sylvain Hubert schrieb am 08.11.2020 um 02:58:

Dear List,

Does anyone know how to set the footer to be "page i/n" where i=current 
page number, n=total number of page? I've tried


     \setuppagenumbering[location=footer, command=\groupedcommand{page 
}{/\lastcounter[userpage]}]


but \lastcounter[userpage] results in empty string.



\setuppagenumbering
  [ left={Page },
   right={/\lastuserpagenumber}]

\starttext
\unknown
\stoptext

or


\setuppagenumbering
  [location=]

\setupfootertexts
  [Page \userpagenumber/\lastuserpagenumber]

\starttext
\unknown
\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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] ConTeXt Linux installation issues (due to GLIBC dependency) - Solved!

[Mojca Miklavec]

Dear Ramkumar,

On Sat, 7 Nov 2020 at 02:10, Ramkumar KB wrote:
>
> Hello All,
>
> This turned out to be an issue with the texmf-context.zip file version 
> mismatch. I updated to version 1.04 and was able to install successfully!
>
> However, I would like to contribute a section to Wiki on how to install 
> ConTeXt in Linux machines which does not have the proper GLIBC version. This 
> is especially true with RHEL 7.x versions - which is still the majority 
> installation in companies & institutions with RHEL subscription.

I'm sorry. We have VMs with an older version of Debian for building,
but those don't provide sufficiently recent build tools (cmake, git,
ninja build system, ... I believe that CMake was the main blocker, but
I'm no longer absolutely sure).

By far the easiest solution was to switch from Debian 8 to 9 (or
something like that, I should check the exact numbers) and you might
be the first one bringing the issue up. I was aware that switching to
a newer Debian version might have caused compatibility issues with
RHEL / CentOS. (Do you happen to have some matrix of glibc versions on
RHEL / CentOS?)

> The section will cover GLIBC 2.24 install, patchelf utility and the changes 
> needed to ConTeXt install scripts for such an installation.
>
> How can I go about contributing to the wiki?

Do you have trouble creating a new account on the wiki?

Mojca
___
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] \define in conflict with \startxtable[]

[Wolfgang Schuster]

Sylvain Hubert schrieb am 08.11.2020 um 04:54:

Dear List,

Could anyone manage to typeset the following example? Here [] causes an 
error "Extra }, or forgotten \endgroup".


     \starttext
     \define\sample{
     \startxtable[]
     \startxtablehead
     \startxrow
     \startxcell 123\stopxcell
     \stopxrow
     \stopxtablehead
     \stopxtable
     }
     \sample
     \stoptext



\starttext

\define\sample
  {\startembeddedxtable
 \startxrow
   \startxcell \unknown \stopxcell
 \stopxrow
   \stopembeddedxtable}

\sample

\stoptext


or


\starttext

\startbuffer[sample]
  \startxtable
\startxrow
  \startxcell \unknown \stopxcell
\stopxrow
  \stopxtable
\stopbuffer

\getbuffer[sample]

\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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___

Re: [NTG-context] temporarily move up a section title

[Wolfgang Schuster]

Sylvain Hubert schrieb am 08.11.2020 um 03:19:

Dear List,

I'm trying to move up a section title (section b) 2cm upward:

     \starttext
     \section{a}
     \blank[-2cm,force]\


\blank[back,disable]

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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___