- ntg-context - NTG Mailing Lists

Double-sided documents with MetaFun's Field[Text][Text]
by śrīrāma 07 Feb '22

07 Feb '22

Dear list, I have a double-sided document in which I want to draw certain page backgrounds on the right (odd) and left (even) pages. Here is an example %%% SOF \setuppagenumbering[alternative=doublesided] \setuplayout [backspace=4cm, leftmargin=4cm, cutspace=2cm, rightmargin=2cm, leftmargindistance=0cm, rightmargindistance=0cm, header=2cm, footer=2cm, topspace=1cm, bottomspace=1cm, top=1cm, bottom=1cm, width=middle, height=fit] \startuseMPgraphic{page} StartPage; draw Area[Text][Text] shifted (InnerMarginWidth,BottomHeight+FooterHeight); draw Field[Text][Text] withcolor blue; StopPage; \stopuseMPgraphic \defineoverlay[page][\useMPgraphic{page}] \setupbackgrounds[page][background=page] \starttext \dorecurse{10}{\input knuth \page} \stoptext %%% EOF In the resulting PDF the Field[Text][Text] path is not positioned (/computed?) correctly, while the manually positioned Area[Text][Text] path is as expected. So, it seems that the margin widths and other distance are updated for each odd, even page but Field[Text][Text] is still wrong? The Field[Text][Text] path appears on every page as though it is on an odd (right) page. Have I missed something? Thanks, śrīrāma (Sreeram)

1 1

Odd Font Behavior in startstop Group
by Michael Urban 06 Feb '22

06 Feb '22

I am experiencing an odd behavior switching text styles in a defined startstop group ("blockquote"). I get different behavior depending on whether the switchtobodyfont in the startstop definition includes the dummy {\it } and {\bf } text. If they are not there, the italic and boldface switches in the second blockquote revert to the gyreschola body font of the main text; but this only happens if there is an earlier blockquote with no style changes. This is with: $ context --version mtx-context | ConTeXt Process Management 1.03 mtx-context | mtx-context | main context file: /usr/local/texlive/texmf-local/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2020.03.10 14:44 mtx-context | main context file: /usr/local/texlive/texmf-local/tex/context/base/mkiv/context.mkxl mtx-context | current version: 2020.03.10 14:44 Do I need a newer version of ConTeXt, or am I doing something wrong? Fonts in ConTeXt are always perilous, alas. For me, anyway. \definefallbackfamily[story][serif][notoserif][range={greekandcoptic,greekextended},force=yes] \definefontfamily[story][serif][TeX Gyre Schola] \definefontfamily[story][sans][modern] \definefontfamily[story][mono][modern] \definefontfamily[story][mm][TeX Gyre Pagella Math] \setupbodyfont[story,11pt] \definestartstop[blockquote] [ before={ \blank \startnarrower \setupwhitespace[2pt] \setupindenting[none] \switchtobodyfont[termes]{\it }{\bf }% This is so weird. Put a comment marker after [termes] for a different result }, after={ \stopnarrower \blank \indenting[next]}, ]% \starttext \chapter{Testing} \input ward \startblockquote \input knuth \stopblockquote \input zapf {\it This is what Italic letters look like.} {\bf And these are bold.} \startblockquote This is what it said, in {\it Italic} and {\bf bold} letters: \bgroup \it\noindent This is what Italic letters look like here. \egroup \bgroup \bf\noindent This is what Bold letters look like here. \egroup \stopblockquote \stoptext

3 3

XMP metadata schema yields invalid PDF/A
by Karl Pettersson 05 Feb '22

05 Feb '22

Hi PDF/A files generated using ConTeXt fail validation with veraPDF, and the reason seems to be that the dc:description metadata is defined with the wrong type in the embedded XMP extension schema. https://tex.stackexchange.com/questions/632380/generate-pdf-a-with-context https://github.com/veraPDF/veraPDF-library/issues/1224 I can reproduce the problem using TeX Live 2021 (MkIV 2021.03.05). The definition seems to be controlled by this code. https://source.contextgarden.net/tex/context/base/mkiv/lpdf-pua.xml?search=… Regards -- Karl Pettersson Uppsala, Sweden https://static-dust.klpn.se/

