Re: [NTG-context] TEST criticus apparatus with line numbering in footnotes

The numbering of lines works fine on MacOS High Sierra and on Linux x64: under linux x64 my CTX version is current version: 2020.01.30 and for MacOS : 2021.12.30. Now, I have to play in order to get a two columns of different texts with a critical apparatus in footnotes on the basis of

Re: [NTG-context] TEST criticus apparatus

Thank you Pablo : it works fine on MACOS either ! > Le 6 janv. 2022 à 17:56, Pablo Rodriguez via ntg-context > a écrit : > > ___ If your question is of interest to others as well, please add an entry to the

Re: [NTG-context] TEST criticus apparatus

On 1/6/22 2:09 PM, Jean-Pierre Delange via ntg-context wrote: > I’ve tested the attached file on MacOS (High Sierra) . See the > result in PDF : the numbering of notes appears as « ? ». Jean-Pierre, your code contains "\start\fr" with no matching "\stop". I wonder whether "\startlanguage[fr]

[NTG-context] TEST criticus apparatus

I’ve tested the attached file on MacOS (High Sierra) . See the result in PDF : the numbering of notes appears as « ? ». The same file works fineunder Linux. ConTeXt_Test_FooteNote-ComplexMedieval.pdf Description: Adobe PDF document ConTeXt_Test_FooteNote-ComplexMedieval.log Description:

Re: [NTG-context] Test suite fonts/features-005.tex failing for me

On 10/3/2021 1:41 AM, Bruce Horrocks via ntg-context wrote: In the test suite, the file fonts/features-005.tex is failing for me on latest lmtx. All three items appear the same each time i.e. no small caps and no old-style digits on the second and third.

[NTG-context] Test suite fonts/features-005.tex failing for me

In the test suite, the file fonts/features-005.tex is failing for me on latest lmtx. All three items appear the same each time i.e. no small caps and no old-style digits on the second and third. Can anyone else reproduce this, please? —

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

Fabrice, there is difference between putting something on the first page regardless of the number of pages in your document or do something when your document contains only a single or more pages. When you have a header or title which is always placed on the first page (but not on the

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] Test for displaying a header

