[NTG-context] Strangely placed dot

[Mikael P. Sundqvist]

Hi,

what is going on with the placement of the dot in this example, and how can
I avoid it?

\starttext
\startTEXpage[offset=3bp]
$E_tE_s=E_{\min(t,s)}$.

\switchtobodyfont[stixtwo]$E_tE_s=E_{\min(t,s)}$.

\switchtobodyfont[lucidaot]$E_tE_s=E_{\min(t,s)}$.
\stopTEXpage
\stoptext

Output attached.

/Mikael


punkt.pdf
Description: Adobe PDF document
___
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] unwanted vertical spaces after sectionhead in column layout

[Damien Thiriet]

Hello list,


Looks like lmtx adds extra vertical space after heads.
Compare those two MWE:

\setuppapersize [S4]
\setuphead [subject] [after={}]

\starttext
\startsubject[title={blabla}]
\input knuth
\stopsubject

\stoptext


\setuppapersize [S4]
\setuphead [subject] [after={}]
\starttext
\startcolumns [n=3]
\startsubject[title={blabla}]
\input knuth
\stopsubject
\stopcolumns
\stoptext

Greetings,

Damien Thiriet (missing BachoTeX)
___
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] [ibmplex setup script]

[Floris van Manen]

At present the ibmplexmonothin font is seen by the mtxrun script

 mtxrun --script fonts --list --all --pattern=ibmplexmonothin*
identifier  familynamefontnamefilename
subfont   instances

ibmplexmonothin ibmplexmono   ibmplexmonothin
/home/vm/.local/share/fonts/Unknown Vendor/OpenType/IBM Plex
Mono/IBM_Plex_Mono_Thin.otf
ibmplexmonothinitalic   ibmplexmono   ibmplexmonothinitalic
/home/vm/.local/share/fonts/Unknown Vendor/OpenType/IBM Plex
Mono/IBM_Plex_Mono_Thin_Italic.otf

But I don't manage to get the monothin variants loaded.
Any hints available?


Thanks
.Floris



pEpkey.asc
Description: application/pgp-keys
___
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] module article-basic interferes with \definebodyfont?

[Hans Hagen]

On 5/1/2020 1:15 PM, Gerben Wierda wrote:

The following code:

\enabletrackers[context.trace]

%\usemodule[article-basic]

\starttypescript [sans] [optima]
    \setups[font:fallback:sans]
    \definefontsynonym [Sans]           [file:Optima.ttc(Optima 
Regular)]     [features=default]
    \definefontsynonym [SansBold]       [file:Optima.ttc(Optima Bold)]   
      [features=default]
    \definefontsynonym [SansItalic]     [file:Optima.ttc(Optima Italic)] 
      [features=default]
    \definefontsynonym [SansBoldItalic] [file:Optima.ttc(Optima Bold 
Italic)] [features=default]

\stoptypescript

\definetypeface [optima] [ss] [sans] [optima] [default]


 \definetypeface [optima] [rm] [sans] [optima] [default]
 \definetypeface [optima] [tt] [mono] [dejavu]




\setupbodyfont [optima]

\starttext

\startMPpage[instance=doublefun]
   picture pic;
pic := textext("\definebodyfont[14.9pt][rm][default=Regular at 
14.9pt]\switchtobodyfont[14.9pt]\setupinterlinespace[16.9pt]\framed[align=center,frame=off,offset=none,width=335.350bp]{\colored[r=0.000, 
g=0.000, b=0.000]{\rm (Artifact)\\}}");

draw pic scaled 1.13;
\stopMPpage

\stoptext

Produces nice Optima at 14.9pt without \usemodule[article-basic] (as 
above), but with \usemodule[article-basic] included, the output becomes 
some serif (modern?) font, /but only if I use nonstandard font sizes/.


Took me some time to hunt this one down.

I actually don’t know what article-basic does for me (I started out with 
an example given to me by Hans) and I don’t need it now, but I might 
need it later in combination with my own stuff


G

___
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
___




--

-
  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] \definehead behaving differently when in an environment file versus \input'ed

[ntg]

> On 2 May 2020, at 17:08, Wolfgang Schuster 
>  wrote:

[comprehensive answer snipped]

Thank-you, very helpful.

> I attached a slightly modified version of your project structure to show a 
> different way to organize documents. What I would change is to use a better 
> section name for each article, e.g. \Article (or \startArticle) is better 
> than \MyTitle as first level header in each article.

Agreed - the \MyTitle was just for the example. Your structure is nice though - 
less complicated than the one I cobbled together looking at the Wiki example.

--
Bruce Horrocks
Hampshire, UK

___
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] \definehead behaving differently when in an environment file versus \input'ed

[Wolfgang Schuster]

n...@scorecrow.com schrieb am 02.05.2020 um 17:14:

I'm having trouble with \definehead behaving differently depending upon whether 
I process a file that includes it via a \input statement versus a project 
structure that calls it via an environment file referenced from a component 
file.

Overall aim:

I currently produce a small circulation journal in Word that I'm hoping to 
switch to ConTeXt. Each article is written by a different author and I 
currently provide a Word template so they can see how their article will 
eventually look and how long it is, etc. I want to do the same for the ConTeXt 
version so I have created a template tex file they can simply \input at the top 
of their article. Processing the single article gives the desired output. So 
far so good.

When I receive the articles, I want to use the project/product/component 
structure to allow me to produce an entire issue of the journal in one go. (I 
would simply comment out the \input line and add \startproject \startcomponent 
etc lines as necessary from each received article.)

Problem:

I've created a custom chapter heading, but the font size changes depending on 
whether I'm processing the \input version of the article or the \component 
version and I don't know why. Obviously, I would like the heading to be the 
same in each case so that authors see what I see and vice versa.


