- ntg-context - Mailing Lists

Bug in command \framed
by Jannik Voges 13 Jan '16

13 Jan '16

Hello, it seems that the command \framed in the newest beta (from today?) is buggy. Minimal example: \starttext \framed{bla} \stoptext Best wishes Jannik

4 4

\startalignment
by Alan BRASLAU 12 Jan '16

12 Jan '16

Hello, Jean-Michel pointed out to me the following curiosity: \starttext \input tufte \startalignment[middle] \input ward \stopalignment \input tufte \stoptext The startalignment applies to the preceding text, too. Strange... I never noticed this before as I have the habit of coding \startalignment\stopalignment blocks set-off with leading and trailing blank lines for better readability. But such practice could lead to undesired results. Consider the following example: \setupwhitespace [big] \starttext \input tufte \startalignment[middle] \input ward \stopalignment \input dawkins \stoptext So \stopalignment implicitly imposes a \par. If I were to omit the blank line before \startalignment so that no big whitespace be included before the centered block, the tufte text will get middle aligned. Also, perhaps I might not wish for the dawkins text to be separated by a big whitespace, logically as in: \startparagraph \input tufte \startalignment [middle] \input ward \stopalignment \input dawkins \stopparagraph Indeed, curious behavior. Alan

3 4

suddenly run error
by dr. Hans van der Meer 12 Jan '16

12 Jan '16

A document that runs fine under ConTeXt ver: 2015.10.09 21:28 MKIV beta fmt: 2015.10.11 int: english/english suddenly doesn't under ConTeXt ver: 2015.12.22 10:50 MKIV beta fmt: 2015.12.27 int: english/english mtx-context | fatal error: no return code, message: luatex: execution interrupted Loaded this beta today. The previous beta runs ok, the new beta gives the error. The pdf produced in the latter seems at fault. Anyone knows how this error can occur?

3 4

context zip files
by Hans Hagen 12 Jan '16

12 Jan '16

Hi, Due to a change in the structure: if you install / update context from the zip file make sure you first wipe you old tex/context and metapost/context paths. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

1 0

font scaling does not work in footnotes
by massifr＠fastwebnet.it 12 Jan '16

12 Jan '16

Hello list, I have a problem with font scaling (see "sc=SansCaps sa 1.5" below). I'm using MyriadPro as sans font, but it lacks small caps. So I decided to provide them using AlegreyaSansSC, because it's similar to MyriadPro and it's made of small caps only. When I use \ss and \sc I get AlegreyaSC instead of MyriadPro. I want to scale them differently to balance their weights. That's why I wrote "sc=SansCaps sa 0.95". In body text the two fonts are balanced, but in the footnotes the scaling is ignored. What am I missing? Here's (part of) the typescript: \starttypescript [sans] [meo] \definefontsynonym [Sans] [name:MyriadPro-Regular][features=meo,fallbacks=mancanti] \definefontsynonym [SansBold] [name:MyriadPro-Bold][features=meo,fallbacks=mancanti] \definefontsynonym [SansItalic] [name:MyriadPro-It][features=meo,fallbacks=mancanti] % ... \definefontsynonym [SansCaps] [name:AlegreyaSansSC-Medium][features=meo,smcp,fallbacks=mancanti] \definebodyfont [13pt,11pt,10pt,8pt,7pt,6pt] [ss] [tf=Sans sa 0.85, it=SansItalic sa 0.85, bf=SansBold sa 0.85, bi=SansBoldItalic sa 0.85, sl=SansSlanted sa 0.85, sc=SansCaps sa 0.95] \stoptypescript Thank you, Massi

1 0

Is there anybody from Vienna, Austria?
by Ursula Hermann 12 Jan '16

12 Jan '16

Hallo everybody! Is there anybody from Vienna, Austria, in this mailinglist? Would like to know, if anybody wants a contact.!! If this ist the wrong Mailinglist, please tell me the right adress, for this message. Thanks Uschi

1 0

disabling ligatures in selected words
by Thomas A. Schmitz 12 Jan '16

12 Jan '16

Hi, in German typography, ligatures are disabled at boundaries between what used to be independent words (Wortfugen). Thusly, in a correct German text, you'd find Anflug (with fl-ligature) but Auf|lage (without ligature). I know that I can prevent a ligature with something like Auf\/lage or even Auf|*|lage. However, I typeset from xml and would much rather have a general solution so I can leave my generated xml files alone. Something like a list where I could list "ligature exceptions" the way we have a file with hyphenation exceptions. Is anything like this possible? Thanks Thomas

4 4

file not found
by Meer, Hans van der 12 Jan '16

12 Jan '16

