[NTG-context] Different authorconversion for citation alternatives and bibliographic entries

I dealt with this issue at length in a separate thread (“Different author rendering in entry citation vs. list”) a couple months after you asked about this, so for the benefit of anyone who has been following this thread specifically, I’ll describe the solution I found here. There are (at least) a

Re: [NTG-context] getting path and filename from url

On 8/27/2021 8:53 PM, Pablo Rodriguez via ntg-context wrote: Dear list, I have the following sample: \starttext \startluacode url = "../a/b/cb/ce.b/ca.b/c/dabc.pdf" context(url) context("0 ok. " .. url:match "^(.*).pdf$") -- name and path context("1. " .. url:match

Re: [NTG-context] Different author rendering in entry citation vs. list

Happy I could help! The \btxflushauthornormal command should handle the authorconversion switch that you want. Just remember that if you need to use different et al. settings in citations as well, you should use \currentbtxciteauthorbyfield! Joey On Fri, Aug 27, 2021, 7:22 AM Ágoston Volcz via

Re: [NTG-context] getting path and filename from url

Hi Pablo, is the following what you need? context("1. " .. url:match ".+/") context("2a. " .. url:match "[^/]+/.+[.]") -- path and name with period --context("2b. " .. url:match "[^/]+[^.]+$") -- name with period and extension context("2c. " .. (url:match "[^/]+[^.]+$") :match

[NTG-context] getting path and filename from url

Dear list, I have the following sample: \starttext \startluacode url = "../a/b/cb/ce.b/ca.b/c/dabc.pdf" context(url) context("0 ok. " .. url:match "^(.*).pdf$") -- name and path context("1. " .. url:match "^(.*).+$") -- path context("2. " .. url:match"[^/]+[.$]") --

Re: [NTG-context] Test for displaying a header

Fabrice Couvreur schrieb am 27.08.2021 um 10:04: Hi Wolfgang, This may not be nicest but seems to work Fabrice %% \definelayout [1]   [header=10mm] \setuplayout   [header=0pt,  height=middle] \setuppagenumbering [alternative=doublesided,location=] \setupbackgrounds

Re: [NTG-context] problem with MkIV/TeXlive/TEXMFCACHE

On Fri, Aug 27, 2021 at 10:35 AM Rainer J.H. Brandt via ntg-context < ntg-context@ntg.nl> wrote: > Dear experts, > > I want to use ConTeXt MkIV as supplied by TeXlive 2021. > After installation, I ran "mtxrun --generate". > I also tried "context --generate". > Both create output in the wrong

Re: [NTG-context] Create an enumeration style

On Fri, Aug 27, 2021 at 11:26:47AM +0200, Vincent Hennebert via ntg-context wrote: > On Wed, 2021-08-11 at 10:23 +0200, Hans Hagen via ntg-context wrote: > > On 8/11/2021 10:09 AM, Otared Kavian via ntg-context wrote: > > > > > > > > > > On 9 Aug 2021, at 18:10, Wolfgang Schuster via

Re: [NTG-context] Different author rendering in entry citation vs. list

After I have seen your code snippet, the command \btxflushauthornormal grabbed my attention. This command and its variations are indeed what I was looking for. As I think the documentation doesn't mention these advanced commands, I didn't even know they exist. Thanks for sharing your discovery!

Re: [NTG-context] Create an enumeration style

On Wed, 2021-08-11 at 10:23 +0200, Hans Hagen via ntg-context wrote: > On 8/11/2021 10:09 AM, Otared Kavian via ntg-context wrote: > > > > > > > On 9 Aug 2021, at 18:10, Wolfgang Schuster via ntg-context > > cont...@ntg.nl> wrote: > > > (…) > > > core-con.lua (line 1155): > > > > > > local

[NTG-context] problem with MkIV/TeXlive/TEXMFCACHE

Dear experts, I want to use ConTeXt MkIV as supplied by TeXlive 2021. After installation, I ran "mtxrun --generate". I also tried "context --generate". Both create output in the wrong place. The TeXlive documentation says that ConTeXt uses TEXMFCACHE, which uses the default

Re: [NTG-context] layer disappears when showframe is set

Hi Wolfgang, thanks a lot for your help. Am Thu, Aug 26, 2021 at 05:52:11PM +0200 schrieb Wolfgang Schuster: > To keep the layer setting you have to move \showframe above your own > \setupbackgrounds command because the reset of the background-key happens > then before you pass your own value.