- ntg-context - NTG Mailing Lists

Scaling characters without font switching in CLD
by Hamid,Idris 13 Aug '23

13 Aug '23

Dear gang, I. In Context, as is well known, scaling a character is not independent of switching the font: ======= \startTEXpage[offset=1em] \definefont[Times][times @ 14pt] \Times Test \tfx Test \setupinterlinespace \Times Test \switchtobodyfont[x]Test \Times Test \high{Test} \stopTEXpage ======= \tfx causes a switch to computer modern. Of course, with the right typescripts and \setupbodyfont, one can maintain stylistic consistency when switching fonts. But what if we want to scale independently of font switching? II. One approach might be to use symbols: \startTEXpage \definesymbol[Tee][\getglyph{times}{T}] \symbol[Tee]est \tfx \symbol[Tee]est \tfa \symbol[Tee]est \stopTEXpage In this example, \tfa does scale the symbol Tee. But \tfx does not scale the symbol! Why does \tfa (or higher such as \tfb etc.) work, but not \tfx (or lower)? III. The best approach would be to do it in CLD (Context Lua Code). That is mostly beyond my skill to write from scratch without a template, but there are some experiments in the system file font-imp-effects.lua. There we will find, e.g., local specification = { name = "extend", description = "scale glyphs horizontally", initializers = { base = initializeextend, node = initializeextend, } } local specification = { name = "squeeze", description = "scale glyphs vertically", initializers = { base = initializesqueeze, node = initializesqueeze, } } This seems hopeful: \definecolor [transparentgreen] [g=1,t=.7,a=1] \definecolor [transparentred] [r=1,t=.7,a=1] \definecolor [transparentyellow] [y=1,t=.7,a=1] \startTEXpage[offset=1em] \definefontfeature[scale][default][extend=yes,squeeze=yes] \hbox{\rlap{\definedfont[times @ 14pt]\transparentgreen Test}% \definedfont[times*scale @ 14pt]\transparentred Test} \stopTEXpage But there is no scaling of the character, extend=yes shifts the glyphs to the left, and squeeze=yes appears to do nothing at all. Here is a file collecting these experiments: https://www.dropbox.com/scl/fi/dggj3ypgjjeia1bo4eelb/test-scaling.tex?rlkey… https://www.dropbox.com/scl/fi/o2u1tsq515ycyoeup43qg/test-scaling.pdf?rlkey… IV. Objective: I need to be able to define a couple of characters in CLD -- glottal stops --, and add commands to scale and/or rotate a character without triggering a font switch. Again, writing this from scratch is beyond my current skill set - although I've recently started to study CLD. Something like this -- some of the semantics is almost certainly wrong and/or clumsy -) ============== -- ʿ ringhalfleft local function ringhalfleft (characters,target,base,accent) -- if not characters[target] then local data1 = characters[base] local data2 = characters[accent] if data1 and data2 then characters[target] = { -- "ʿ" height = data1.height, depth = (data1.depth or 0) + 0.5*(data2.height or 0), width = data1.width, unicode = target, commands = { { "slot", 0, 0 }, { "left", -0.5*(data2.width or 0) + 0.5*(data2.width or 0)}, -- { "down", 0.2*(data2.height or 0) + (data2.height or 0) }, { "up", 0.0*(data2.height or 0) + (data2.height or 0) }, { "slot", 0, 0x063, }, { "squeeze", 0.75*(data2.height or 0) }, { "extend", 0.75*(data2.width or 0) }, }, } end -- end end -- ʾ ringhalfright local function ringhalfright (characters,target,base,accent) -- if not characters[target] then local data1 = characters[base] local data2 = characters[accent] if data1 and data2 then characters[target] = { -- "ʾ" height = data1.height, depth = (data1.depth or 0) + 0.5*(data2.height or 0), width = data1.width, unicode = target, commands = { { "slot", 0, 0 }, { "left", -0.35*(data2.width or 0) + 0.5*(data2.width or 0)}, { "down", 0.0*(data2.height or 0) + (data2.height or 0) }, -- { "up", 0.0*(data2.height or 0) + (data2.height or 0) }, { "slot", 0, 0x063, }, { "squeeze", 0.75*(data2.height or 0) }, { "extend", 0.75*(data2.width or 0) }, }, } end -- end end local function initialize(tfmdata,value) if value then -- Hdotbelow(tfmdata.characters,0x02BF,0x063,0) -- ringhalfleft (tfmdata.characters,0x02BF,0x063,0x063) ringhalfright(tfmdata.characters,0x02BE,0x063,0x063) -- (i.e., tfmdata.characters,target,base,accent) -- hdotbelow(tfmdata.characters,0x1E25,0x068,0x2D9) end end local function scale (ringhalfleft,ringhalfright) for v in next, ringhalfleft do v.height = 0.75 * (v.height or 0) v.width = 0.75 * (v.width or 0) v.depth = 0.75 * (v.depth or 0) end for v in next, ringhalfright do v.height = 0.75 * (v.height or 0) v.width = 0.75 * (v.width or 0) v.depth = 0.75 * (v.depth or 0) end end local specification = { name = "glottalstops", description = "glottalstops", manipulators = { base = initialize, node = initialize, } } ============== Rotation for one of the characters is also needed. Here is an experimental test file: https://www.dropbox.com/scl/fi/wi81e23wg17k8jasqpeon/transliteration-glotta… https://www.dropbox.com/scl/fi/rca5v6uusyj6mogyklfpd/transliteration-glotta… Thank you in advance for your guidance. Best wishes Idris -- Professor Idris Samawi Hamid Department of Philosophy Colorado State University Fort Collins, CO 80523

