- ntg-context - NTG Mailing Lists

names of cached images
by Jano Kula 02 Jul '21

02 Jul '21

Hello list, using conversion=gray.pdf in lmtx the cached images' names have some string in their name. I thought it's a name of random sequence of luatex cache, but the string is the same on other machines and I don't know, where it comes from. mkiv used to have m_k_i_v_ string there. hacker.pdf = source image hacker_jpg_c60ccda70ef92e32d7a6334f31c23259.gray.pdf = cached linux hacker_jpg_c60ccda70ef92e32d7a6334f31c23259.gray.pdf = cached win MWE \starttext \externalfigure[hacker] [cache=./, conversion=gray.pdf] \stoptext Is it intended behavior? Thanks, Jano

3 5

Rolling out a pandoc-context publication workflow in an organization
by Jan U. Hasecke 02 Jul '21

02 Jul '21

Dear all, in the last weeks I asked more questions than I normally do. The reason is that my organization is discussing to roll out a markdown-pandoc-context publication workflow. Some time ago we started to use context to produce flyers and some other documents. In fact I was the only one to use it. The results are so good that we discussed how to use it more often. Currently we use LaTeX to produce our legal documents, terms of services etc. With ConTeXt we are able to meet our corporate design guidelines and to produce good looking and individually designed documents. But our authors and editors were not willing to use ConTeXt directly so that we decided to look into Pandoc and use Markdown as authors input markup. Markdown is much better supported by text editors than ConTeXt. The main problem for me is to come up with a good organization of the ConTeXt workflow so that it is easy usable and meets our requirements for quality management. These are quite strict. We are a Debian based cooperative and the majority of our editors also use this distribution on their private computers. Some use a MacBook, only one uses of Windows. For this reason we would like to stay with the Debian ConTeXt, which I never used as it is quite old. The same is true for Pandoc which made some improvements in the last years and also is very old in the current Debian distribution. As we did not decide this issue I can't say how much I have to refactor our styles to meet the older versions of ConTeXt. Apart from this I have to organize our style files and ressources, anyway. In another thread Hans said how to use these folders. Thanks a lot. texmf-local : maybe configurations texmf-project : stuff you're working on (styles) texmf-fonts : fonts you downloaded or bought All our styles and our shared image folder are versioned by git so I think that I either put links into texmf-project pointing to our style repository and to our image repository to have easy access to these ressources no matter how we call context or to put them into texmf-project directly. (We did not decide yet whether we call context from pandoc using a tmp directory for building or directly from our build script. If we use the current lmtx distribution, all editors would have to install ConTeXt with the install.sh script on their private computers, then we would either call a post installation script to clone the repositories in texmf-project or to clone them in another folder and set links to texmf-project. Linking seems better as I am not sure what "context generate" would do with the .git folder inside the repositories. All document projects are in their own repository. Currently we use a build script to call pandoc with an individual set of arguments including a custom context template which is stored in the document repository, also. Inside of this template we include all the environments we need for this particular document. We have a lot of small environments to reuse them in different document types. This is our plan so far. But to role out this successfully I would like to ease the way to a working pandoc-context installation for our editors. Do you have an idea how to do this? I come up with the idea of an "organizational context distribution" that has all requirements preinstalled. That could look like this: We have a repository: hs.lmtx which contains the install script and all our ressources (images and styles). Our editors would clone the repository and just call the installation script to download the lmtx distribution. Afterwards they are ready to start as we would point to the right context executable in our build scripts. Problem: What will happen if our editors do a git pull in hs.lmtx and a "context generate"? There are also concerns if something breaks after updating context with the install.sh. Is there a way to reset the installation to a given point release? How do you solve this in a production environment? On my private computer I sometimes install a new version of lmtx in a "staging" folder try it out and redo updating in my "production" folder. I think I will try this out but I am happy if you have any comments on this. TIA juh

6 11

columnsets messed up
by Henning Hraban Ramm 02 Jul '21

02 Jul '21

Hi, I’m working at the current CG journal whose layout uses columnsets. They aren’t usable any more. Same in current LMTX and MkIV. - the first line can start one or more lines lower - then the same number of lines is printed over each other at the bottom - it gets worse with footnotes (looks like their space isn’t considered at all) - if the column set doesn’t start at the top of the page, the second column does Hraban \definecolumnset[cgjcolset][n=2] \starttext \chapter{This is a chapter about column sets} \startcolumnset[cgjcolset] \dorecurse{20}{ \samplefile{sapolsky}\par } \stopcolumnset \stoptext

2 3

Hyphens broken with lucidaot
by Otared Kavian 02 Jul '21

02 Jul '21

Hi Hans, I noticed that with the recent LMTX version 2021.06.27 16:59 the hyphens do not show up correctly with lucidaot. Here is a minimal example and the resulting PDF \setupbodyfont[lucidaot,10pt] \startTEXpage c'est-à-dire sous-ensemble sous-préfet \stopTEXpage Best regards: Otared

3 2

Different authorconversion for citation alternatives and bibliographic entries
by Ágoston Volcz 02 Jul '21

02 Jul '21

Hi there, My university has special requirements for the theses I submit. Layout, fonts etc. are pretty straightforward to set up in ConTeXt. The one part I'm struggling with is citations / bibliography. I have to use the german citation style with footnotes. Essentially the first time I cite something, I have to put the full entry in a footnote. From the second time on, I only have to put a shorter entry in the footnotes. I have two problems: 1. I created the publ-imp-deu.lua and publ-imp-deu.mkvi files. If I put them into the ~/bin/context/tex/texmf-context/tex/context/base/mkiv/ directory, I get the following two lines in the log: ``` publications > unknown library 'deu' publications > no data definition file 'publ-imp-deu.lua' for 'deu' ``` If I put them into the directory where my thesis is, they seem to get recognized, but I would very much like to reuse them and not have to copy them to each project directory. What am I doing wrong? 2. Entries in the bibliography and fist time citations must have 'normal' authorconversion, while consequent citations must have 'normalshort'. For consequent citations I defined the 'authortitle' alternative. In the thesis I have: ``` \usebtxdataset[default][literature.bib] \usebtxdefinitions[deu] \setupbtx[deu] ``` A snippet from the publ-imp-deu.mkvi: ``` \definebtx [deu:list] [deu] [authorconversion=normal] \definebtx [deu:cite] [deu] [authorconversion=normalshort, alternative=authortitle] \startsetups btx:deu:list:book {\sc \btxflush{author}}\btxcolon \btxflush{title} \btxdoif{subtitle}{\btxperiod\btxflush{subtitle}}\btxperiod \btxflush{address}\btxcolon \btxflush{publisher} \btxflush{year} \btxdoif{series}{ (\btxflush{series} \btxflush{volume})}\btxperiod \stopsetups ``` In the setup and definition, the fields I defined do get into the citation correctly, but the authorconversion remains 'normal'. If I comment out the lines which set up 'normal' authorconversion for the list, everything, including the bibliography and 'entry' type citations get 'normalshort'. Is that a bug or am I missing something? Thank you, Agoston

7 14

Heading for endnotes / grouped by chapter endnotes
by denis.maier＠unibe.ch 02 Jul '21

02 Jul '21

Hi, I have two questions regarding endnotes: 1. Is there a way to add a heading automatically to the endnotes placed with \placenotes[endnote]? 2. I reset the endnote number at each part. Is there a way to insert the title of the corresponding part heading to the endnotes? I have searched the wiki and the mailing list, and I've found two relevant questions, but no answers. https://www.mail-archive.com/ntg-context@ntg.nl/msg68490.html https://www.mail-archive.com/ntg-context@ntg.nl/msg34163.html Best, Denis =================================== \setuphead[part][placehead=yes] \setupnotation [endnote] [way=bypart] \starttext \part{First Part} asdf\endnote{asdf} jklö\endnote{jklö} \part{Second Part} asdf\endnote{asdf} jklö\endnote{jklö} \placenotes[endnote] \stoptext =============================

3 11

using variable font
by Herbert Voss 01 Jul '21

01 Jul '21

Hello all, this worked years ago with another variable font. But it fails with FiraCode. I get always the same weight: \definefontfeature[w300][default][axis={weight:300}] \definefontfeature[w400][default][axis={weight:400}] \definefontfeature[w500][default][axis={weight:500}] \definefontfeature[w600][default][axis={weight:600}] \definefontfeature[w700][default][axis={weight:700}] \definefont [FiraCode@300] [file:FiraCode-VariableFont_wght.ttf*w300] \definefont [FiraCode@400] [file:FiraCode-VariableFont_wght.ttf*w400] \definefont [FiraCode@500] [file:FiraCode-VariableFont_wght.ttf*w500] \definefont [FiraCode@600] [file:FiraCode-VariableFont_wght.ttf*w600] \definefont [FiraCode@700] [file:FiraCode-VariableFont_wght.ttf*w700] \starttext \csname FiraCode@300\endcsname FiraCode, weight=300\par \csname FiraCode@400\endcsname FiraCode, weight=400\par \csname FiraCode@500\endcsname FiraCode, weight=500\par \csname FiraCode@600\endcsname FiraCode, weight=600\par \csname FiraCode@700\endcsname FiraCode, weight=700\par \stoptext the font is availabel at Google: https://fonts.google.com/specimen/Fira+Code It also fails with another variable font. up-to-date lmtx on macOS. thanks Herbert

2 1

Re: [NTG-context] Different authorconversion for citation alternatives and bibliographic entries
by Gavin 01 Jul '21

01 Jul '21

Hi Alan, Hans, and Chicago style bibliography users, > 3) I believe that Gavin (on CC:) is a user of the Chicago author-year > model. I’d like to use the Notes and Bibliography style in my physics book, with endnotes after each chapter. I would gladly participate by testing and providing feedback. I am using a patched-together \footnote solution right now, and it is not great. The existing "biblatex-chicago” package might be helpful for development, especially in selecting database syntax and perhaps in designing algorithms. The author, David Fussner, has been maintaining and updating since the first public release in 2008. It the extensive documentation, he invites contact. It looks like a complicated project! I’d be happy to discuss this more at our next Norther Colorado ConTeXt User meeting. Would some time next week work? (Alan, who I met on this mailing list, lives a short bike ride from my house.) Gavin

1 0

hyphenate nothyphenated
by Steffen Wolfrum 01 Jul '21

01 Jul '21

When running this mwe with luatex, the command \- could be used to manually break the line, even though it is set up nothyphenated. When running luametatex the word does not break: \setuppapersize[A10] \showframe \setuphead[chapter][align={nothyphenated}] \starttext \chapter{abc\-def} \stoptext Is this intended? Steffen

5 10

Loading a file at the line ConTeXt throws as an errror automatically with vim
by Marcus Vinicius Mesquita 01 Jul '21

01 Jul '21

Dear list, Is there a way to do this when running context from the command line in linux? TIA Marcus Vinicius -- Todas as coisas fatigam o corpo, salvo a música, que não fatiga nem o corpo nem seus membros, por ser descanso da alma, primavera do coração, distração do aflito, entretenimento do solitário, e viático do viajante. Kunnâsh al-Hâ'ik (Cancioneiro de al-Hâ'ik)

1 0