Fabrice Couvreur via ntg-context schrieb am 26.08.2021 um 19:06: Hi, Using this (almost what I'm trying to do) without success [...] \startsetups[header] \doifelse{\totalnumberofpages}{1} {\setupheadertexts[\setups{header}]}     {} \stopsetups This stores the page check in the setups

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

Hi, Using this (but it's not exactly what I want) it works test-1.tex %% \setuppagenumbering [alternative=doublesided,location=] \definelayout [1] [header=10mm] \setuplayout [header=0pt, height=middle] \setupbackgrounds [header] [text]

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

Taco Hoekwater via ntg-context schrieb am 26.08.2021 um 16:34: Hi, On 26 Aug 2021, at 16:07, Fabrice Couvreur via ntg-context wrote: Hi, I know I asked the question a few years ago, but I don't remember ! The idea is to test whether the document contains only one page or not. Perhaps not

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

Hi, > On 26 Aug 2021, at 16:07, Fabrice Couvreur via ntg-context > wrote: > > Hi, > I know I asked the question a few years ago, but I don't remember ! > The idea is to test whether the document contains only one page or not. Perhaps not the nicest solution, but this works:

[NTG-context] Test for displaying a header

Hi, I know I asked the question a few years ago, but I don't remember ! The idea is to test whether the document contains only one page or not. If it contains only one page, the header is enabled. If it contains several pages, the header is enabled only on the first page but not on the others.

Re: [NTG-context] Test XML node registration

On 5/17/2019 10:28 AM, Hans van der Meer wrote: Having a series of nodes in setups in a helper module: \startxmlsetups xmlcommon:setups \xmlsetsetup{#1}{error|comment|... etcetera}{xmlcommon:*} \stopxmlsetups \xmlregistersetup{xmlcommon:setups} I would like to check if a certain node is in that

[NTG-context] Test XML node registration

Having a series of nodes in setups in a helper module: \startxmlsetups xmlcommon:setups \xmlsetsetup{#1}{error|comment|... etcetera}{xmlcommon:*} \stopxmlsetups \xmlregistersetup{xmlcommon:setups} I would like to check if a certain node is in that series of nodes. For example doing

Re: [NTG-context] test-suite wiki page

On 2019-02-01 17:57, Taco Hoekwater wrote: > Yes, foundry.supelec.fr is officially dead now (and that project with > it) >> 2. I did find the (a?) test suite on the PRAGMA site at >> as a 7zip file. Is that >> the correct location to point people

Re: [NTG-context] test-suite wiki page

Hi, > Op 1 feb. 2019 om 17:09 heeft Sanjoy Mahajan het volgende > geschreven: > > In another thread, Hans had pointed me to the examples of blocks in the > test suite. That leads to my following two questions before I revise > the associated wiki page: > > 1. The wiki page about the test

[NTG-context] test-suite wiki page

In another thread, Hans had pointed me to the examples of blocks in the test suite. That leads to my following two questions before I revise the associated wiki page: 1. The wiki page about the test suite contains dead links to

[NTG-context] TEST

Hello, sorry for this mail, this is a test for my new provider. Happy TeXing! Willi ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl /

Re: [NTG-context] test on front/body/backmatter

On 7/14/2017 10:42 AM, Meer, Hans van der wrote: Is there a test usable in a macro to determine if one is inside frontmatter, bodymatter, backmatter? \starttext \startfrontmatter \doifelsemode{*frontpart}{yes}{no} \doifelsemode{*backpart} {yes}{no} \stopfrontmatter \startbackmatter

[NTG-context] test on front/body/backmatter

Is there a test usable in a macro to determine if one is inside frontmatter, bodymatter, backmatter? Hans van der Meer ___ If your question is of interest to others as well, please add an entry to the Wiki!

Re: [NTG-context] Test Suite Fonts "extensions-001"

Thomas Fehige 29. April 2016 um 10:38 Below is a minimal not-working example extracted from "extensions-001.tex" in the fonts section of the test suite. From what I understand of the code, the second line should read "XPrXcXdXPrX" instead of "abracadabra". But it

[NTG-context] Test Suite Fonts "extensions-001"

Below is a minimal not-working example extracted from "extensions-001.tex" in the fonts section of the test suite. From what I understand of the code, the second line should read "XPrXcXdXPrX" instead of "abracadabra". But it doesn't, it is still "abracadabra". Compiling the original

[NTG-context] test for new page

Can someone indicate how one can easily test for a new page in a list environment (or, indeed, anywhere else)? In one implementation of a listing, repeated sequential items or elements of items are suppressed, but I would like to repeat them when they occur at the top of a new page. I imagine

Re: [NTG-context] test for new page

On 4/12/2015 10:42 AM, Alan BRASLAU wrote: Can someone indicate how one can easily test for a new page in a list environment (or, indeed, anywhere else)? In one implementation of a listing, repeated sequential items or elements of items are suppressed, but I would like to repeat them when they

[NTG-context] Test example for problem

The context docment below shows two anomalies. One is the occurrane of the unknown font latinmodernmath-regular, loading aborted and two is that the compilation process halts on the first 'D' in the word Dutch, and no item bullet is typeset. The line \setmainfont[ipaexm] seems to cause

[NTG-context] Test

Hi All, Sorry for the noise. For some reason I am have been recieving mail from this list. regards Keith. ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist :

Re: [NTG-context] [test suite] Bidi and line numbering

Hello there. https://github.com/melmothx/context-unofficial-test-suite/blob/master/src/mkiv/bidi/linenumbers-001.tex The line numbering positioning is messed up and overlaps the text, or is on the wrong side. With TL12 the output was good. Cheers -- Marco

Re: [NTG-context] [test suite] Column-related fails to compile

https://github.com/melmothx/context-unofficial-test-suite/blob/master/src/mkiv/columns/sets-001.tex fails to compile, but it's not a regression since TL, where it fails too. Cheers system tex error on line 20 in file sets-001.tex: Missing number, treated as zero ... 10 11

Re: [NTG-context] [test suite] two linenote related testfiles fail

FAILING: https://github.com/melmothx/context-unofficial-test-suite/blob/master/src/mkiv/critical/testlinenotes-007.tex and https://github.com/melmothx/context-unofficial-test-suite/blob/master/src/mkiv/critical/testlinenotes-008.tex Also, it appears that \linenote was not present in TL12, so

[NTG-context] [test suite] Bibtex-related test fails to compile.

I've imported most of the testfiles kindly provided by Hans. Now the test suite has grown to ~900 files. I'm running them in chunks and I'll keep reporting, even if I don't need the feature. If you prefer me to post to another list, please let me know.

[NTG-context] Test suite report

Hello there. Aditya added a couple of testfiles. Thanks a lot. I encourage anyone reporting bugs to send a minimal example to me too, via mail or via pull requests on github, so people running the tests can catch regressions. I modified the code, so a unique filename for each test is not

Re: [NTG-context] Test suite report

On 21-10-2012 15:24, Marco Pessotto wrote: Hello there. Aditya added a couple of testfiles. Thanks a lot. I encourage anyone reporting bugs to send a minimal example to me too, via mail or via pull requests on github, so people running the tests can catch regressions. there is s zip with

Re: [NTG-context] Test suite report

Hans Hagen pra...@wxs.nl writes: there is s zip with lots of test files, it might make sense to take some from them (not all make sense in a visual compare) There are more then 800 files in http://www.pragma-ade.com/context/latest/cont-tst.7z Any clue about which directory can be safely

Re: [NTG-context] Test suite report

Any clue about which directory can be safely dropped? Nevermind, I'm finding the way. -- Marco ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist :

Re: [NTG-context] test for (negative) number

On Mon, 20 Aug 2012 20:11:32 +0200, Sietse Brouwer sbbrou...@gmail.com wrote: Hi Peter, I recommend using the following handy little idiom: \ctxlua{commands.doifelse(-45 0)}{big}{small} % small It lets you do all sorts of things that are tricky in TeX: \ctxlua{ commands.doifelse(

Re: [NTG-context] test for (negative) number

Am 21.08.2012 um 08:32 schrieb Procházka Lukáš l...@pontex.cz: On Mon, 20 Aug 2012 20:11:32 +0200, Sietse Brouwer sbbrou...@gmail.com wrote: Hi Peter, I recommend using the following handy little idiom: \ctxlua{commands.doifelse(-45 0)}{big}{small} % small It lets you do all

Re: [NTG-context] test for (negative) number

Thanks for all the answers so far. The 'doifelse' should do the trick. I was hoping for a system macro, but if there is none, I have to program it myself. :-) Peter Am 21.08.2012 08:56, schrieb Wolfgang Schuster: Am 21.08.2012 um 08:32 schrieb Procházka Lukáš l...@pontex.cz: On Mon, 20

Re: [NTG-context] test for (negative) number

... I also found another solution reposter before: \ctxlua{commands.testcase(condition)} { If true...} {If false} Note that both blocks (if-true and if-false) are mandatory. Considering Wolfgang's last answer, it would be better to write: \ctxcommand{testcase(condition)}

Re: [NTG-context] test for (negative) number

On 21-8-2012 17:13, Procházka Lukáš wrote: I also found another solution reposter before: \ctxlua{commands.testcase(condition)} { If true...} {If false} yes, but testcase is an unfortunate name and sort of obsolete (so best use doifelse)

[NTG-context] test for (negative) number

Hi, I used '\doifnumberelse' to validate some macro parameters (angle). Sadly it does not work with negative numbers. Is there a similar macro, that also supports negative values? Example: \doifnumberelse {45}{yes}{no}% yes \doifnumberelse{-45}{yes}{no}% no Greetings, Peter

Re: [NTG-context] test for (negative) number

Hi Peter, I recommend using the following handy little idiom: \ctxlua{commands.doifelse(-45 0)}{big}{small} % small It lets you do all sorts of things that are tricky in TeX: \ctxlua{ commands.doifelse( string.len( -45 ) 5 ) }{long}{short} Cheers, Sietse

[NTG-context] Test for existence of a Ctx buffer by Lua

Hello, how to test by Lua whether a Ctx buffer exists? --- \startbuffer[A] Aaa aaa \stopbuffer \starttext \getbuffer[A] Test %\getbuffer[NonExisting] Vvv \stoptext --- To get something like 'context.buffers.A' - no-nil and 'context.buffers.NonExisting' - nil? Best regards, Lukas

Re: [NTG-context] Test for existence of a Ctx buffer by Lua

On 28-1-2011 3:13, Procházka Lukáš Ing. - Pontex s. r. o. wrote: Hello, how to test by Lua whether a Ctx buffer exists? \doifelsebuffer --- \startbuffer[A] Aaa aaa \stopbuffer \starttext \getbuffer[A] Test %\getbuffer[NonExisting] Vvv \stoptext --- To get something like

[NTG-context] TEST

Please ignore this message - it's just a test due to some problems delivering e-mails to this conference. Lukas ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist :

[NTG-context] test files for Xindy (was Re: [Context] Xindy)

Arthur == Arthur Reutenauer [EMAIL PROTECTED] writes: Hello Arthur! Arthur At for the original question, it certainly sounds like a good Arthur idea to me, but it needs investigation. Gour, can you make a Arthur small test file with usage instruction? I've found some old post from Xindy

[NTG-context] Test message, different mail server.

My isp doesn't like ntg.nl for some reason. -- John Culleton Resources for every author and publisher: http://wexfordpress.com/tex/shortlist.pdf http://wexfordpress.com/tex/packagers.pdf http://www.creativemindspress.com/newbiefaq.htm http://www.gropenassoc.com/TopLevelPages/reference%20desk.htm

[NTG-context] Test message---different mail server.

-- John Culleton Precision Typesetting Able Indexers and Typesetters http://wexfordpress.com ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl /

[NTG-context] Test whether variable has been set

Hi, How can test whether a variable has been set? I couldn't find any reference to this in the wiki? TIA, Elliot ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist :

Re: [NTG-context] Test whether variable has been set

Hi Elliot, Elliot Clifton schrieb: Hi, How can test whether a variable has been set? I couldn't find any reference to this in the wiki? What do you mean by set? I use \doifnothing{\getvariable{foo}{bar}} {foo:bar contains nothing.\par}% \doifsomething{\getvariable{foo}{bar}} {foo:bar

Re: [NTG-context] Test whether variable has been set

Hi Peter, Thanks for your reply. I think I may have misunderstood the variable section on the wiki. I been using \setvariable to both declare and assign variables from my component files. When I should have been declaring them in the environment file first, right?

Re: [NTG-context] Test whether variable has been set

On Sun, 27 May 2007, Elliot Clifton wrote: Hi Peter, Thanks for your reply. I think I may have misunderstood the variable section on the wiki. I been using \setvariable to both declare and assign variables from my component files. When I should have been declaring them in the environment

Re: [NTG-context] Test whether variable has been set

Aditya Mahajan wrote: On Sun, 27 May 2007, Elliot Clifton wrote: Hi Peter, Thanks for your reply. I think I may have misunderstood the variable section on the wiki. I been using \setvariable to both declare and assign variables from my component files. When I should have been declaring

Re: [NTG-context] Test whether variable has been set

Elliot Clifton schrieb: Hi Peter, Thanks for your reply. I think I may have misunderstood the variable section on the wiki. I been using \setvariable to both declare and assign variables from my component files. When I should have been declaring them in the environment file first, right?

[NTG-context] test

-- John Culleton Able Indexing and Typesetting Precision typesetting (tm) at reasonable cost. Satisfaction guaranteed. http://wexfordpress.com ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context

[NTG-context] Test message

test ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context

[NTG-context] test

All, please ignore this test. ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] test

On Feb 13, 2007, at 10:24 PM, David Arnold wrote: please ignore this test. Too late. I've already read it. Steve ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context

[NTG-context] Test

All, Sorry, this is just a test. ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context

[NTG-context] Test, Ignore

-- John Culleton Able Indexing and Typesetting Precision typesetting (tm) at reasonable cost. Satisfaction guaranteed. http://wexfordpress.com ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context

Re: [NTG-context] test suite in the garden

Henning Hraban Ramm wrote: Am 2005-07-25 um 22:04 schrieb Mojca Miklavec: It is perhaps a lot of work included, but extending the contextgarden.net in such a way that users could provide test cases which would be typeset with different ConTeXt versions and PNGs compared afterwards ... could