- dev-context - NTG Mailing Lists

x-setups-basics.mkiv
by Wolfgang Schuster 12 Oct '16

12 Oct '16

Hi, grouping is necessary to keep \ttbf local. \startxmlsetups xml:setups:typeset:line + \bgroup \ttbf \nohyphens \xmlsetup{#1}{xml:setups:make:prepare} \directsetup{xml:setups:make:start} \xmldoif{#1}{/arguments} { \bgroup \settrue\c_cmd_doing_line \global\c_cmd_current_argument\zerocount \ignorespaces \xmlfilter{#1}{/arguments/text()} \egroup } \directsetup{xml:setups:make:stop} + \egroup \stopxmlsetups Wolfgang

1 0

bad i-common-value.xml
by luigi scarso 10 Oct '16

10 Oct '16

tex/texmf-context/tex/context/interface/mkiv$ xmllint *.xml >/dev/null i-common-value.xml:14: parser error : Opening and ending tag mismatch: parameter line 10 and define </cd:define> ^ i-common-value.xml:577: parser error : Opening and ending tag mismatch: define line 9 and interface </cd:interface> ^ i-common-value.xml:578: parser error : Premature end of data in tag interface line 5 -- luigi

2 2

x-setups-basics.mkiv
by Wolfgang Schuster 28 Sep '16

28 Sep '16

Hi, \startxmlsetups xml:setups:instance - \xmlatt{#1}{value}\enspace + \xmlatt{#1}{value}\enskip \stopxmlsetups Wolfgang

1 0

m-educat.mkiv
by Wolfgang Schuster 28 Sep '16

28 Sep '16

Hi, \def\doanswerspace[#1]% {\begingroup \dontcomplain \setupanswerarea [\c!n=0,\c!m=,#1,\c!location=\v!text]% + \let\currenttextbackground\v!answerarea \doifelsenothing{\textbackgroundparameter\c!m} {\expandafter\donoanswerspace} {\expandafter\dodoanswerspace}% [#1]} \def\dostartanswerlines[#1]% {\begingroup \dontcomplain \setupanswerarea [\c!n=0,\c!m=,#1,\c!location=\v!text]% + \let\currenttextbackground\v!answerarea \doifnot{\textbackgroundparameter\c!option}\v!joinedup\softbreak \doifelsenothing{\textbackgroundparameter\c!m} {\expandafter\donostartanswerlines} {\expandafter\dodostartanswerlines}% [#1]} Wolfgang

1 0

Luatex 1.0.0 announcement
by luigi scarso 27 Sep '16

27 Sep '16

Version 1.0.0 After some ten years of development and testing, today we have released LuaTeX 1.0.0! Instead of staying below one and ending up with versions like 0.99.1234, we decided that the moment is there to show the TeX audience that LuaTeX is stable enough to loose its beta status. Although functionality has evolved and sometimes been replaced, we have been using LuaTeX in production right from the start. Of course there are bugs and for sure we will fix them. Our main objective is to provide a variant of TeX that permits user extensions without the need to adapt the inner workings. We did add a few things here and there but they mostly relate to opening up the inner parts and/or the wish to influence some hard coded behaviour. Via Lua we managed to support modern functionality without bloating the code or adding more and more dependencies on foreign code. In the process a stable and flexible MetaPost library became part of the engine. The functionality as present now will stay. We might open up some more parts, we will stepwise clean up the code base while staying as close as possible to the Knuthian original, we will try to document bits and pieces. We might also experiment a bit with better isolation of the backend, and simplify some internals. For that we might use the experimental version but if we divert too much we may need to give that another name. We want to thank all those who have tested the betas and helped to make LuaTeX better. Hans Hagen Hartmut Henkel Taco Hoekwater Luigi Scarso

1 0

x-setups-basics.mkiv
by Wolfgang Schuster 27 Sep '16

27 Sep '16

Hi, \unexpanded\def\show_setup_any#1#2% {\bgroup \global\advance\c_cmd_current_argument\plusone - \doif{\xmlatt{#1}{optional}}{yes}\donetrue\donefalse + \doifelse{\xmlatt{#1}{optional}}{yes}\donetrue\donefalse \setbox0=\hbox {\ifdone\sl\fi \doifelse{\xmlatt{#1}{list}}{yes} {\getsetupstring{cd:#2-l}}% {\getsetupstring{cd:#2-s}}}% \setbox2=\hbox to \wd0 {\hss \ifcase\c_cmd_kind\else \ifcase\c_cmd_maximum_argument \relax \or \raise1.25\exheight\hbox {\txx *}% \else \raise1.25\exheight\hbox {\txx\the\c_cmd_current_argument}% \fi \fi \hss}% \setbox4=\hbox to \wd0 {\hss \ifdone \lower2\exheight\hbox \bgroup \txx \getsetupstring{cd:optional}% \egroup \hss \fi}% \ht2\ht\strutbox \dp4\dp\strutbox \hskip.5\emwidth \wd0\zeropoint \box0 \wd2\zeropoint \box2 \box4% \egroup \ignorespaces} Wolfgang

1 0

mult-def.lua
by Wolfgang Schuster 27 Sep '16

27 Sep '16

Hi, cd:oneargument etc. are strings (no -s or -l variants)but something has to be changed because they end up with duplicated hashes (##1 instead of #1). A entry for parentheses has to be added as well. mult-def.lua: ["cd:xmlsetup"]={ ["cs"]="xmlsetup", ["de"]="xmlsetup", ["en"]="xmlsetup", ["fr"]="xmlsetup", ["it"]="xmlsetup", ["nl"]="xmlsetup", ["ro"]="xmlsetup", }, + ["cd:oneargument"]={ + ["en"]="\\...#1", + }, + ["cd:twoarguments"]={ + ["en"]="\\...#1#2", + }, + ["cd:threearguments"]={ + ["en"]="\\...#1#2#3", + }, ["cd:sign"] = { en = "[-+]" }, ["cd:csname-s"] = { en = "\\..." }, ["cd:csname-l"] = { en = "\\..." }, ["cd:noargument-s"] = { en = "\\..." }, ["cd:noargument-l"] = { en = "\\..." }, - ["cd:oneargument-s"] = { en = "\\...#1" }, - ["cd:oneargument-l"] = { en = "\\...#1" }, - ["cd:twoarguments-s"] = { en = "\\...#1#2" }, - ["cd:twoarguments-l"] = { en = "\\...#1#2" }, - ["cd:threearguments-s"] = { en = "\\...#1#2#3" }, - ["cd:threearguments-l"] = { en = "\\...#1#2#3" }, ["cd:braces-s"] = { en = "{...}", lua = '"..."' }, ["cd:braces-l"] = { en = "{...,...}", lua = '".. ... .."' }, ["cd:brackets-s"] = { en = "[...]", lua = "{ ... }" }, ["cd:brackets-l"] = { en = "[...,...]", lua = "{..., ...}" }, + ["cd:parentheses-s"] = { en = "{...}", lua = '"..."' }, + ["cd:parentheses-l"] = { en = "{...,...}", lua = '".. ... .."' }, ["cd:index-s"] = { en = "[...]" }, ["cd:index-l"] = { en = "[..+...+..]" }, Wolfgang

1 0

tabl-tbl.mkiv
by Wolfgang Schuster 26 Sep '16

26 Sep '16

Hi, \def\tabl_tabulate_inside_before {\ifhmode\par\fi \ifhmode \ifinsidesplitfloat \let\tabl_tabulate_inside_after \relax + \let\tabl_tabulate_inside_inbetween\relax \else \vbox\bgroup \let\tabl_tabulate_inside_after \egroup + \let\tabl_tabulate_inside_inbetween\relax \fi \else \let\tabl_tabulate_inside_after \relax + \let\tabl_tabulate_inside_inbetween\relax \fi} Wolfgang

1 0

Pragma website and alpha uploads?
by Taco Hoekwater 22 Sep '16

22 Sep '16

Hi, On the subject of 'latest', there is a bug it seems: it looks like the Download section of the pragma website no longer picks up 'latest' uploads since the change from '/alpha' to '/latest' in the folder name? Best wishes, Taco

2 2

New style bibliographies
by Taco Hoekwater 12 Aug '16

12 Aug '16

Hi, Working on the next issue of the CG Journal, I finally had a good reason to look at the new bibliography code. Even with a big manual, it was still a bit of challenge. The article I was working on was written for mkii, and came with a prebuilt .bbl file for that (but not with the original .bib files). The original databases look like they were created for latex so there were some problems with embedded commands and it being 8-bit (ISO-latin), but that was to be expected. Some other problems seems to be more related to differences between the mkii and the mkiv bibliography code. First question: is there a ‘default’ or ‘standard’ dataset, or not? If so, is it named ‘default’ or ‘standard’? The bit of code on the wiki and the actual manual seem to disagree on that. My current solution looks like this: \usebtxdataset[h-all-forced.bbl] \usebtxdefinitions[aps] \setupbtxrendering[alternative=aps] … \placelistofpublications[criterium=text] That works, but almost all the documentation uses either [default] or [standard]. Second question: It appears I need both \usebtxdefinitions and \setupbtxrendering, which surprised me. I understand that right now, there is only ‘apa’ and ‘aps’, but it seems neither are preloaded? Without the \usebtxdefinitions, I did get a list of publications, but with horrible formatting, especially for ‘manual’ and ‘inproceedings’. Contrary to what the manual says, \cite[key] does not seem to work. however, \citation[key] does. So, in the preamble I now have \let\cite\citation but isn’t it weird that I needed that? More importantly (read: "more timeconsuming-ly"), there are some differences in the .bbl processing compared to mkii, which is not great. So far, I found this: * mkii used \arttitle in some spots. To be exact: in ‘article’, ‘incollection’, and ‘inproceedings’ entries. I changed the ones in ‘article' to \title inside the .bll to get these to work. * That fixed ‘article’s, but ‘inproceedings’ and ‘incollection’ are broken, because these *also* has an actual \title for the complete proceedings/collection, and I do not know how to make the module display both titles. Please help, because I definitely need the ‘inproceedings’ one to work properly! I now get formatted output like this: [18] J.-M. Hufflen, Proc. 6th ConTEXt Meeting & EuroTEX 2012 (2012). (actually twice the exact same entry, because there were two articles by J-M in that one proceedings). Do I need \booktitle? Not that I mind, but it is a little odd in the sense that a ‘collection’ has a title, but it is not really a ‘book title’, it is a ‘collection title’ (and likewise for 'proceedings’) ;) * In mkii, the bbl uses e.h. \artauthor[]{John}[J.]{}{Doe}. The problem I have there is that the new biblio code (at least the ‘aps’ version) inserts dots after the initials in the output list, So I end up with “J.. Doe”. I like the ‘adding a dot’ in principle, but if it stays, then it should definitely be conditional on whether or not the initials already have one. Having to edit the datafile the fix the double dot was quite uncomfortable. * I had to change the .bbl, replacing all \pubyear with \year. The extra \pub… prefix was there because of conflicts with the primitive \year in mkii and it makes sense to not require it any more in mkiv, but nevertheless it would be helpful if \pubyear could be used as an alias to \year. Not the hardest change though, it was a single global replace in the bbl, so a low priority request. * The new ‘aps’ style does not print the publisher name for ‘book’ (at least, I probably missed others). I assume this is because of the ‘not quite ready yet’ state of new biblio code, but I hope that will be fixed at some point. And there are probably a few other (less common) fields still missing, right?. Probably because the .bbl uses e.g. \pubname, not ‘\publisher’? I don’t want to go looking for these missing fields just now, but I would be willing to do at some later date. Finally: the manual says there are various ‘required fields’ for the entry types. That is great, but could there be some (optional) visual feedback in the formatted list if such a required field is in fact missing? traditionally, that would a black square, but a bold *publisher missing* would be very useful. That’s it for now. Sorry about the long list of complaints. I do appreciate the amount of work needed to get bibliographies working even without having to worry about backward compatibility, but I feel it is important that, if there is supposed to be backward compatibility, that it ten be as close to perfect as technically possible. Even if it is a bit of pain. Best wishes, Taco

2 4