3 11

Transliteration
by Ivan Pešić 03 Feb '22

03 Feb '22

Hello! I've been working on a Serbian book and I had to transliterate it from cyrillic to latin. There's been some nice improvement in transliteration, and I would like to propose a small change. One of the peculiarities that current transliteration mechanisms (both internal one and the 3rd party module from Philipp Gesang) don't process is that Љ, Њ and Џ are transliterated to Lj, Nj and Dž in normal words that start the sentence, or in names that normally start with a capital letter, but in titles written in all capitals they should be transliterated to LJ, NJ and DŽ. So, the quick solution was to update the current mapping vector and add another one (that is attached) that maps cyrillic capitals to LJ, NJ and DŽ and set the correct 30 letters used in Serbian language. It requires a bit more manual work to set the correct mapping for all capitals text, but it works. I have also merged the Serbian hyphenation patterns, so there is no need to switch the language in order to have hyphenation in transliterated text. That was possible because cyrillic and latin scripts use different code points, and there are no conflicts in patterns. So I suggest merging the patterns for Serbian cyrillic and latin. There is another issue if one wants to use a dropcap and the rest of that first word, and several following words are to be typeset in small caps. If that first letter is Љ (or other two letters that transliterate as digraphs), then the second letter of the digraph is not typeset in small caps because it gets injected before the group that turns on small caps. For example: \placeinitial Љ{\sc уди нису знали} but this is quite a special case... Regards, Ivan

3 3

lmtx
by Hans Hagen 03 Feb '22

03 Feb '22

Hi, There haven't been updates and the reason is that we're in the middle of math and/or wrapping up on transliteration / indic (for which there is also a nice wiki page being made). Concerning math, we're progressing with some rather flexible spacing, penalty, linebreak extensions but don't want to risk that when not used it gives different results (probably not all can be completely compatible but that is a side effect of getting rid of some hard coded assumptions in the engine). One objective is to make input a bit easier and predictable, esp wrt the often needed correction spacing (\, and friends). Anyway, in addition to Mikaels request for input an while ago ... if there are 'tex math annoyances' that you think originate in the way tex expects input, and you'd like them to be taken into account, let us know. 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

sorting for particular sub entries to register
by jbf 01 Feb '22

01 Feb '22

Let me come back to the unresolved (for me) question of two situations in sub entries to a book index (register). Sub entries that have formatting or sub entries that are surrounded by quote marks (straight or curly, it makes no difference) do not appear in the correct alphabetical order. Two attempts on my part: text before \index[Plenary+periti]{Plenary Council+{\it periti} (experts)} text after. text before \index{animals+‘special kinds’} text after. Or alternatively, \index[animals+special]{animals+‘special kinds’} The setup for my register is a pretty standard one. The processor is not for the 'periti' case above but I use it for book titles. \setupregister[index][n=1,method={zc,pc,zm,pm,uc},style=WORD] \defineprocessor[special][style=italic] In the periti case it is the \it command that clearly interferes with correct alphabetic positioning in the sub entry list. Placing +periti in the key does not overcome that problem. In the ‘special kinds’ case it is the initial single quote mark (‘) that causes the problem. The item comes last in the sub entry list. And if i include a key [special], then it comes first in the sub entry list. Either way, it is out of the desired sorting order. I believe I have followed the helpful suggestions of various ones, but it is always possible that I have not fully understood those suggestions. The reality is that at the moment the issue remains unresolved for me. Any further wisdom out there to offer me? Julian

3 4

paragraph notes located in text
by Pablo Rodriguez 01 Feb '22

01 Feb '22

