- ntg-context - NTG Mailing Lists

descriptions failing in mkiv
by Hans van der Meer 22 Mar '10

22 Mar '10

I made use of descriptions in mkii. For example: % Define the intro for the annotation % Block opened on \startquestion and closed on \stopquestion % \startannotation{} ... \stopannotation; {} required \definedescription[annotationblock][% \c!margin=\v!no,\c!location=\v!top,\c!width=\v!broad,% \c!headstyle=\@@exmintrostyle,\c!style=\@@exmstyle,% \c!before=,\c!inbetween=,\c!after=,% \c!text=\placeannotationstart] etcetera The error message in latest context beta is: ! Use of \@@startdescription doesn't match its definition. \doifnextoptionalelse ...\nextoptionalcommandyes { #1}\def \nextoptionalcomma... \setuptextrules ...odoubleargument \getparameters [\??tl ] \placeannotationstart ...aloffset \setuptextrules [\c!style = \@@exmintrostyl... \dododescriptioncomponent ...onparameter \c!label }\xdef \currentdescription... \@@makedescription ...},\c!bookmark =,\c!list =][] \@@dostartdescriptionindeed \dodogotopar ->\@@makedescription []{} \BeforePar \emptytoks ... Can someone tell me if it is known to be broken in mkiv? Before delving too deep in the code myself.... Hans van der Meer

2 2

synctex broken
by Steffen Wolfrum 22 Mar '10

22 Mar '10

Hi, with yesterdays beta (ConTeXt ver: 2010.03.20 22:59 MKIV) synctex seems to be broken: no response in none direction (source<->pdf). Steffen

5 6

Problem in sorting bibtex entries
by Mikael Persson 22 Mar '10

22 Mar '10

Dear Taco and list, I have a problem (with the latest minimals) sorting bibtex entries: Consider the following example: % bibbug.tex \usemodule[bib] \setuppublications[ sorttype=bbl, ] \setupbibtex[ database=mp, ] \starttext See~\cite{resi3,resi4} and also~\cite{resi2,resi1}. \placepublications[criterium=all] \stoptext % end of bibbug.tex I get an eror: ! LuaTeX error ...TeXt/tex/texmf-context/tex/context/base/bibl-tra.lua:83: attempt to compare two nil values stack traceback: ...TeXt/tex/texmf-context/tex/context/base/bibl-tra.lua:83: in function <...TeXt/tex/texmf-context/tex/context/base/bibl-tra.lua:80> [C]: in function 'sort' ...TeXt/tex/texmf-context/tex/context/base/bibl-tra.lua:93: in function 'flush' <main ctx instance>:1: in main chunk. \typesetpubslist ...hacks.flush("\@@pbsorttype ")} \doendoflist \dodoplacepublications ...sttrue \typesetpubslist \inpublistfalse \endgroup ... l.14 \placepublications[criterium=all] If I uncomment the sorttype=bbl line, it compiles. Attached is the tex file, the log file, and my bib file. Best regards, Mikael

3 4

startlanguagespecifics missing in mkiv
by Hans van der Meer 22 Mar '10

22 Mar '10

The following macro is present in mkii but obviously missing in mkiv. Why? I have a use for it. ConTeXt ver: 2010.03.20 22:59 MKIV fmt: 2010.3.21 int: english/ english ! Undefined control sequence. l.184 \startlanguagespecifics [nl] In mkii in lang-spe.mkii \def\startlanguagespecifics% % we use double to {\bgroup ... \dodoubleempty\dostartlanguagespecifics} % get rid of spaces Hans van der Meer

2 1

sort-lan.lua line 157
by Philipp Gesang 22 Mar '10

22 Mar '10

Hi, I had a look at sort-lan.lua, here are lines 156--158: ['y'] = 38, -- y ['z'] = 49, -- z [uc(0x017E)] = 40, -- zcaron I guess the correct value for “z” should be “39”? Philipp -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments

2 1

Problem with \c{a}
by Mikael Persson 22 Mar '10

22 Mar '10

