April 2016 - ntg-context - NTG Mailing Lists

font error with latest beta
by Thomas A. Schmitz 16 Apr '16

16 Apr '16

Hi Hans, I run into my favorite error with the latest beta ("this can't happen"). The document uses a SabonNext font, but I get similar results with other fonts. The error message is: tex error > tex error on line 855 in file /home/tas/context/tex/texmf-context/tex/context/base/mkiv/cont-yes.mkiv: ! This can't happen (fuzzy token cleanup in node) \page_shipouts_normal ...box \shipoutscratchbox }} \else \page_shipouts_ignor... \page_boxes_shipout ... {\box \shipoutscratchbox } \fi \setnextrealpageno \th... \page_otr_construct_and_shipout ...cted_page #1#2} \page_otr_flush_pending_co... \page_sides_output_routine_nop ...de_float_output \global \d_page_sides_vsiz... \page_sides_output_routine ..._output_routine_nop \fi \page_otr_triggered_output_routine ...and_routine \fi ... l.97 \getvalue{clf_processjob} % from cont-run.lua mtx-context | fatal error: return code: 1% An older context version (2016.02.08 15:35) processes the same file without problems, so I suspect it may be the newer luatex binary. I can't produce a minimal example right now, the error is a bit unpredictable. All best Thomas

2 1

Re: [NTG-context] Questions about Scite lexers
by Christoph Reller 14 Apr '16

14 Apr '16

Nicola <nvitacolonna(a)gmail.com> wrote on Wed., 13. Apr. 2016 19:36: > > I have found an old document of mine, which uses a > (slightly customized) pret-c.lua, located inside the project's folder. > It compiles, but I don't get syntax highlighting. Is it because pret-c > is not searched in the project's directory? > Alternatively you can set the TEXMF_LOCAL environment variable to some directory where your "private" texmf-tree resides. Note that after this you have to run context --generate in order for context to find the modules in your texmf-tree. Also note that the compilation logfile written by context tells you what modules have been found in which locations. I hope this helps, Christoph >

2 2

Assigning a variable to the list argument in \setupsection
by Michael Guravage 14 Apr '16

14 Apr '16

Greetings, I would like to use a variable for the value of the list argument in, e.g., the \startsection command. If you compile my little example you will see that the first 'literal' assignment works, while the second 'variable' assignment does not. What am I missing here? Cheers, Michael \starttext \placecontent \setvariables[TOC][list=Second Section] \startsection [title={First}, list={First Section}] This is the first section. \stopsection \startsection [title={Second}, list={\getvariable{TOC}{list}}] This is the \getvariable{TOC}{list} \stopsection \stoptext

3 2

contextjit missing from win32
by Pablo Rodriguez 14 Apr '16

14 Apr '16

Hans, I downloaded the latest beta from the ConTeXt Suite yesterday for win32 and win64. I’m afraid that contextjit isn’t available for win32. I guess it might be a bug. Many thanks for your help, Pablo -- http://www.ousia.tk

3 5

uppercase, small caps, numerals and German capital sharp s
by Thomas Fehige 14 Apr '16

14 Apr '16