The code below did work ok some version of ConTeXt ago, now an error and I cannot think of the cause. There is an unknown file ./t. Is it origin something with the jobname mysteriously being t? Or is it perhaps that modules now have names preceded by t- ? I am completely baffled. Help would be very much appreciated because I have not much time left to finish the text. Macro for calling a context run: % Call context for figures #1 = mode, #2 = fontchoice, #3 = colorchoice, #4 = file without .tex extension. \def\callcontext[#1][#2][#3]#4{% \writestatus{HVDM}{CALLING DIRECTLUA file=#4 mode=#1 fontchoice=#2}% \directlua{os.execute("cd \FigSrc;context --once --mode=#1 --font=#2 --colors=#3 --purge #4;rm #4.tuc;cd -;mv \FigSrc/#4.pdf \FigDir")}% } HVDM > CALLING DIRECTLUA file=taalengels mode=screen,info fontchoice=lucidaot,sans,12pt\tt resolvers | trees | analyzing '/Users/hansm/Documents/TeX/texmf' mtx-context | warning: no (local) file './t', proceeding mtx-context | run 1: luatex --fmt="/Users/hansm/Applications/TeX/context-28/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en" --jobname="t" --lua="/Users/hansm/Applications/TeX/context-28/tex/texmf-cache/luatex-cache/context/5fe67e0bfe781ce0dde776fb1556f32e/formats/luatex/cont-en.lui" --no-parse-first-line --c:colors="darkslategray,darkslategray,mistyrose,darklavenderblush,peachpuff" --c:currentrun=1 --c:font="lucidaot,sans,12pt" --c:fulljobname="./t" --c:input="./t" --c:kindofrun=3 --c:maxnofruns=1 --c:mode="screen,info" --c:once --c:purge "cont-yes.mkiv" This is LuaTeX, Version beta-0.80.0 (TeX Live 2015) (rev 5238) \write18 enabled. resolvers > trees > analyzing '/Users/hansm/Documents/TeX/texmf' system > callbacks > not registering frozen 'find_format_file' open source > 1 > 1 > /Users/hansm/Applications/TeX/context-28/tex/texmf-context/tex/context/base/cont-yes.mkiv ConTeXt ver: 2015.10.09 21:28 MKIV beta fmt: 2015.10.11 int: english/english system > 'cont-new.mkiv' loaded open source > 2 > 2 > /Users/hansm/Applications/TeX/context-28/tex/texmf-context/tex/context/base/cont-new.mkiv close source > 2 > 2 > /Users/hansm/Applications/TeX/context-28/tex/texmf-context/tex/context/base/cont-new.mkiv system > files > jobname 't', input './t', result 't' fonts > latin modern fonts are not preloaded languages > language 'en' is active tex error > tex error on line 8 in file /Users/hansm/Applications/TeX/context-28/tex/texmf-context/tex/context/base/cont-yes.mkiv: ! I can't find file `./t'. Hans van der Meer

1 0

ConTeXt on ARM architecture raspberry pi
by Jan U. Hasecke 12 Jan '16

12 Jan '16

Hi, has anyone installed ConTeXt on a Raspberry Pi? juh -- Das ZEN von Pandoc Bücher und E-Books einfach und professionell produzieren http://www.amazon.de/Das-ZEN-von-Pandoc-professionell/dp/1505218799/ Paperback (232 Seiten) und E-Book

3 3

Paragraph breaking bug with BiDi text
by Mohammad Hossein Bateni 11 Jan '16

11 Jan '16

Hello, When a line ends with a sequence whose direction differs from that of the paragraph, we risk pushing some text into the margin (when not necessary). Here is an example with corresponding output: \usemodule[simplefonts] \setmainfont[ALM Fixed][features=arabic,range=arabic] \setupalign[r2l] \setupwhitespace[big] \showframe \starttext % 10 copies of Persian word "hello" stay on one line. \dorecurse{10}{سلام } % 20 copies makes a 2-line paragraph. \dorecurse{20}{سلام } % one copy of the word goes into the margin although the Latin letters perfectly fit the line. \dorecurse{10}{سلام } {\textdir TLT\dorecurse{20}{a}} \dorecurse{10}{سلام } % although the Latin string extends into the margin, TeX still puts one copy of "hello" there as well. \dorecurse{10}{سلام } {\textdir TLT\dorecurse{30}{a}} \dorecurse{10}{سلام } % something similar happens here with the opposite par/text dir \pardir TLT \dorecurse{10}{bidi } {\textdir TRT\dorecurse{20}{آ}} \dorecurse{10}{bidi } \stoptext The problem seems to be that after typesetting the LTR text within the RTL paragraph, TeX thinks the current text ends at the left end of the LTR portion; hence, it tries to add something to the line; it's only after that that it discovers we ran into the margin! —MHB

3 5