Dear list, with current latest (2022.01.21 20:13), I cannot get paragraph footnotes when located in text. Here you have the mandatory sample: \setuppapersize[A6] \showframe\showgrid %~ \setupnote[footnote][paragraph=yes] \setupnote[footnote][location=text, paragraph=yes] \setupnotation[footnote][alternative=serried, width=broad] \starttext \startlinenumbering[step=3] \dorecurse{25} {a\footnote{b} } \stoplinenumbering \placenotes[footnote] \stoptext I already asked this twice (https://mailman.ntg.nl/pipermail/ntg-context/2022/104770.html, https://mailman.ntg.nl/pipermail/ntg-context/2022/104929.html) Could anyone confirm that the is no way to get paragraph notes when location is text, or tell me what I’m missing? Many thanks for your help, Pablo

2 2

doublesided margin page number
by Youssef Cherem 31 Jan '22

31 Jan '22

I've managed to put double-sided page numbers -- but numbers are restarting after two, though. What's going on? ==== \setuppagenumbering[location=,alternative=doublesided] % https://tex.stackexchange.com/questions/128854/context-eliminate-topspace-a… \definelayer [pagenumber] [ width=\paperwidth, height=\paperheight, % preset=rightbottom, voffset=.3\paperheight ] %\setupbackgrounds[page][background=pagenumber, setups=setpagenumber] \setupbackgrounds[text] [rightmargin] [background=pagenumber, setups=setpagenumber] %isso aqui é o que funciona para doublesided (frente e verso) \startsetups setpagenumber % Set the page number to be (2em, \lineheight) from the bottom right corner % Note the `preset=rightbottom` above. % % The 2nd set of optional arguments are for the frame. For illustration I change % the color and font of the page number \setlayerframed [pagenumber] [ x=3em, y=2em, ] [ frame=on, foregroundcolor=red, foregroundstyle=bold, ] {\pagenumber} \stopsetups % Disable default page numbering \starttext Page 1 \page Page 2 \page Page 3 \page Page 4 \dorecurse{15}{\input knuth} \stoptext ===================== Thanks a lot for any help!

3 3

control cite - bibliographical references
by r.ermers＠hccnet.nl 30 Jan '22

30 Jan '22

Dear list, I am struggling with the color of bibliographical references. I found (Ulrike’s) hack to render the items in the bibliography the regular color (black): \appendtoks \iflocation \letinteractionparameter{color}\empty \fi \to \everybtxlistrendering. There the problem seems to relate to the use of \setupinteraction. Now, in my citations (\cite[Douma1979a]) the authornames are still colored. Douma, 1979a, 86 I examined the contextgarden site, read and tried the answers to previous questions, but could not find out how to do this. Is there a way to control the author names? Thank you in advance, Kind regards, Robert

2 1

Re: [NTG-context] registers, how to ignore quote marks
by jbf 30 Jan '22

30 Jan '22

No, I had already tried that. It places the subentry at the top of the list of subentries, not in its correct alphabetical order. Using the example below, I assume you meant (I am including text before and after): The \index[Plenary+periti]{Plenary Council+{\it periti} (experts)} group comprises 10 members. There are nine subentries altogether, and quite a number under 'p', like \index{Plenary Council+preparations for}. The italicised /periti /should come just before the latter (preparations for) but, using the double key above it comes first in the list. The same happens with the subentry surrounded by single quotes. It too comes first in the list if I use a double key. So clearly it is the fact that there is formatting ({\it something}) or quotes ({‘word’}) in a subentry that causes the problem, and I am wondering how to overcome this. Julian On 30/1/22 20:59, Hans Hagen wrote: >> 2. \index{Plenary Council+{\it periti} (experts)}: in this case it is >> the italicised /periti/ that appears out of place, after the letter >> 'i' rather than after 'p'. Again I tried putting various keys but >> this did not help. >> >> I guess my confusion is this: I assumed that the [key] establishes >> the literal string which determines sort order. That seems to be the >> case for a main entry. How do I get it to work for a subentry? > just provide an extra key:

1 0