Hello, I'm new to ConTeXt and this list. After a long time of using LaTeX and xeLaTeX I was finally lured into trying ConTexT by its ability of grid typesetting. Today's problem is a bit complex. In a book project I have several points where stuff is capitalized or turned into caps+smallcaps or pure smallcaps. My guess is that that should work either with \WORD{Stuff}, \Cap{Stuff} and \cap{Stuff} or with \uppercase, \sc, and {\sc\lowercase{Stuff}}. (Not quite, it seems) I'll use a commercial font called Calluna, but have added Linux Biolinum O to the example for those who don't want to download Calluna (the "Regular" can be "bought" for free, e.g. at https://www.fontspring.com/fonts/exljbris/calluna) Both Calluna and Biolinum contain the glyph "LATIN CAPITAL LETTER SHARP S" at "1E9E. I'm not sure if they contain a small or medium caps version. I'd like to use that glyph in the capitalizations mentioned, but it only works erratically (cf. example). Also, Calluna comes with oldstyle numerals switched on, which is nice for normal text, but should change to lining numbers in all-caps and to small-cap lining numbers in all-small-cap text. I'm not sure what I'll want in a caps+smallcaps context, but certainly not oldstyle numbers with their descenders. Any ideas? Thanks for reading! -- Thomas PS: I asked the same question on stackexchange, there's also an image of the result of my example: http://tex.stackexchange.com/questions/302823/context-uppercase-%C3%9F-cust… %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \mainlanguage[de] \language[de] \uccode`ß="1E9E % This gives the capital ß to \uppercase \definefontfeature[fcalluna][default][] % I tried all the font features built % into Calluna, to no avail. \definefontfamily [myfamily] [serif][Calluna][features=fcalluna] \definefontfamily [myfamily] [sans] [Linux Biolinum O][features=fcalluna] \definefontfamily [myfamily] [mono] [TeX Gyre Cursor] \setupbodyfont [myfamily] \startTEXpage[offset=10pt] \starttabulate[|l|l|l|] \NC \it Command \NC \it Calluna \NC \it Linux Biolinum \NC\NR \NC\type{\WORD{Gruß134}}: \NC\WORD{Gruß134} \NC {\ss\WORD{Gruß134}} \NC\NR \NC\type{\uppercase{Gruß134}}: \NC\uppercase{Gruß134} \NC{\ss\uppercase{Gruß134}} \NC\NR \NC\type{\sc{Gruß134}}: \NC{\sc Gruß134} \NC{\ss{\sc Gruß134}} \NC\NR \NC\type{\Cap{Gruß134}:} \NC\Cap{Gruß134} \NC{\ss \Cap{Gruß134}} \NC\NR \NC\type{\cap{Gruß134}:} \NC\cap{Gruß134} \NC{\ss \cap{Gruß134}} \NC\NR \NC\type{{\sc\lowercase{Gruß134}}:} \NC{\sc\lowercase{Gruß134}} \NC{\ss\sc\lowercase{Gruß134}} \NC\NR \stoptabulate \stopTEXpage %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

1 0

PageSetup
by Aidan Nichol 14 Apr '16

14 Apr '16

I’ve been have been having a couple of problems with swapping pages and so I went back to the example in Context Garden using the latest beta \definepapersize[main] [A4] \definepapersize[extra][A4,landscape] \setuppapersize[main] \starttext Page 1. Portrait \page Page 2. Portrait \page \adaptpapersize[extra] Page 3. Landscape \page Page 4. Portrait \page \stoptext The main problem I have is that \adaptpapersize is working as though I had entered \setuppapersize. Page 3 was created as landscape and but it didn’t revert to main to give page 4 as portrait. The secondary issue is that the landscape page is not as expected in that it is a square page. Inserting a \showsetups and \showframe into page 3 I can see that it is layed out Ok but on a large piece of paper. \printpaperwidth and \printpaperheight are both set to 29.7cm. Aidan

1 0

Assigning a variable to the list argument in \setupsection
by Michael Guravage 14 Apr '16

14 Apr '16

Greetings, I would like to use a variable for the value of the list argument in, e.g., the \startsection command. If you compile my little example you will see that the first 'literal' assignment works, while the second 'variable' assignment does not. What am I missing here? Cheers, Michael \starttext \placecontent \setvariables[TOC][list=Second Section] \startsection [title={First}, list={First Section}] This is the first section. \stopsection \startsection [title={Second}, list={\getvariable{TOC}{list}}] This is the \getvariable{TOC}{list} \stopsection \stoptext

1 0

RTL section heads
by Mohammad Hossein Bateni 14 Apr '16

14 Apr '16

Hi, This is concerning an RTL text. I have one chapter and 10 sections under that. My goal is to achieve the following. 1) The number 10 should appear correctly with '1' visually to the left of '0'. 2) The chapter number should visually appear to the right of the section number. 3) Chapter and section numbers should be separated with a dash. (This is ignored in this email and I will follow up about it in another thread. To get a minimal working example, I also do not try to change the numbers to use Persian digits.) In particular, the headings will be visually something like the following (aligned to the right). elpmas 1 txet 1-1 txet 2-1 txet 3-1 ... txet 10-1 Here's the first attempt. %% Attempt 1 \setupalign[r2l] \starttext \placecontent \chapter{sample} \dorecurse{10}{\section{text}} \stoptext The result is: elpmas 1 txet 1-1 ... txet 01-1 Then I add "\setupdirections[bidi=global,method=default]" to the beginning and I get the most strange result (number right-aligned but texts left-aligned): sample 1 text 1.1 ... text 1.10 A third attempt gives almost what I want (without period as the separator). %% Attempt 3 \setupalign[r2l] \def\LTR#1{{\lefttoright#1}} \def\leftnumbers#1{\LTR{\numbers{#1}}} \defineconversion[leftnumbers][\leftnumbers] \setuphead[chapter,title,section,subject] [conversion=leftnumbers] \starttext \placecontent \chapter{sample} \dorecurse{10}{\section{text}} \stoptext The big problem is that in my RTL documents, I always have the setupdirections command, which messes things up here. (This makes it difficult to one section name with English title, which should still be typeset on the right-hand side of the page.) Note that in attempt 2 above, there were two issues: (1) Text and numbers appeared on the two far ends of the screen instead of being close to each other. This does not happen when I use Farsi text. (2) Chapter number appears to the left of section number. %% Attempt 5 \usemodule[simplefonts] \setmainfont[ALM Fixed][features=arabic,range=arabic] \setupdirections[bidi=global,method=default] \setupalign[r2l] \starttext \placecontent \chapter{نمونه} \dorecurse{10}{\section{متن}} \stoptext Interestingly the table of contents looks fine if I put the number inside an LTR macro; still in the main body, the section heads are typeset incorrectly. %% Attempt 6 \usemodule[simplefonts] \setmainfont[ALM Fixed][features=arabic,range=arabic] \setupdirections[bidi=global,method=default] \setupalign[r2l] \def\LTR#1{{\lefttoright#1}} \def\leftnumbers#1{\LTR{\numbers{#1}}} \defineconversion[leftnumbers][\leftnumbers] \setuphead[chapter,title,section,subject] [conversion=leftnumbers] \starttext \placecontent \chapter{نمونه} \dorecurse{10}{\section{متن}} \stoptext I guess the solution is to get the entire section head number string (e.g., 1.10) to have RTL direction, however, each individual number string inside (say, 1 or 10) should be written LTR. How can this be achieved? The six TeX files (with corresponding PDF outputs) are attached. BTW this is using ConTeXt ver: 2016.04.01 13:01 MKIV beta fmt: 2016.4.7 int: english/english, running LuaTeX, Version beta-0.90.0 (TeX Live 2016) on Mac OS X. Thanks a lot, —MHB