Your simple version sets the bodyfont before \starttext

 begin example
\setupbodyfont[termes,14pt]

\starttext

{\bfc Cheesy double boxed title}

\stoptext
 end example

while your complexer version loads the bodyfont after \starttext 
(\startcomponent acts here as \starttext)


 begin example
\starttext

\setupbodyfont[termes,14pt]

{\bfc Cheesy double boxed title}

\stoptext
 end example

When you use a non standard font size (e.g. 14pt) size switches are 
sometimes ignored even with ConTeXt's fallback mechanism.


To get the correct size for the header you can either use a standard 
font size (14.4pt) or you add the following line before you set the 
global font for your document (ConTeXt does this by itself in most cases 
but it can fail).


\definebodyfontenvironment [14pt]

I attached a slightly modified version of your project structure to show 
a different way to organize documents. What I would change is to use a 
better section name for each article, e.g. \Article (or \startArticle) 
is better than \MyTitle as first level header in each article.


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] Blank page added after pagecolumns

[Joey McCollum]

I recently found the pagecolumns manual (
http://www.pragma-ade.com/general/manuals/pagecolumns.pdf), and in several
of the examples (including those for side floats and footnotes), the
addition of a blank page after the end of the pagecolumns environment also
seems to occur. So when the manual says, "We always start at a new page and
end on a new one," does it mean that this is a feature of pagecolumns? And
if so, is there any way to disable it? I have no problem with a page break
after the end of the pagecolumns environment, but an empty page added after
the break seems unnecessary. I checked for a wiki page on the
\definepagecolumns command to get more information on its accepted inputs,
but there doesn't appear to be a page for this command.

Joey

On Tue, Apr 28, 2020 at 1:40 PM Joey McCollum 
wrote:

> I am typesetting a document using pagecolumns to ensure that my footnotes
> are set ragged-bottom in columns. I have observed some unexpected behavior
> whenever the last column on a page is left incomplete: a blank page is
> added at the end of the document. A minimal working example follows:
>
> ```
>
> \starttext
>
> \startpagecolumns[n=2]
>
> \dorecurse{3}{\par\input zapf}
>
> \stoppagecolumns
>
> \stoptext
> ```
>
> I typeset this using ConTeXt version 2020.03.10, as released with TeXLive
> 2020. Notably, if \dorecurse{3} is changed to \dorecurse{2} or
> \dorecurse{6} (so that the text ends in the first column of a page), then
> there is no problem. I have tried to fix this by specifying page=no in the
> \startpagecolumns arguments, but it did not change anything. Is there
> something else I am missing?
>
> Thank you,
>
> Joey
>
___
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] \definehead behaving differently when in an environment file versus \input'ed

[ntg]

And the attachment (d'oh):
<>
___
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] \definehead behaving differently when in an environment file versus \input'ed

[ntg]

I'm having trouble with \definehead behaving differently depending upon whether 
I process a file that includes it via a \input statement versus a project 
structure that calls it via an environment file referenced from a component 
file.

Overall aim:

I currently produce a small circulation journal in Word that I'm hoping to 
switch to ConTeXt. Each article is written by a different author and I 
currently provide a Word template so they can see how their article will 
eventually look and how long it is, etc. I want to do the same for the ConTeXt 
version so I have created a template tex file they can simply \input at the top 
of their article. Processing the single article gives the desired output. So 
far so good.

When I receive the articles, I want to use the project/product/component 
structure to allow me to produce an entire issue of the journal in one go. (I 
would simply comment out the \input line and add \startproject \startcomponent 
etc lines as necessary from each received article.)

Problem:

I've created a custom chapter heading, but the font size changes depending on 
whether I'm processing the \input version of the article or the \component 
version and I don't know why. Obviously, I would like the heading to be the 
same in each case so that authors see what I see and vice versa.

I've attached a small zip file with a directory structure containing a minimal 
example. There are two directories: "input_version" and "project" version and 
the article.pdf files in each show the difference in the heading.

I'm using TeX Live 2020 on a Mac. The console reports: ConTeXt  ver: 2020.03.10 
14:44 MKIV beta  fmt: 2020.4.18  int: english/english

--
Bruce Horrocks
Hampshire, UK

___
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] followtext, lmt_followtext and an offset of the glyphs typeset along the path

[ntg]

> On 1 May 2020, at 17:33, Gerben Wierda  wrote:
> 
> 
> 
>> On 1 May 2020, at 17:10, Henning Hraban Ramm  wrote:
>> 
>> 
>> 
>>> Am 01.05.2020 um 10:26 schrieb Gerben Wierda :
>>> 
>>> I have been looking at lmt_followtext and followtext to get typesetting 
>>> done along a path. That works fine, except that in my case, I need the text 
>>> to not be exactly on that path, I need it to hover slightly above tor below 
>>> he path. Given that the path may have an unpredictable form, that means 
>>> that all the glyphs need to be shifted a bit, there is no generic transfrom 
>>> of the entire text string that will work,
>> 
>> Can’t you duplicate and shift the path, i.e. keep the original visible and 
>> make the copy that carries the text invisible? That’s what I would do in a 
>> graphical application, but I would be surprised if MP wouldn’t know a 
>> transformation for this purpose.
> 
> No, that is what I did in the example, fiddling, but there is no 
> transformation that will work in all cases. E.g. on the left side of the 
> bump, I need to go to the upper left, on the right side to the upper right. 
> There is no single shift that helps me. Nor a scale rotation or shift 
> combination. That could be managed by only going up (though the distance to 
> the path would vary, on the sides the text would be very close or on the top 
> it would be too far.)
> 

There is an example, at the link below, of creating a parallel path that claims 
to cope with sharp bends in the original path. You might be able to adapt it?


--
Bruce Horrocks
Hampshire, UK

___
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
___