3 9

upload
by Hans Hagen 11 Aug '23

11 Aug '23

Hi, I uploaded a new lmtx. There are some new features that wil be revealed in the future (likely after the meeting) but here is one: \starttext \defineoverlay [test] [\color [blue] {TEST \inframed [foregroundcolor=red] {xxx} TEST}] \framed [background=test, foregroundstyle=\switchtobodyfont[small]] {test} \stoptext From now on many commands accept (properly) nested [] inside commands that use [] as fences (like the setup commands) where it makes sense. It is up to the user to decide to use {} (as before) or not but it is less error prone. It is now also possible to nest setups as in \starttext \startsetups one \startsetups [three] HERE \stopsetups \stopsetups \startsetups two \startsetups [three] THERE \stopsetups \stopsetups \setups[one] \setups[three] \setups[two] \setups[three] \stoptext As part of the ongoing improvements on math rendering we added some classic lm/cm kerns (between upperacse and periods / commas) in the goodie files. Some lowlevel manuals have been extended, explaining experimental 'named cross macro nesting parameter referencing' and 'constrained cq. retained assignments', but that is only relevant for those interested in overcoming some limitations in the traditional engines. 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 12

How to override parts of a typescript
by Vincent Hennebert 11 Aug '23

11 Aug '23

Say I want to use the Adobe Source font family in my document. They are installed on my system, but the file names are different to what’s in the typescript file provided with the ConTeXt distribution. If I do this: \starttypescript [serif] [source] [name] \definefontsynonym [Serif] [file:SourceSerif4-Regular] [features=default] \definefontsynonym [SerifItalic] [file:SourceSerif4-It] [features=default] \definefontsynonym [SerifBold] [file:SourceSerif4-Bold] [features=default] \definefontsynonym [SerifBoldItalic] [file:SourceSerif4-BoldIt] [features=default] \stoptypescript \setupbodyfont[source] \starttext I want this text to be typeset in Adobe Source Serif. \stoptext Then I get what I want. The question is: can I move the \start/stoptypescript code into its own typescript file that would somehow refer to the official one and override only what’s needed? Or is the only solution to just copy the whole file and tweak what I need? I found some thread in the mailing list archive relating to this but it’s more than 15 years old. Maybe things have changed since then. Thanks, Vincent

2 1

xml: matches always child of other element
by denis.maier＠unibe.ch 10 Aug '23

10 Aug '23

