- ntg-context - NTG Mailing Lists

Bug report: \setupbackend corrupts bibliography rendering
by a badin 28 Feb '21

28 Feb '21

Dear gardeners, I'm new to ConTeXt and would like to share a possible bug with you. If I have the \setupbackend[export=example.xml,css=example.css] entry in my .tex file, then my bibliography renders in a strange way (text copied from pdf): 1 bfldcategoryarticle: [author: Andrej Arrow] [journal: MAPS] [keywords: context] [pages: 2-8] [title: The Font Name Mess] [volume: 40] [year: 2010] If I remove or comment that entry out, then the bibliography renders OK (copy from pdf): 1 A. Arrow, “The Font Name Mess”, *MAPS *40, 2-8, 2010. my .tex source is: % \setupbackend[export=example.xml,css=example.css] \usebtxdataset[default][ref.bib] \starttext \cite[Arrow][Arrow] \placelistofpublications \stoptext my ref.bib file: @ARTICLE{Arrow, author = {Andrej Arrow}, title = {The Font Name Mess}, journal = {MAPS}, year = {2010}, volume = {40}, pages = {2-8}, keywords = {context}, } Hope this helps, best, Andrej -- Andrej Badin +31 6 82 23 50 33

2 2

Incorrect css reference in exported html file
by Aditya Mahajan 27 Feb '21

27 Feb '21

Hi, This message is prompted by a bug report for t-vim (https://github.com/adityam/filter/issues/43) but the issue is more general. Whenever, `cssfile` in `\setupexport` points to a file now in $PWD, the reference to the file in the exported CSS is incorrect: Consider the following directory tree: test.tex styles/mystyle.css where test.tex is: ``` \setupbackend[export=yes] \setupexport[cssfile=styles/mystyle.css] \starttext \startparagraph This is a test \stopparagraph \stoptext ``` and styles/mystyle.tex is (the content doesn't matter, listing it for completeness): ``` paragraph, p, div.paragraph, div.p { color : red ; } ``` I am attaching a zip file for convenience. When I compile the above file, I get (selective lines from output) ``` backend > export > copying styles/mystyle.css ... backend > export > adding css reference 'styles/styles/mystyle.css' ``` Indeed, the styles/mystyle.css file is copied to `test-export/styles/mystyle.css` but the reference in `test-export/test-export-div.html` is: ``` <link type="text/css" rel="stylesheet" href="styles/styles/mystyle.css" /> ``` Note the repeated styles/styles. What is happening is that while copying the file, context is using (in back-exp.lua): local source = addsuffix(cssextra[i],"css") local target = joinfile(stylepath,basename(source)) while for reference, context is using: result[#result+1] = replacetemplate(csspreamble, { filename = cssfile }) extras[#extras+1] = replacetemplate(cssheadlink, { filename = cssfile }) Shouldn't the last part be filename=basename(source) to get the right name? Without that whenever the value of cssfile is a file in another directory, the css reference in the exported html file will be incorrect. In case anyone is interested, this manifests in t-vim as follows. The t-vim module includes a pre-generated css file which provides the color and style values for the default color schemes. The module provides a macro \vimcssfile, which is the complete path of the file (basically the value of `resolvers.resolve("full:vimtyping-default.css")`). The intended usage is: \usemodule[vim] \setupbackend[export=yes] \setupexport[cssfile=\vimtypingcssfile] ... In this case, the css file is correctly copied to the '\jobname-export/styles` directory. but the `\jobname-div.html` file contains a unusable reference: ``` ... <link type="text/css" rel="stylesheet" href="styles/opt/luametatex/texmf-modules/tex/context/third/vim/vimtyping-default.css" /> ``` In principle, I can work around this in t-vim but I think that this will impact others as well. Thanks, Aditya

1 0

\showcolor broken in LMTX
by Jairo A. del Rio 27 Feb '21

27 Feb '21

Hi, list. The following example fails in LMTX, but it works in MkIV: \starttext\showcolor[svg]\stoptext LMTX complains about a s-colors-run file not found Best regards, Jairo

2 2

\hbox to ... equivalent in ConTeXt (\framed)
by Jairo A. del Rio 26 Feb '21

26 Feb '21

Hi list. Is there an interface for \hbox to <size> via framed? I think it's not the ConTeXt spirit to do something like \framed[offset=0cm]{\hbox to 10cm{Uno dos tres}} where spacing is stretched so all the available space is filled, so I want to know about a better way. Thank you beforehand. Cordially, Jairo

3 5

How to reduce the inter-item space
by Alain Delmotte 26 Feb '21

26 Feb '21

4 6

Warning: "nodes: unable to store reference from lua in tex"
by Lukas/ConTeXt 26 Feb '21

26 Feb '21

Hello, after I renewed ConTeXt MkIV, I started to get the following warning: " ... luatex warning > nodes: unable to store reference from lua in tex ... (repeated more times) " This happens when I try to typeset a looo...ong table (by \start/\stop-tabulate) over several pages. It used to work OK with a Ctx version several months (or half year) ago. Is there a simple way to overtake the problem? MWE: ---- \starttext \startluacode context[[ \starttabulate[|Tr|] \HL \NC AABBCC \NC\AR \HL[3] ]] for i = 1, 4000 do context.NC(i) context.NC() context.AR() end context[[ \HL \stoptabulate ]] \stopluacode \stoptext ---- Best regards, Lukas

3 3

Re: [NTG-context] How to reduce the inter-item space
by Alain Delmotte 26 Feb '21

26 Feb '21

1 0

looping an overlay
by Pablo Rodriguez 24 Feb '21

24 Feb '21

Dear list, I have the following sample: \starttext \startTEXpage[offset=1em] \startoverlay \dostepwiserecurse{25}{95}{5} {{\recurselevel\ }} \stopoverlay \stopTEXpage \stoptext Which is the right way to loop an overlay? Many thanks for your help, Pablo -- http://www.ousia.tk

2 2

Help figuring why long document stops short in xml export
by Christoph Hintermüller 24 Feb '21

24 Feb '21

Hi What command line parameters, trackers etc I should activate when i want to figure why my document lacks content worth of several pages in xml export while the pdf which is created in parallel contains all pages. I'm using mtx-context | ConTeXt Process Management 1.04 mtx-context | mtx-context | main context file: <prefixpath>/tex/texmf- context/tex/context/base/mkiv/context.mkiv mtx-context | current version: 2021.02.14 16:39 mtx-context | main context file: <prefixpath>/tex/texmf- context/tex/context/base/mkxl/context.mkxl mtx-context | current version: 2021.02.14 16:39 Would switching to lmtx may be helpful in at least figuring why or be the only known solution? The Document it self is my lecture notes which are about 125 Pages long. The xml export ends at Page 63. Are there any known commands which can cause exporter to give up early and thus should in export be avoided or be put in mode dependent block hiding them form exporter. Any hint what i should, would have to check and how to hopefully grabe any hint where to amend the document to get full output. Currently i have not made images mode dependent (pdf:metapost, xml:png/svg). Could that be a reason why exporter finally ends document early? I'm sorry to be so clue less to not be able to provide more information. The document it self is too big to be posted and i do not want to make it public anyway, but if required i can provide a share link. Best Christoph Hintermüller

3 6

Letter module not found by LMTX
by Henning Hraban Ramm 24 Feb '21

24 Feb '21

Hi, I just stumbled upon this, no time for further checks ATM: \usemodule[letter] can’t find the installed letter/correspondence module in LMTX mode, while MkIV works flawlessly. Don’t know if other modules are affected. Hraban

3 3