4 12

How to embed formatting commands into the syntax highlight code generated by scite module?
by Li Yanrui (李延瑞) 14 Apr '16

14 Apr '16

Hi, i want to embed some formatting commands into code highlighted with scite or vim module, but i do not find its option like "escape=yes". Is there a way to do it? -- Best regards, Li Yanrui (李延瑞)

2 2

Questions about Scite lexers
by Nicola 13 Apr '16

13 Apr '16

I'm trying to define a custom scite lexer for a toy language I'm using. So far, I've copied a lexer from the distribution, changed its name and keywords, and it's all fine. I have a few questions, though: 1) my custom scite-context-lexer-xxxx.lua is found only if I put it in the distribution. It there a way to have it in my project's folder instead? 2) How do I customize colors? 3) Is it possible to embed TeX commands in \startscite..\stopscite environments, like /BTEX../ETEX in built-in typing? 4) Are scite lexers documented somewhere besides the source code? 5) May I rely on this feature to be stable? 6) It is my understanding that pret-xxx.lua files are obsolete. Is it correct? (If so, it would be nice to update the wiki to reflect that). To be clear, I'm not interested in using the Scite application. I just need to typeset formatted verbatim code. The vim module is fantastic and I already use it, but there are cases where I need a syntax not supported by Vim (and I'd rather avoid defining it on the Vim side) and/or need to embed TeX commands (anywhere, not only in comments). Nicola

4 4