Re: [NTG-context] BibTeX inproceedings entries not rendered correctly in APA style
On 5/28/2021 16:33, Alan Braslau wrote: On Fri, 28 May 2021 19:52:19 - (UTC) Nicola wrote: If there is no publisher, then @unpublished is a better category. APA explicitly, and for good reason, accounts for self-publishing, indicating that the Author was the publisher. Ah ok, that explains the output I was obtaining. So, I am using the wrong bibliographic style for my purposes. In practice, at least in Computer Science, publishers (and also editors) are often omitted in references (it's more a "don't care", rather than a "don't know" thing, though). If a publisher does not exist, was it published? If the publisher is unknown, then why not state that: publisher="unknown publisher", or whatever? Strictly speaking, your reasoning makes perfect sense, and I am all for enforcing constraints if a given bibliographic style requires them. But then, there might be alternatives for when one does not need to adhere to those styles. Does ConTeXt (LMTX) currently provide anything else besides apa and aps? I have read the BibTeX manual looong time ago, but I remember that there were mandatory and optional fields for each reference type. My memory may fail me, but I think that Editor and Publisher were not mandatory fields for inproceedings and article (I think Publisher is mandatory for book). Is there a bibliographic style in ConTeXt that follows those rules? Bibliography management is very sophisticated in ConTeXt (much more than LaTeX) and I have not grasped all of its details yet. It seems to me that it has also evolved quite a bit in recent years. So, the "ConTeXt way" of doing bibliographies still eludes me to some extent. In writing the ConTeXt bibliography system, we tried to base this on references, indeed following the original bibtex manual for its definitions. The APA style follows the APA style guide as best as possible. The APS style is intended as a simple example of a numbered bibliography minimalist style. Multiple other styles exist out there, more or less well defined. The problem is that most of them are not very rigorous, and they are greatly abused. Many publishers follow their own (quirky) bibliography styles. The Context system started out as sort of a database handling subsystem, useful in publishing. It is entirely tune-able, through setups and parameters. However, the system is complex, so the customization is not quite as easy as originally intended. Note that the original bibtex system was conceived in order to have this configurability, however few were those who mastered writing bibliography styles, and even carefully crafted styles, for example as implemented by the APS RevTeX, were buggy and had a number of known, serious limitations requiring manual intervention. We could, and have had the intention of, writing other bibliography styles. But there must be a motivation as well as a clearly defined specification, for otherwise we will be heading down a rabbit hole of differing expectations and endless tweaking. As to "don't care" concerning publishers, this is not very academic. Indeed, many famous books have been published by various publishers, in particular for different markets. It is important to say, for each one might be slightly different, have different pagination for example, and even certain edits of the text. One might also not pay attention to the edition, but this too can lead to major differences (even, and especially in computer science). Thomas Schmitz, one of the originators of the bibliography project, will tell you to take the APA style as a model, and then modify it as you wish to your own needs. I further took this to heart, trying to write the macros as somewhat standard definitions that one could modify as needed without breaking the entire system. And then there are clearly bugs that can be fixed. In the case of a missing publisher, it is not simply left blank because the APA style explicitly tells us to put "Author" when there is no defined publisher, so this is a feature, not a bug. Alan The APA does not attempt to define bibliographies. It defines reference lists (and more specifically, reference lists for APA journal articles), and there is a difference. The reference list, as defined in the APA guide, simply exists to point the reader to the cited document (whatever 'document' might mean). Bibliographies, as the APA guide acknowledges, can be much richer, although they do not say it that way. Looking at the 6th edition of the APA guide (I have not reviewed the 7th edition guide, but as far as I know ConTeXt used the 6th edition), I note that example 36, a symposium contribution, does not have a publisher name. However, it does appear that ConTeXt would require a publisher for this and the following examples which have a DOI but no publisher. This may be an error, but whether on the part of the APA or ConTeXt or both I cannot say. For books, the APA guide does not require a publisher if a URL is provided, and
[NTG-context] Fwd: --luatex option failing
Pablo, thanks for the assistance you gave me... it made me look at the cache inside the lmtx folders and I could see that the entire luatex folder was missing. I did try your --erase and --generate moves, but that did nothing to resolve things, so I installed the latest 2021.05.27 14:15 and the problem is resolved. Julian On 29/5/21 3:43 am, Pablo Rodriguez wrote: On 5/28/21 12:00 PM, Hans Hagen wrote: On 5/28/2021 11:40 AM, jbf wrote: [...] As this may be an 'ignorant' kind of question, something I should really know but don't, about paths and permissions, there may be someone else on the list with time (in lockdown like I am) to put me right. you need help from a linux expert indeed Just a comment. I also experienced problems in Linux with --luatex some days ago. I got everything right with current latest (2021.05.27 14:15). I would erase the cache and try it again: mtxrun --script cache --erase && mtxrun --generate I’m not a Linux expert at all. But this might help. Pablo -- http://www.ousia.tk ___ 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] BibTeX inproceedings entries not rendered correctly in APA style
On Fri, 28 May 2021 19:52:19 - (UTC) Nicola wrote: > > If there is no publisher, then @unpublished is a better category. > > APA explicitly, and for good reason, accounts for self-publishing, > > indicating that the Author was the publisher. > > Ah ok, that explains the output I was obtaining. So, I am using the > wrong bibliographic style for my purposes. In practice, at least in > Computer Science, publishers (and also editors) are often omitted in > references (it's more a "don't care", rather than a "don't know" > thing, though). > > > If a publisher does not exist, was it published? > > > > If the publisher is unknown, then why not state that: > > publisher="unknown publisher", or whatever? > > Strictly speaking, your reasoning makes perfect sense, and I am all > for enforcing constraints if a given bibliographic style requires > them. But then, there might be alternatives for when one does not > need to adhere to those styles. Does ConTeXt (LMTX) currently provide > anything else besides apa and aps? > > I have read the BibTeX manual looong time ago, but I remember that > there were mandatory and optional fields for each reference type. My > memory may fail me, but I think that Editor and Publisher were not > mandatory fields for inproceedings and article (I think Publisher is > mandatory for book). Is there a bibliographic style in ConTeXt that > follows those rules? > > Bibliography management is very sophisticated in ConTeXt (much more > than LaTeX) and I have not grasped all of its details yet. It seems > to me that it has also evolved quite a bit in recent years. So, the > "ConTeXt way" of doing bibliographies still eludes me to some extent. In writing the ConTeXt bibliography system, we tried to base this on references, indeed following the original bibtex manual for its definitions. The APA style follows the APA style guide as best as possible. The APS style is intended as a simple example of a numbered bibliography minimalist style. Multiple other styles exist out there, more or less well defined. The problem is that most of them are not very rigorous, and they are greatly abused. Many publishers follow their own (quirky) bibliography styles. The Context system started out as sort of a database handling subsystem, useful in publishing. It is entirely tune-able, through setups and parameters. However, the system is complex, so the customization is not quite as easy as originally intended. Note that the original bibtex system was conceived in order to have this configurability, however few were those who mastered writing bibliography styles, and even carefully crafted styles, for example as implemented by the APS RevTeX, were buggy and had a number of known, serious limitations requiring manual intervention. We could, and have had the intention of, writing other bibliography styles. But there must be a motivation as well as a clearly defined specification, for otherwise we will be heading down a rabbit hole of differing expectations and endless tweaking. As to "don't care" concerning publishers, this is not very academic. Indeed, many famous books have been published by various publishers, in particular for different markets. It is important to say, for each one might be slightly different, have different pagination for example, and even certain edits of the text. One might also not pay attention to the edition, but this too can lead to major differences (even, and especially in computer science). Thomas Schmitz, one of the originators of the bibliography project, will tell you to take the APA style as a model, and then modify it as you wish to your own needs. I further took this to heart, trying to write the macros as somewhat standard definitions that one could modify as needed without breaking the entire system. And then there are clearly bugs that can be fixed. In the case of a missing publisher, it is not simply left blank because the APA style explicitly tells us to put "Author" when there is no defined publisher, so this is a feature, not a bug. Alan ___ 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] BibTeX inproceedings entries not rendered correctly in APA style
On 2021-05-28, Alan Braslau wrote: > On Fri, 28 May 2021 13:02:10 -0400 (EDT) > Aditya Mahajan wrote: > >> > If you have not defined a publisher, how should ANY format place the >> > undefined publisher's name? >> >> Simply leave it blank? > > If there is no publisher, then @unpublished is a better category. APA > explicitly, and for good reason, accounts for self-publishing, > indicating that the Author was the publisher. Ah ok, that explains the output I was obtaining. So, I am using the wrong bibliographic style for my purposes. In practice, at least in Computer Science, publishers (and also editors) are often omitted in references (it's more a "don't care", rather than a "don't know" thing, though). > If a publisher does not exist, was it published? > > If the publisher is unknown, then why not state that: > publisher="unknown publisher", or whatever? Strictly speaking, your reasoning makes perfect sense, and I am all for enforcing constraints if a given bibliographic style requires them. But then, there might be alternatives for when one does not need to adhere to those styles. Does ConTeXt (LMTX) currently provide anything else besides apa and aps? I have read the BibTeX manual looong time ago, but I remember that there were mandatory and optional fields for each reference type. My memory may fail me, but I think that Editor and Publisher were not mandatory fields for inproceedings and article (I think Publisher is mandatory for book). Is there a bibliographic style in ConTeXt that follows those rules? Bibliography management is very sophisticated in ConTeXt (much more than LaTeX) and I have not grasped all of its details yet. It seems to me that it has also evolved quite a bit in recent years. So, the "ConTeXt way" of doing bibliographies still eludes me to some extent. Nicola ___ 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] LMTX and my custom typescripts
Michael Guravage schrieb am 28.05.2021 um 19:33: A pox upon me for a clumsy lout! You can also remove \usetypescriptfile[...] from your document because \setupbodyfont loads the file itself when the typeface and the file have matching names. Wolfgang ___ 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] BibTeX inproceedings entries not rendered correctly in APA style
On Fri, 28 May 2021 13:02:10 -0400 (EDT) Aditya Mahajan wrote: > > If you have not defined a publisher, how should ANY format place the > > undefined publisher's name? > > Simply leave it blank? If there is no publisher, then @unpublished is a better category. APA explicitly, and for good reason, accounts for self-publishing, indicating that the Author was the publisher. This is why it works that way. If a publisher does not exist, was it published? If the publisher is unknown, then why not state that: publisher="unknown publisher", or whatever? Alan ___ 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] --luatex option failing
On 5/28/21 12:00 PM, Hans Hagen wrote: > On 5/28/2021 11:40 AM, jbf wrote: >> [...] >> As this may be an 'ignorant' kind of question, something I should really >> know but don't, about paths and permissions, there may be someone else >> on the list with time (in lockdown like I am) to put me right. > you need help from a linux expert indeed Just a comment. I also experienced problems in Linux with --luatex some days ago. I got everything right with current latest (2021.05.27 14:15). I would erase the cache and try it again: mtxrun --script cache --erase && mtxrun --generate I’m not a Linux expert at all. But this might help. Pablo -- http://www.ousia.tk ___ 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] wrong link rectagle in LMTX
Dear list,
I have the following sample:
\setuppapersize[A9]
\setupinteraction[state=start]
\enabledirectives[references.border]
\unexpanded\def\MyURL#1%
{\bgroup\goto{{\tt\hyphenatedurl{#1}}}[url(#1)]\egroup}
\starttext
\startitemize
\dorecurse{2}{\item \MyURL{a.b\\/c.d\letterhash e}}
\stopitemize
\stoptext
I get an unindented link rectangle with LMTX (2021.05.27 14:15). Using
--luatex, the link rectangle is perfectly fine.
Could anyone confirm the issue?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
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] styling references
Dear list,
I have the following sample:
\starttext
\startitemize
\dorecurse{15}
{\item[\recurselevel]whatever}
\stopitemize
As exposed in \in{item}[9]...
\stoptext
How can I add style to the item reference (9)?
I mean, how can I get “As exposed in item {\em 9}”?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___
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] LMTX and my custom typescripts
A pox upon me for a clumsy lout! On Fri, May 28, 2021 at 6:54 PM Thomas A. Schmitz < thomas.schm...@uni-bonn.de> wrote: > > > On 28. May 2021, at 18:40, Michael Guravage < > gurav...@literatesolutions.com> wrote: > > > > Any encouragement in how to resolve this would be much appreciated. > > > > Hi Michael, > > Try renaming it to type-imp-DollyPro.tex (and then of course > \usetypescriptfile[type-imp-DollyPro]), that should help. This changed a > couple of months ago and was announced on the list, so shame on you for not > following our discussions religiously… > > Best > > Thomas > > ___ > 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] BibTeX inproceedings entries not rendered correctly in APA style
On Fri, 28 May 2021, Alan Braslau wrote: > On Thu, 27 May 2021 20:21:55 - (UTC) > Nicola wrote: > > > Thank you all for the precious comments. > > > > The current LMTX appears to have almost fixed my issue, except that > > inproceedings entries without a publisher have the text "Author" > > instead of the publisher's name. > > > > I must say that I have no requirement to use the APA style > > specifically; I do it only because it uses the format (Name, Year) > > for the citation. I guess that I could use another style (aps seems > > fine) and just customize the citation format. I have tried with > > > > \usebtxdataset[main.bib] > > \setupbtx[default:cite][alternative=authoryear] > > \usebtxdefinitions[aps] > > > > but it seems that the setup command has no effect: the citations still > > use numbers. > > APS is an inherently numbered citation format. > > If you have not defined a publisher, how should ANY format place the > undefined publisher's name? Simply leave it blank? Aditya ___ 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] LMTX and my custom typescripts
> On 28. May 2021, at 18:40, Michael Guravage > wrote: > > Any encouragement in how to resolve this would be much appreciated. > Hi Michael, Try renaming it to type-imp-DollyPro.tex (and then of course \usetypescriptfile[type-imp-DollyPro]), that should help. This changed a couple of months ago and was announced on the list, so shame on you for not following our discussions religiously… Best Thomas ___ 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] Luatex format error
> On 23 May 2021, at 23:41, Hans Hagen wrote: > > So this is not lmtx (which also has luatex) but the regular installation > right? The error occurs when there is a newline before the \starttext, as in the attachment. Remove the initial newline, and it compiles with context line_bug.tex A workaround is to give the name of the file at the prompt '**', but one will get another such prompt after the compile. line_bug.tex Description: Binary data ___ 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] LMTX and my custom typescripts
Yesterday I installed a new LMTX instance *ex nihilo*. Unfortunately, the new instance will not load my typescripts. My several commercial fonts and the typescripts I wrote for them reside in the texmf-project tree, along with a style file that loads them. I load the style file in my source files with the \environment command. The files in texmf-project are properly indexed. I know this, because the style file's name appears in the log, because I can list the fonts with mtxrun --script fonts --list --files --all --pattern=Dolly*, and because he style file evokes \showframe and \showgrid; the result of which I see in the typeset results. Regardless of whether a typescript files, e.g. type-DollyPro.tex, is in the texmf-tree or in the same directory as the ConTeXt source file, evoking \usetypescriptfile[type-DollyPro] fails. The log says: fonts > typescripts > unknown library 'DollyPro' fonts > typescripts > unknown library 'DollyPro' However, including the typescripts in the ConTeXt source file succeeds; which would seem to imply that my typescript definitions are correct. Using an old instance: LMTX LuaTeX 2.03 20191227 + ConTeXt MkIV 2019.12.27 19:26, loading the typescript via the style file works as expected. I regret that my mwe remains academic, since you need the Dolly font to run it. Any encouragement in how to resolve this would be much appreciated. Cheers, Michael % \starttypescript [serif] [DollyPro] % \definefontsynonym [Regular] [file:DollyPro-Regular.otf] % \definefontsynonym [Bold] [file:DollyPro-Bold.otf] % \definefontsynonym [Italic][file:DollyPro-RegularItalic.otf] % \definefontsynonym [SmallCaps] [file:DollyPro-RegularSmallCaps.otf] % \stoptypescript % \starttypescript [serif] [DollyPro] % \setups[font:fallback:serif] % \definefontsynonym [Serif] [Regular] [features=default] % \definefontsynonym [SerifBold] [Bold] [features=default] % \definefontsynonym [SerifItalic] [Italic][features=default] % \definefontsynonym [SerifCaps] [SmallCaps] [features=default] % \stoptypescript % \definefontfeature % [hz] [default] % [protrusion=quality, expansion=quality, mode=node, script=latn] % \starttypescript[DollyPro] % \definetypeface [DollyPro] [rm] [serif] [DollyPro] [default] [features=hz] % \stoptypescript \usetypescriptfile[type-DollyPro] \setupbodyfont[DollyPro] \starttext \input tufte \stoptext% Regular \starttypescript [serif] [DollyPro] \definefontsynonym [Regular] [file:DollyPro-Regular.otf] \definefontsynonym [Bold] [file:DollyPro-Bold.otf] \definefontsynonym [Italic][file:DollyPro-RegularItalic.otf] \definefontsynonym [SmallCaps] [file:DollyPro-RegularSmallCaps.otf] \stoptypescript \starttypescript [serif] [DollyPro] \setups[font:fallback:serif] \definefontsynonym [Serif] [Regular] [features=default] \definefontsynonym [SerifBold] [Bold] [features=default] \definefontsynonym [SerifItalic] [Italic][features=default] \definefontsynonym [SerifCaps] [SmallCaps] [features=default] \stoptypescript \definefontfeature [hz] [default] [protrusion=quality, expansion=quality, mode=node, script=latn] \starttypescript[DollyPro] \definetypeface [DollyPro] [rm] [serif] [DollyPro] [default] [features=hz] \stoptypescript % finis fonts > beware: no fonts are loaded yet, using 'lm mono' in box system > system > ConTeXt ver: 2021.05.27 14:15 LMTX fmt: 2021.5.28 int: english/english system > system > 'cont-new.mkxl' loaded open source > level 1, order 1, name '/opt/_lmtx_/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' system > beware: some patches loaded from cont-new.mkiv close source> level 1, order 1, name '/opt/_lmtx_/tex/texmf-context/tex/context/base/mkxl/cont-new.mkxl' system > files > jobname 'mwe', input './mwe', result 'mwe' fonts > latin modern fonts are not preloaded languages > language 'en' is active open source > level 1, order 2, name './mwe.tex' fonts > typescripts > unknown library 'DollyPro' fonts > typescripts > unknown library 'DollyPro' fonts > preloading latin modern fonts (third stage) fonts > 'fallback modern-designsize rm 12pt' is loaded open source > level 2, order 3, name 'tufte.tex' close source> level 2, order 3, name 'tufte.tex' backend > xmp > using file '/opt/_lmtx_/tex/texmf-context/tex/context/base/mkiv/lpdf-pdx.xml' pages > flushing realpage 1, userpage 1, subpage 1 close source> level 1, order 3, name './mwe.tex' system > start used files system > text: mwe system > stop used files system > start used files system >1: filename=char-prv.lua filetype=tex format=tex foundname=/opt/_lmtx_/tex/texmf-context/tex/context/base/mkiv/char-prv.lua
Re: [NTG-context] what happend to \writeline?
On 5/28/2021 6:05 PM, Werner Hennrich wrote: Hello everyone, I'm looking into my environment's logging to trace a problem and realize that \writeline is gone mute - that is, the output of subsequent logging lines now gets joined up in the same line, very hard to read... i'll check it - 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] what happend to \writeline?
Hello everyone,
I'm looking into my environment's logging to trace a problem and realize
that \writeline is gone mute -
that is, the output of subsequent logging lines now gets joined up in
the same line, very hard to read...
I observe this in version: 2021.05.27 14:15, as well as in version:
2021.05.27 14:15
the last one I used where \writeline did write (and end) the logging
line was version: 2021.03.17 17:46.
\def\log#1{
\message{ logging: #1}
\writeline
logging #1\par
}
\starttext
\log{the}
\log{quick}
\log{brown}
\log{fox}
\stoptext
used to log like this:
logging: the
logging: quick
logging: brown
logging: fox
but now:
logging: the logging: quick logging: brown logging: fox
Any idea how I can switch back the old behavior (on the new lmtx)?
Thanks you,
Werner
___
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] BibTeX inproceedings entries not rendered correctly in APA style
On Thu, 27 May 2021 20:21:55 - (UTC) Nicola wrote: > Thank you all for the precious comments. > > The current LMTX appears to have almost fixed my issue, except that > inproceedings entries without a publisher have the text "Author" > instead of the publisher's name. > > I must say that I have no requirement to use the APA style > specifically; I do it only because it uses the format (Name, Year) > for the citation. I guess that I could use another style (aps seems > fine) and just customize the citation format. I have tried with > > \usebtxdataset[main.bib] > \setupbtx[default:cite][alternative=authoryear] > \usebtxdefinitions[aps] > > but it seems that the setup command has no effect: the citations still > use numbers. APS is an inherently numbered citation format. If you have not defined a publisher, how should ANY format place the undefined publisher's name? I'm not sure what you want. Alan ___ 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] setupindentations
Am 27.05.21 um 21:24 schrieb Hans van der Meer: This macro \setupindentations is mentioned in my ConText the manual from november 12, 2001. It seems to have disappeared. Is that so? Then why? What replacement? How about \setupindenting ? https://wiki.contextgarden.net/Command/setupindenting Hraban ___ 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] Luatex format error
> On 23 May 2021, at 23:41, Hans Hagen wrote:
>
> So this is not lmtx (which also has luatex) but the regular installation
> right?
It works with
mtxrun math_style.tex
but not
context math_style.tex
where the file math_style.tex only contains
\starttext
\m{f = \beta}
\stoptext
It does not help with context --generate.
___
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] t-vim module: no highlighting for custom filetypes
>> >> Thanks. I have updated to version 2021.05.23 and run `mtxrun >> >> --generate`. Syntax highlighting is fine, but with LMTX I'm still >> >> getting an en-dash. Below, a MWE. >> > >> > Can you test if the file tests/vim/21-en-dash.tex works fine at your end: >> > >> > https://github.com/adityam/filter/blob/dev/tests/vim/21-en-dash.tex >> >> No, I get an en-dash with that, too. Log included below. > > For now, please use align=flushleft, either globally: > > \setupsyntaxhighlighting[align=flushleft] > > or as part of defining the typing environment: > > \definevimtyping[...][, align=flushleft, ...] I can confirm that this workaround works for me. Nicola ___ 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] --luatex option failing
On 5/28/2021 11:40 AM, jbf wrote: Still finding it very difficult to nail what the real problem is. You say: "An mtxrun --generate or even context --generate should work ok. if not there's something with permissions or paths or a missing file". Neither of the --generate options make any difference, so it clearly has to come down to "permissions or paths or a missing file". I cannot see that it is permissions. Comparing permissions on both machines (one working with --luatex and one not) I cannot see any difference. Paths? The only thing I can see is that I also have (later in the path) a separate installation for mkiv... but surely that would not make a difference? So, a missing file?? I renamed the current folder called lmtx so it would not be recognised (called it lmtxx) and created a new lmtx folder into which I have installed a new version (and obviously it would still be in the path, since ~/Documents/lmtx/tex/texmf-linux-64/bin is already in the path). So two questions: (1) Is it possible that having another version (mkiv) later in the path is causing the problem? (2) If a file is missing, what could it possibly be, given that I did a fresh install? not really, because the location where the running bin is found is determining the root of the to be used tds .. (i assume your cache is in that tree, not in some /tmp although even then the hashed name should prevent clashes) As this may be an 'ignorant' kind of question, something I should really know but don't, about paths and permissions, there may be someone else on the list with time (in lockdown like I am) to put me right. you need help from a linux expert indeed 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 ___
Re: [NTG-context] --luatex option failing
Still finding it very difficult to nail what the real problem is. You say: "An mtxrun --generate or even context --generate should work ok. if not there's something with permissions or paths or a missing file". Neither of the --generate options make any difference, so it clearly has to come down to "permissions or paths or a missing file". I cannot see that it is permissions. Comparing permissions on both machines (one working with --luatex and one not) I cannot see any difference. Paths? The only thing I can see is that I also have (later in the path) a separate installation for mkiv... but surely that would not make a difference? So, a missing file?? I renamed the current folder called lmtx so it would not be recognised (called it lmtxx) and created a new lmtx folder into which I have installed a new version (and obviously it would still be in the path, since ~/Documents/lmtx/tex/texmf-linux-64/bin is already in the path). So two questions: (1) Is it possible that having another version (mkiv) later in the path is causing the problem? (2) If a file is missing, what could it possibly be, given that I did a fresh install? As this may be an 'ignorant' kind of question, something I should really know but don't, about paths and permissions, there may be someone else on the list with time (in lockdown like I am) to put me right. Julian On 28/5/21 5:15 pm, Hans Hagen wrote: On 5/28/2021 7:13 AM, jbf wrote: Hi list, Not at all sure why this is happening. In my most recent install of lmtx (which works fine as lmtx) on Linux, I wanted to choose the --luatex option just to make a comparison between the mkiv output and lmtx. The redirection part seems to work (... --script mtx-context --luatex myfile.tex --redirected), but no 'resolvers' follow. Instead I get mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua'. I have tried both luatextools --generate and mtxrun --generate, but neither of these fix the problem. Would someone know why this is not working? Or even better, how to fix it? I installed lmtx on another machine and have no problems using the --luatex option there, so the matter is not urgent for me, just puzzling! I do have a separate mkiv installation as well, but my understanding is that they would not conflict. LMTX contains everything that is needed. In lmtx "mtxrun" and "context" are just links to "luametatex" and when called with a different name than "luametatex" they will try to locate scripts with their name in the same path (so there need to be mtxrun.lua and context.lua in that nin path). The mtxrun.lua file contains most lua libs so it can provide the same helpers as in context, when used as stand alone runner (so, instead if native lua one can just use mtxrun) while the context.lua script will locate mtx-context.lua and run that one. For that it needs the file database. Forget about luatools .. gone for ages. An mtxrun --generate or even context --generate should work ok. if not there's somethign with permissions or paths or a missing file. 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 ___
Re: [NTG-context] --luatex option failing
On 5/28/2021 7:13 AM, jbf wrote: Hi list, Not at all sure why this is happening. In my most recent install of lmtx (which works fine as lmtx) on Linux, I wanted to choose the --luatex option just to make a comparison between the mkiv output and lmtx. The redirection part seems to work (... --script mtx-context --luatex myfile.tex --redirected), but no 'resolvers' follow. Instead I get mtxrun | unknown script 'mtx-context.lua' or 'mtx-mtx-context.lua'. I have tried both luatextools --generate and mtxrun --generate, but neither of these fix the problem. Would someone know why this is not working? Or even better, how to fix it? I installed lmtx on another machine and have no problems using the --luatex option there, so the matter is not urgent for me, just puzzling! I do have a separate mkiv installation as well, but my understanding is that they would not conflict. LMTX contains everything that is needed. In lmtx "mtxrun" and "context" are just links to "luametatex" and when called with a different name than "luametatex" they will try to locate scripts with their name in the same path (so there need to be mtxrun.lua and context.lua in that nin path). The mtxrun.lua file contains most lua libs so it can provide the same helpers as in context, when used as stand alone runner (so, instead if native lua one can just use mtxrun) while the context.lua script will locate mtx-context.lua and run that one. For that it needs the file database. Forget about luatools .. gone for ages. An mtxrun --generate or even context --generate should work ok. if not there's somethign with permissions or paths or a missing file. 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 ___
Re: [NTG-context] no leavevmode
On 5/27/2021 10:43 PM, Hans van der Meer wrote:
Why is there not implemented in \subsection a \leavevmode at the end of
it? Here a minimal example showing that starting with the first word in
an \hbox encounters vertical mode. Thus requiring a \leavevmode to put
it on line with the following text. Whereas not starting with an \hbox
does an implicite switch to horizontal mode.
I can imagine that this behaviour could be confusing for users not well
versed in the different behaviour of the horizontal and vertical modes.
Therefore my question: Wouldn't it be wise to implement that \leavevmode?
\startsubsection[title=TEST]
\hbox{abc} def\crlf
ghi jkl xyz
\stopsubsection
first of all, context never uses (and used) \leavevmode and that is for
a good reason
anyway, adding any mode change command automatically will somehow
interfere,
\starttext
\def\MyTitle#1{\blank{\bf#1}\blank}
\MyTitle{xxx}
\MyTitle{xxx}
\MyTitle{xxx}
\MyTitle{xxx}
\def\MyTitle#1{\blank{\bf#1}\blank\leavevmode}
\MyTitle{xxx}
\MyTitle{xxx}
\MyTitle{xxx}
\MyTitle{xxx}
\stoptext
so, when we'd add that you would ask: why is there not implemented that
unwanted \leavevmode's get cleaned up
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
___
Re: [NTG-context] t-vim module: no highlighting for custom filetypes
On Thu, 27 May 2021, Nicola wrote: > On 2021-05-27, Aditya Mahajan wrote: > > On Thu, 27 May 2021, Nicola wrote: > > > >> On 2021-05-24, Aditya Mahajan wrote: > >> > On Fri, 21 May 2021, Nicola wrote: > >> > > >> >> I have only a minor annoyance: I have just noticed that -- is typeset as > >> >> an en-dash in LMTX (but not in MKIV, as documented). Could you look into > >> >> that? > >> > > >> > Fixed in the new release. > >> > >> Thanks. I have updated to version 2021.05.23 and run `mtxrun > >> --generate`. Syntax highlighting is fine, but with LMTX I'm still > >> getting an en-dash. Below, a MWE. > > > > Can you test if the file tests/vim/21-en-dash.tex works fine at your end: > > > > https://github.com/adityam/filter/blob/dev/tests/vim/21-en-dash.tex > > No, I get an en-dash with that, too. Log included below. For now, please use align=flushleft, either globally: \setupsyntaxhighlighting[align=flushleft] or as part of defining the typing environment: \definevimtyping[...][, align=flushleft, ...] I'll test a bit more carefully and then upload a new version. Aditya ___ 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 ___