Dear list, I cannot get \c{a} to work in mkiv. Small test file: \starttext \c{c} % works both in mkii and mkiv \c{a} % works only in mkii (in mkiv I get nothing) \stoptext Is there a fix for this? I would not like to use the unicode char directly in the file (because I have this inside a bib-entry and I'd like to keep the bib file without such constructions.) Best regards, Mikael

3 6

index / line-break bug
by Steffen Wolfrum 21 Mar '10

21 Mar '10

Hi, in yesterday's beta (ConTeXt ver: 2010.03.20 22:59 MKIV) there still is this index/line-break bug, see example below please: \setuplayout [width=113mm,location=middle] \usetypescript[postscript] \definetypeface[postscript][rm][serif][times][default] \mainlanguage[de] \setupbodyfont[postscript,10pt] \setupinterlinespace[line=12pt] \setupalign[line,block] \starttext dieses ist dabei typisch für den Bereich der Architekten- oder Ingenieurleistungen\index{Ingenieurleistungen}. Warum? \stoptext Steffen

2 2

More on Adobe Multiple Master fonts (not quite dead yet:-)
by Graham Douglas 21 Mar '10

21 Mar '10

Dear Hans + Taco I have a question about "Minion Expert" fonts. I do have a copy of Idris's paper on this very topic but I'm not sure if this is still the way to install fonts via MKIV/LuaTeX. I'll give some background on what I'm doing, so my apologies to the list for the long post. [Note: happy to write this up in full for the Wiki at some point if of more general interest] I have been able to create hundreds of Minion instances and (with the excption of "Expert") successfully install them in Context --- works really very well. I have tested the PDF output with 500+ separate instances embedded, all seem to work perfectly --- provided the mmpfb settings are right. The resulting instances/fonts (.afm, .pfb) are output directly into the Context tree with names like MinionRegularRoman_wt525_wd600_op20.[afm|pfb] Generally the names are formed as follows: Minion[Variety][Angle]_wt[num]_wd[num]_op[num] Variety = one of Expert,Regular,Smallcaps Angle = one of Roman,Italic After refreshing the font lists/file name databases all instances can all be accessed through commands like this \definedfont[MinionRegularRoman_wt450_wd600_op10 at 12pt] --- I intend to write a typescript to set them up properly but these are early days for me with Context. I'm hoping that the above font naming convention will allow me to write a quite flexible set of typescripts... eventually. The only one that does not work is the Expert font (no surprise I guess) As mentioned, my scripts output the fonts directly into the Context tree, for Regular,Smallcaps varieties that's all I have to do. Wonderful! So, to the "Expert" variety... Clearly, this font has a "non standard" encoding vector which is causing the problm (I guess). The AFM records EncodingScheme FontSpecific If I install instances like MinionExpertRoman_wt350_wd450_op10.afm then run the minimal example \starttext \definedfont[MinionExpertRoman_wt500_wd450_op10 at 12pt] This is an interesting test. 1234567890. filling, fill. ABCDEF. \stoptext When I run this for the firt time I get !load afm : reading c:/Context/tex/texmf-context/fonts/afm/minion/MinionExpertRoman/MinionExpertRoman_wt500_wd450_op10.afm !load afm : unifying c:/Context/tex/texmf-context/fonts/afm/minion/MinionExpertRoman/MinionExpertRoman_wt500_wd450_op10.afm !afm glyph : assigning private slot U+F0000 for unknown glyph name Acutesmall !afm glyph : assigning private slot U+F0001 for unknown glyph name nineoldstyle <snip> The resulting PDF is blank, apart from the dot and commas in the sample text "This is an interesting test. 1234567890. filling, fill. ABCDEF." So, finally to my question: what additional work do I need to do to fully integrate the Expert fonts to access some of the nice features of these fonts? Warm wishes Graham =======

3 3

Table of contents
by Alain Delmotte 21 Mar '10

21 Mar '10

Hi! I have two question about table of contents. 1) is it possible to have the toc at the end of the document. I tried to place \placecontent or \completecontent at the end and it didn't work; I only managed to have the toc at the beginning of the document. 2) If I define my own header (like in ConTeXt an excursion: 5. Headers) and so, for example, replacing \section by \myheader, which has a section level, the table of content is empty! If the information is in another document, please give me a pointer, thanks! Alain

4 3

stripping space from xml nodes
by Hans van der Meer 21 Mar '10

21 Mar '10

In order to have (1) <abc>text</abc> behave the same as (2) <abc> text </abc> one can use \xmlstripped{node}{lpath}. However, the drawback is that I found there is no further node expansion of inner content. For example \xmlstripped with <abc>text <somenode/> text</abc> returned "text <somenode/> text". I have already reported earlier that I could not see \xmlstrip{node} {lpath} work as I understood it. That is, it seems to me that in: \startxmlsetups xml:abc \xmlstrip{#1}{} \stopxmlsetups this would strip the spaces from (2) above. It didn't do that, while I also tried of course \xmlstrip in the node enclosing <abc>, also to no avail. As a work around one finds: \startxmlsetups xml:abc \ignorespaces % removes spurious space before \xmltext{#1}{} \unskip % removes spurious space after \stopxmlsetups but it is the sort of a kludge I do not feel happy about, apart from the fact that either this has to be put everywhere or another macro layer put around all \xml's suffering. This boils down to two questions: (1) how about \xmlstrip? (2) is the observed behaviour of \xmlstripped (not expanding nodes below) as it should? As Hans Hagen mentioned before he would have I look into it, I kindly ask if he already has found time for this. Hans van der Meer

1 0