Hi, I must be missing something obvious, but in this example the pattern for <term> always matches the first element, not the one under the current <index-entry>. Interestingly, using xml:index-entry-2 instead of the normal version matches correctly... Any hints what is going off the rails here? Best, Denis \startxmlsetups xml:test \xmlsetsetup{#1}{*}{-} \xmlsetsetup{#1}{index}{xml:*} \xmlsetsetup{#1}{index-entry}{xml:index-entry} %\xmlsetsetup{#1}{index-entry}{xml:index-entry-2} \xmlsetsetup{#1}{term}{xml:index-entry-term} \xmlsetsetup{#1}{nav-pointer-group}{xml:*} \xmlsetsetup{#1}{nav-pointer}{xml:nav-pointer} \xmlsetsetup{#1}{nav-pointer/ext-link}{xml:nav-pointer-link} \stopxmlsetups \xmlregisterdocumentsetup{test}{xml:test} % Index \startxmlsetups xml:book-back \xmlflush{#1} \stopxmlsetups \startxmlsetups xml:index \startsectionlevel[title={\xmlfilter{#1}{/index-title-group/title/command(xml:index-title)}},] \xmlflush{#1} \stopsectionlevel \stopxmlsetups \startxmlsetups xml:index-title \xmlflush{#1} \stopxmlsetups \definedescription[indexentry] [alternative=top, headstyle=normal, headcommand=\hskip-1cm, margin=1cm, inbetween=, ] \startxmlsetups xml:index-entry \xmlflush{#1} \stopxmlsetups \startxmlsetups xml:index-entry-2 \xmlfilter{#1}{/term/command(xml:index-entry-term)}% \xmlverbatim{#1} \stopxmlsetups \startxmlsetups xml:index-entry-term \indexentry{\xmlflush{#1}} \stopxmlsetups \startxmlsetups xml:nav-pointer-group \xmlconcat{#1}{/nav-pointer}{, } \stopxmlsetups \startxmlsetups xml:nav-pointer \xmlflush{#1} \stopxmlsetups \startxmlsetups xml:nav-pointer-link \xmlflush{#1} \stopxmlsetups \startbuffer[test] <?xml version="1.0" encoding="UTF-8"?> <index> <index-title-group> <title>Index</title> </index-title-group> <index-entry> <term>First</term> <nav-pointer-group> <nav-pointer> <ext-link>1</ext-link> </nav-pointer> <nav-pointer> <ext-link>2</ext-link> </nav-pointer> <nav-pointer> <ext-link>3</ext-link> </nav-pointer> </nav-pointer-group> </index-entry> <index-entry> <term>Second</term> <nav-pointer-group> <nav-pointer> <ext-link>1</ext-link> </nav-pointer> </nav-pointer-group> </index-entry> <index-entry> <term>Third</term> <nav-pointer-group> <nav-pointer> <ext-link>1</ext-link> </nav-pointer> </nav-pointer-group> </index-entry> </index> \stopbuffer \starttext \xmlprocessbuffer{test}{test}{} \stoptext

2 3

Cron <context@cgl> /var/www/aanhet.net/context/bin/cron/context-mirror
by root＠ntg.nl 10 Aug '23

10 Aug '23

receiving incremental file list ./ ctan.lsr document-2.htm download-1.htm download-2.htm logo-ade.png logo-cts.png logo-pod.png rss.xml show-fil.pdf context/latest/ context/latest/cont-lmt.zip context/latest/cont-mpd.zip context/latest/cont-ppc.zip context/latest/cont-sci.zip context/latest/cont-tmf.zip context/latest/cont-tst.7z context/latest/cont-tst.tar.xz context/latest/cont-tst.zip sent 175,487 bytes received 38,024,206 bytes 3,321,712.43 bytes/sec total size is 562,337,758 speedup is 14.72 Running archiver: New dir: /var/www/aanhet.net/context//htdocs/archives/context-2023-08-10.17 233660520 /var/www/aanhet.net/context//htdocs/archives/context-2023-08-10.17/latest 126745317 /var/www/aanhet.net/context//htdocs/archives/context-2023-08-10.17/current 360409933 /var/www/aanhet.net/context//htdocs/archives/context-2023-08-10.17 360409933 total

1 0

Map XML attributes to variables, dynamically
by Thangalin 10 Aug '23

10 Aug '23

Hello! A Markdown document resembles the following: ::: {.concurrent title="Berth 5" location="San Diego"} Text Goes Here ::: ::: {.concurrent title="Road" location="Beale AFB"} Different Text Goes Here ::: The XHTML generated from that document resembles: <div class="concurrent" data-title="Berth 5" data-location="San Diego"> Text Goes Here </div> <div class="concurrent" data-title="Road" data-location="Beale AFB"> Different Text Goes Here </div> Environments for the DIV element gets translated using: \startxmlsetups xml:div \start[\xmlatt{#1}{class}]\xmlflush{#1}\stop \stopxmlsetups This creates "\startconcurrent" and "\stopconcurrent", which are later defined using "\definestartstop[concurrent]". I'd like to dynamically define all the data- attributes to make key/value pairs accessible from the document. For example, I have this: \definestartstop[concurrent][ before={% \blank[big]% \setMPtext{1}{Berth 5}% \startTextConcurrentFrame}, after={\stopTextConcurrentFrame\blank[big]}, ] I'd like to replace \setMPText calls with a reference to a dynamically created variable reference. For example: \setMPtext{1}{\usermap[concurrent.title]} \setMPtext{2}{\usermap[concurrent.location]} I can verify the attribute values exist by exporting them to the document: \startxmlsetups xml:div title:\xmlatt{#1}{data-title} location:\xmlatt{#1}{data-location} \start[\xmlatt{#1}{class}]\xmlflush{#1}\stop \stopxmlsetups How would you change the xml:div setup to create a map of its attributes as key/value pairs? Thank you!

3 5

Cron <context@cgl> /var/www/aanhet.net/context/bin/cron/context-mirror
by root＠ntg.nl 09 Aug '23

09 Aug '23

receiving incremental file list ./ ctan.lsr document-2.htm download-1.htm download-2.htm logo-ade.png logo-cts.png logo-pod.png rss.xml show-fil.pdf context/latest/ context/latest/cont-lmt.zip context/latest/cont-mpd.zip context/latest/cont-ppc.zip context/latest/cont-sci.zip context/latest/cont-tmf.zip context/latest/cont-tst.7z context/latest/cont-tst.tar.xz context/latest/cont-tst.zip general/manuals/ general/manuals/lowlevel-grouping.pdf general/manuals/lowlevel-macros.pdf sent 176,523 bytes received 40,431,915 bytes 3,248,675.04 bytes/sec total size is 562,360,213 speedup is 13.85 Running archiver: New dir: /var/www/aanhet.net/context//htdocs/archives/context-2023-08-09.18 233679568 /var/www/aanhet.net/context//htdocs/archives/context-2023-08-09.18/latest 126745317 /var/www/aanhet.net/context//htdocs/archives/context-2023-08-09.18/current 360428981 /var/www/aanhet.net/context//htdocs/archives/context-2023-08-09.18 360428981 total

1 0

Tracker for hyphens at the end of lines
by Keith McKay 09 Aug '23

09 Aug '23

Hi colleagues, Is there a tracker for highlighting hyphens at the end of lines similar the way underfull and overfull boxes can be displayed with a coloured bar at the end of the offending line? I have looked at the wiki page "Reviewing hyphenation" and it has a solution for mkii from 2009 which, I would think, won't be suitable for present day ConTeXt. I have tried searching for hyphens using Skim and Adobe Acrobate viewers but although they find hyphenation in line they don't recognise hyphens at the edge of lines. Any help would be appreciated. Keith McKay

3 4

Re: Triaging tikz error: Cannot parse this coordinate
by Hans Hagen 09 Aug '23

09 Aug '23

On 8/9/2023 1:00 PM, Xavier B. wrote: > Yes. The problem is syntactic: with > \startscope[shift={(\p)}] > > it works. that's one way to look at it, kind of like (10,20) shifted (((((10,100))))) which looks somewhat weird (does {((((\p))))} actually work?) one can wonder why the coordinate is not expanded without encapsulating () which should not that hard to do 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 -----------------------------------------------------------------

1 0

Triaging tikz error: Cannot parse this coordinate
by Xavier B. 09 Aug '23

09 Aug '23

After some time, I could write a minimal example with tikz with strange error: Cannot parse this coordinate. Can someone help me to find the bug? I attach the file and the log. Help very appreciate I run $ context --version mtx-context | ConTeXt Process Management 1.04 mtx-context | mtx-context | main context file: /usr/share/texmf-dist/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2023.03.10 12:15 mtx-context | main context file: /usr/share/texmf-dist/tex/context/base/mkxl/context.mkxl mtx-context | current version: 2023.03.10 12:15 via texlive (arch) Thanks, Xavier

4 6