May 2022 - ntg-context - NTG Mailing Lists

conditionals for font features
by Pablo Rodriguez 13 May '22

13 May '22

Dear list, I wonder whether there is a conditional for font features similar to \doifelseitalic. \doifelsecurrentfonthasfeature checks whether the font supports an OpenType feature. \doifunknownfontfeature checks whether the font feature has been defined. It seems that \doifelsefontfeature checks whether the font feature has been defined or not. Could anyone explain me how to check whether c2sc is being used or not in the following sample? \definefontfeature[asc][c2sc=yes, smcp=yes] \setupbodyfont[palatino] \starttext \feature[+][asc] abc\\ \feature[-][asc] abc \stoptext Many thanks for your help, Pablo

1 0

blockligatures removing characters
by Ben Moon 13 May '22

13 May '22

Hi List, I'm using blockligatures to avoid the 'Th' ligature in some fonts but keep others. Recently I've found this removes the 'h' completely, i.e. 'Th' is changed to 'T', 'The' becomes 'Te' etc. Is there a way to restore the blockligatures functionality? I'm on ConTeXt version 2022.05.02 16:19. Here is a MWE using Almendra (https://fonts.google.com/specimen/Almendra <https://fonts.google.com/specimen/Almendra?preview.text=Th%20Almost%20befor…>) from Google Fonts. ``` \starttypescriptcollection[myfont] \starttypescript[myfont] \definefontsynonym[Serif][Almendra-Regular][features=default] \stoptypescript \starttypescript[myfont] \definetypeface[\typescriptone][rm][serif][myfont][default][] \stoptypescript \stoptypescriptcollection \blockligatures[Th] \definefontfeature[default][default][liga=yes] \definefontfeature[default:nolig][default][liga=no] \definefontfeature[default:blocklig][default][liga=yes,blockligatures=yes] \setupbodyfont[myfont] \starttext The This These have the Th ligature and others (fi) \definedfont[Serif*default:nolig] The This These have no ligatures (not fi) \definedfont[Serif*default:blocklig] The This These are missing the `h' (fi) \stoptext ``` Best, Ben

3 6

Re: [NTG-context] OpenBSD install
by Angel M Alganza 13 May '22

13 May '22

Hi again, On Fri, May 13, 2022 at 09:39:06AM +0200, Mojca Miklavec wrote: >Are you able to (log in and) edit wiki pages yourself? >I can of course edit this now, but this can be community effort. I >will surely forget to update the page in 6 months when the next >OpenBSD version gets released. I could create an account to do that. I suppose there is no problem in doing so, and, of course, I'd gladly update the links for the next release in 6 months (I see you have already done that for the 32bits also, thank you!). I think a good solution instead of linking to all individual files, could be to link to the official download page once: http://www.pragma-ade.com/install.htm >So you plan to keep using the 32-bit binaries for OpenBSD? I am, yes. I am migrating almost all 32bit boxes both at work and at home to Haiku and OpenBSD, since Linux is getting more and more resource demanding day by day (even Devuan, which can be configured to be very lightweight). I would really appreciate if you kept providing them. Cheers, Ángel

1 0

OpenBSD install
by Angel M Alganza 13 May '22

13 May '22

Hello, I've just started upgrading some systems to OpenBSD 7.1 (released last month) and found out there isn't a link to download LMTX for OpenBSD 7.1 at https://wiki.contextgarden.net/Installation. I then thought I'd try to see if the previous versions (for 6.9 or 6.8) would work on 7.1, but it turned out that all four links (for both 32bits and 64bits) won't work. FreeBSD and Linux links work fine, Any help for me to get the installation scripts for OpenBSD 7.1, please? Thank you in advance. Cheers, Ángel

2 2

Reference prefix for sections is ignored
by Wolfgang Schuster 12 May '22

12 May '22

Hi, the automatic reference prefix for section etc. with the setup \setuphead[chapter][referenceprefix=+] doesn't work anymore (broken since a while). The following patch for strc-sec.mkxl fixes the missing prefix: %%%% begin fix \def\strc_sectioning_set_reference_prefix {\ifempty\currentstructurereferenceprefix % nothing \orelse\ifx\currentstructurereferenceprefix\m_strc_references_prefix_yes - \global\advance\prefixcounter \plusone % temp here - \setupglobalreferenceprefix[\the\prefixcounter]% + \ifempty\currentstructurereference + \global\advance\prefixcounter \plusone % temp here + \setupglobalreferenceprefix[\the\prefixcounter]% + \else + \setupglobalreferenceprefix[\currentstructurereference]% + \fi \orelse\ifx\currentstructurereferenceprefix\m_strc_references_prefix_nop \setupglobalreferenceprefix[]% \else \setupglobalreferenceprefix[\currentstructurereferenceprefix]% \fi \glet\currentstructurereferenceprefix\referenceprefix} %%%% end fix When I apply the changes above the following document shows the correct references in the output. %%%% begin example \setuphead[chapter][referenceprefix=+] \starttext \chapter[one]{First chapter} \section[alpha]{First section} See \in{Section}[alpha]. See \in{Section}[two:beta]. \chapter[two]{Second chapter} \section[beta]{Second section} See \in{Section}[one:alpha]. See \in{Section}[beta]. \stoptext %%%% end example Wolfgang

1 0

check whether font feature is being used
by Pablo Rodriguez 12 May '22

12 May '22

Dear list, I have the following sample: \setupbodyfont[pagella] \definefontfeature[asc] [c2sc=yes, smcp=yes] \starttext \startTEXpage[offset=1em] text \doifelsecurrentfonthasfeature{asc} {yes}{no} \doifelsefontfeature{asc} {yes}{no} \doifunknownfontfeature{asc} {yes}{no}\\ \feature[+][asc] text \doifelsecurrentfonthasfeature{asc} {yes}{no} \doifelsefontfeature{asc} {yes}{no} \doifunknownfontfeature{asc} {yes}{no} \stopTEXpage \stoptext Sorry, but which is the right way to check when the font feature is being deployed? Many thanks for your help, Pablo

1 0

\startXML vs \startPARSEDXML
by denis.maier＠unibe.ch 12 May '22

12 May '22

Hi everyone, the wikipage on \starttyping (https://wiki.contextgarden.net/Command/_starttyping) says there are some dedicated commands, e.g. \startXML and \startPARSEDXML. How do they differ? Best, Denis

2 2

Re: [NTG-context] \xmlpos and \xmldepth misbehave? (again)
by denis.maier＠unibe.ch 12 May '22

12 May '22

Hi, I get the same behaviour with a slightly older version. I don't really understand what's happening, but I agree it's not what I'd have expected. Best, Denis > > -----Ursprüngliche Nachricht----- > > Von: ntg-context <ntg-context-bounces(a)ntg.nl> Im Auftrag von Pablo > > Rodriguez via ntg-context > > Gesendet: Freitag, 6. Mai 2022 18:21 > > An: Hans Hagen via ntg-context <ntg-context(a)ntg.nl> > > Cc: Pablo Rodriguez <oinos(a)gmx.es> > > Betreff: [NTG-context] \xmlpos and \xmldepth misbehave? (again) > > > > Dear list, > > > > I have the folloing sample: > > > > \startbuffer[text] > > <doc>first level > > <s>second level > > <ss>third level</ss> > > <ss>third level</ss> > > </s> > > <s>second level > > <ss>third level</ss> > > <ss>third level</ss> > > </s> > > <s>second level > > <ss>third level</ss> > > <ss>third level</ss> > > </s> > > </doc> > > \stopbuffer > > > > \startxmlsetups xml:text > > \xmlsetsetup{#1}{doc|s|ss}{xml:*} > > \stopxmlsetups > > > > \xmlregistersetup{xml:text} > > > > \startxmlsetups xml:doc > > \chapter{\xmlpos{#1}\letterat\xmldepth{#1}: \xmlflush{#1}} > > \stopxmlsetups > > > > \startxmlsetups xml:s > > \section{\xmlpos{#1}\letterat\xmldepth{#1}: \xmlflush{#1}} > > \stopxmlsetups > > > > \startxmlsetups xml:ss > > \subsection{\xmlpos{#1}\letterat\xmldepth{#1}: \xmlflush{#1}} > > \stopxmlsetups > > > > \setuphead[chapter,section,subsection][before=,after=,] > > > > \setuppapersize[A7] > > \setuplayout[width=middle, header=0cm] > > > > \starttext > > \xmlprocessbuffer{main}{text}{} > > \stoptext > > > > All \xmldepth values are +1 that I think they should be (starting from > > 2 [instead of 1] up to 4 [instead of 3]). > > > > \xmlpos values seem to count 2, 4, 6… (instead of 1, 2, 3…). > > > > This is with current latest from 2022.05.02 16:19. > > > > Sorry, but could anyone confirm whether I’m missing something or > > whether this issue is a bug? > > > > 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(a)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 > > > ______________________________________________________________ > > _____________________

1 0

Custom type-imp file creating empty lines
by Alexandre Christe 12 May '22

12 May '22

Dear list, I've played a bit with a custom type-imp file (partly inspired from the wiki https://wiki.contextgarden.net/Alegreya_Typescript) However, the file I ended up with seems to create some empty lines at the beginning of the document (if I use the default or another font this vanishes, so it really comes from that file). Could anyone enlighten me? The file is attached. BR, Alex

2 2

upload
by Hans Hagen 11 May '22

11 May '22

Hi, I uploaded a new version of lmtx (also because some users have to test some new metapost functionality). In the next upload metafun will use 'double' mode (and scaledfun will be the traditional one). The advantage is less dager for overflows and in the meantime running in double mode is often also faster. 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 -----------------------------------------------------------------

6 9