[NTG-context] \setupheadertexts for chapters with different authors
I thought this should work, since \structurelistuservariable{author}
works fine to call the author name into the TOC, but the same does not
work for header texts it seems:
\setupheadertexts
[{\hfill\getmarking[\structurelistuservariable{author}]\hfill}][]
[{\hfill\documentvariable{metadata:title}\hfill}][]
But it doesn't. What am I doing wrong?
Julian
___
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] Tex capacity exceeded...
Thanks Hans, and Rik. Perhaps I need to take a much closer look at this file to see if I have created some grouping issues. The removal of the .tuc file is a very handy tip that I hadn't thought of, and I assume it is associated with the way Hans put it, namely, 'looks like you load the same file...' Julian ___ 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] TeX capacity exceeded.... but....
On 2022-03-17 18:14, jbf via ntg-context wrote: I'd like to understand what is happening in this particular instance: While playing with a suggestion to a recent request (re \currentlistentrynumber etc.) I suddenly got a compiling error: TeX capacity exceeded, sorry [file=2000]. I returned everything to how it was before I was trying out those suggestions, but still got the error, so I began the \stopdocument routine fairly early in the document... same problem still. Then I brought the \stopdocument well forward, immediately after the standard makeup pages and the document compiled. When I removed \stopdocument, the entire document compiled as it should. So the basic question is: what can be causing the error message? This has happened to me on two occasions with this document - it occurred once before I had even begun experimenting with the \currentlistentry options, so I do not think that the problem lies there. And when it occurred that time, I again solved it with \stopdocument routine, but further into the document. And similarly, once it compiled that far and I removed it, the whole document compiled once more. If it is too complicated an explanation for an email response, maybe just point me to a document that explains the issue. Julian I cannot explain what is happening, but I can tell you what I do when I come across an unexpected failure: I delete the .tuc file (and .tua file as well if present) and try again. This is an easy thing to do before halving the source (moving \stop) and such. -- Rik ___ 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] TeX capacity exceeded.... but....
On 3/17/2022 11:14 PM, jbf via ntg-context wrote: I'd like to understand what is happening in this particular instance: While playing with a suggestion to a recent request (re \currentlistentrynumber etc.) I suddenly got a compiling error: TeX capacity exceeded, sorry [file=2000]. I returned everything to how it was before I was trying out those suggestions, but still got the error, so I began the \stopdocument routine fairly early in the document... same problem still. Then I brought the \stopdocument well forward, immediately after the standard makeup pages and the document compiled. When I removed \stopdocument, the entire document compiled as it should. So the basic question is: what can be causing the error message? This has happened to me on two occasions with this document - it occurred once before I had even begun experimenting with the \currentlistentry options, so I do not think that the problem lies there. And when it occurred that time, I again solved it with \stopdocument routine, but further into the document. And similarly, once it compiled that far and I removed it, the whole document compiled once more. If it is too complicated an explanation for an email response, maybe just point me to a document that explains the issue. a guess ... it looks like you load the same file so you have some nesting / grouping problem; (some file loaders keep track of being loaded but you probably load before that is done) 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 - ___ 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] TeX capacity exceeded.... but....
I'd like to understand what is happening in this particular instance: While playing with a suggestion to a recent request (re \currentlistentrynumber etc.) I suddenly got a compiling error: TeX capacity exceeded, sorry [file=2000]. I returned everything to how it was before I was trying out those suggestions, but still got the error, so I began the \stopdocument routine fairly early in the document... same problem still. Then I brought the \stopdocument well forward, immediately after the standard makeup pages and the document compiled. When I removed \stopdocument, the entire document compiled as it should. So the basic question is: what can be causing the error message? This has happened to me on two occasions with this document - it occurred once before I had even begun experimenting with the \currentlistentry options, so I do not think that the problem lies there. And when it occurred that time, I again solved it with \stopdocument routine, but further into the document. And similarly, once it compiled that far and I removed it, the whole document compiled once more. If it is too complicated an explanation for an email response, maybe just point me to a document that explains the issue. Julian ___ 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] Calling in chapter number in list={}
But thanks anyway and also to Jean-Pierre (although I do understand sufficient German and could also have made headway in French if it came to that!). The \currentlistentry... options were what I needed. I was playing with wrong options (for this particular problem) like \currentheadnumber. Julian On 17/3/22 21:36, Henning Hraban Ramm via ntg-context wrote: Am 17.03.22 um 11:31 schrieb Jean-Pierre Delange via ntg-context: Which could be translated in English ! Yes, I was a bit lazy and Thunderbird also messed up the line breaking. HR ___ 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 ___ ___ 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] zint module on LMTX
On 3/16/22 22:32, Pablo Rodriguez via ntg-context wrote: > [...] > On Windows, I need to check the issue further. Using latest binary from SF (which is Win32, btw), I get the following error message: error (lmt library): unable to load 'D:/utilidades/context/tex/ texmf-win64/bin/lib/luametatex/zint/libzint.dll', quitting mtx-context | fatal error: return code: 1 So, latest version in Windows breaks compilation on my computer. What am I doing wrong? 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@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] Calling in chapter number in list={}
Am 17.03.22 um 11:31 schrieb Jean-Pierre Delange via ntg-context: Which could be translated in English ! Yes, I was a bit lazy and Thunderbird also messed up the line breaking. HR ___ 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] Calling in chapter number in list={}
Which could be translated in English !
\currentlistentrylocation = Consecutive number of the list entry
\namedstructureheadlocation{section} = Section number of the specified
hierarchy level (chapter, section, etc.) \currentlistentrynumber =
section number of the current list entry \currentlistentrytitle =
Heading of the current list entry \currentlistentrypagenumber = page
number of the current list entry
Le 17/03/2022 à 11:18, Henning Hraban Ramm via ntg-context a écrit :
\currentlistentrylocation
= Laufende Nummer des Listeneintrags \namedstructureheadlocation{section}
= Abschnittsnummer der angegebenen Hierarchiestufe (chapter, section
usw.)
\currentlistentrynumber
= Abschnittsnummer des aktuellen Listen eintrags
\currentlistentrytitle
= Überschrift des aktuellen Listeneintrags
\currentlistentrypagenumber
= Seitenzahl des aktuellen Listeneintrags
--
Jean-Pierre Delange
Ancients
Professeur Agrégé de Philosophie (HC)
___
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] Calling in chapter number in list={}
Hi Julian,
have fun with:
\currentlistentrylocation
= Laufende Nummer des Listeneintrags \namedstructureheadlocation{section}
= Abschnittsnummer der angegebenen Hierarchiestufe (chapter, section usw.)
\currentlistentrynumber
= Abschnittsnummer des aktuellen Listen eintrags
\currentlistentrytitle
= Überschrift des aktuellen Listeneintrags
\currentlistentrypagenumber
= Seitenzahl des aktuellen Listeneintrags
(in German, because I copied it from my book)
If you use \setuplist[command=...], you should set
alternative=interactive, otherwise you don’t get bookmarks and links.
\define[3]\MeinEintrag{#3: #2 (#1)} % Seite: Titel (Nummer)
\setuplist[alternative=interactive,command=\MeinEintrag]
or define your own alternative:
\definelistalternative[j][renderingsetup=list:jbf]
\startsetups[list:jbf]
... \currentlist...
\stopsetups
HTH
Hraban
Am 16.03.22 um 22:03 schrieb jbf via ntg-context:
I wonder if there is a way I can call in the chapter number in the TOC,
although that number is not used for chapters as such. I know the
chapter number is 'remembered' anyway, so there is probably a way I can
call it in just for the TOC.
The context for this question is the layout for book which comprises
individual contributions, and each contribution has its own
author/copyright (hence the individual chapters bear a title without a
number, but the editor who has compiled these wants them numbered in the
TOC).
I currently call the author name in the TOC with:
\define[1]\SectionTocEntry{%
\leftaligned{#1}\par% title. \leftaligned is needed
\hskip1cm\relax\doifnot{\structurelistuservariable{author}}{}{\structurelistuservariable{author}}%
}
\setuphead[chapter] of course includes number=no.
\setuplist[chapter] is currently set as:
[label=yes,distance=1.2cm,style=normal,before=\blank,after=\blank,textstyle=normal,alternative=c,textcommand=\SectionTocEntry,]
And for the moment I simply use, as part of the \startchapter[]
description: list={1. This is the rather long title of the first
chapter, with the number included at the beginning}.
While that gives me the number of the chapter, it does not give me
correct indentation when the chapter title runs to more than one line.
What I would prefer to do is to be able to call the chapter number
automatically with placing 1., 2., etc. in list={}.
Julian
___
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] Force a hyphenation
Thanks everybody very much for the explanations. — As I am Swiss, these matters with ß were never correctly understood and my knowledge about hyphenation is old… Thank you Thomas for pointing me to the Duden-rules. I will check-out the same issue about ck and k-k … Kind regards Willi > On 16 Mar 2022, at 17:29, Arthur Rosendahl via ntg-context > wrote: > > On Wed, Mar 16, 2022 at 05:17:46PM +0100, Thomas A. Schmitz via ntg-context > wrote: >> So Eiwei-ßes may in fact be correct... But I assume that Arthur has some >> authoritative answer to this question. > > I’ll refer to the German hyphenation pattern list as an authority > (https://lists.dante.de/mailman/listinfo/trennmuster) :-) But I do > believe that you, Thomas, are right and that Eiwei-ßes is correct (while > Ei-weißes is much better anyway). It is in fact logical: ‘ß’ in the new > spelling means that the preceding sound is long, hence it has to be > spelt that way always, not “analysed” as ‘ss’. If you were to hyphenate > Straße as Stras-se, it would indicate a different pronunciation. > > Best, > > Arthur > ___ > 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 > ___ ___ 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 ___
