- ntg-context - NTG Mailing Lists

Re: [NTG-context] [***SPAM***] Provide showgrid as a PDF layer
by Hans Hagen 30 Nov '13

30 Nov '13

On 11/30/2013 12:04 AM, Jan Tosovsky wrote: > Dear All, > > it would be nice to have a possibility to interactively disable/enable a > grid rendered via \showgrid command. Whereas this grid is helpful for > debugging, it disturbs when the page is evaluated as the whole. Using layers > could make this process more efficient (not requiring to generate both > variants). > > I've noticed something like this is already implemented for the body area > (visualizer vbox layer). > > Or is there any option for this already? \setupinteraction[state=start] \showgrid \showframe \showmakeup \showlayoutcomponents \starttext \input tufte \placefigure{}{} \stoptext but you need a viewer that supports layers (can turn them on and off) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 1

[***SPAM***] Provide showgrid as a PDF layer
by Jan Tosovsky 29 Nov '13

29 Nov '13

Dear All, it would be nice to have a possibility to interactively disable/enable a grid rendered via \showgrid command. Whereas this grid is helpful for debugging, it disturbs when the page is evaluated as the whole. Using layers could make this process more efficient (not requiring to generate both variants). I've noticed something like this is already implemented for the body area (visualizer vbox layer). Or is there any option for this already? Thanks, Jan

1 0

Re: [NTG-context] Eliminating orpans in the Index
by Hans Hagen 29 Nov '13

29 Nov '13

On 11/26/2013 10:09 PM, Jan Tosovsky wrote: > On 2013-11-23 Jan Tosovsky wrote: >> >> in my two-column index there are several cases when the last >> entry in the given letter group overflows to the next column/page. >> In the extreme case it is just the last page reference. >> ... >> Additionaly, columns are not balanced properly in all cases. When the >> first is longer, it is not a big problem. But the opposite case >> looks weird. > > As the registers are rendered programatically, I cannot intervene into this > process. But can I influence it e.g. using 'processors' applied to > problematic index entries? > > Processors can be used for setting the font-weight or color of particular > entry. Can the same method used for manual setting of > 'keep-with-previous/next' ? I can think of a hack but it will always be for last minute work. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 1

bibliography - maybeyear
by Alan Braslau 29 Nov '13

29 Nov '13

Hello, Using \setuppublications [alternative=num] for example, should not append letters to the publication years when encountering multiple publications by the same author(s) per year. So, in the use of bibliographies, I have not understood how to control \maybeyear. In the bibl-xxx.tex files, it is defined as \def\maybeyear#1{#1} or \def\maybeyear#1{} as needed. Perhaps this is for mkii. In bibl-bib.mkiv, one has \appendtoks \doifelse{\bibtexpublicationsparameter\c!maybeyear}\v!off {\let\maybeyear\gobbleoneargument} {\let\maybeyear\firstofoneargument}% \to \everysetupbibtexlistplacement which seems to then use the keyword maybeyear. I guess that \setupbibtexpublications [maybeyear=off] in my source would turn off the appended letters, but this is not correct. I have tried many variants (\setuppublications, \setupbibtex). What am I misunderstanding? Or is this a bug? Alan

3 5

Re: [NTG-context] Palatino patch for the current ConTeXt version
by Hans Hagen 29 Nov '13

29 Nov '13

On 11/27/2013 9:16 PM, Jan Tosovsky wrote: > On 2013-11-27 Hans Hagen wrote: >> On 11/27/2013 12:40 AM, Jan Tosovsky wrote: >>> On 2013-11-17 Hans Hagen wrote: >>>> On 11/17/2013 12:23 PM, honyk wrote: >>>>> Hello Everyone, >>>>> >>>>> I am trying to fix a Palatino small caps issue using the procedure >>>>> explained here: >>>>> http://wiki.contextgarden.net/Palatino_Linotype_under_MKIV >>>>> >>>>> That fix seems to be obsolete nowadays and returning errors. >>>>> >>>> >>>> there are several ways to apply patches runtime, see *.lfg files >>>> (and also fonts-mkiv.pdf) >>> >>> 1) I've created a sample LFG file >>> 2) placed it into the folder where other LFG files are stored >>> 3) removed pala.tma and pala.tmc files from the cache >>> 4) triggered the generating >>> >>> My pala.lfg file seems to be ignored: >>> >>> return { >>> name = "pala", >>> comment = "Switching the small capped 'i' to a dotless variant >>> in Palatino Linotype.", >>> remapping = { >>> tounicode = true, >>> unicodes = { >>> ["i.sc"] = 983201, >>> }, >>> }, >>> } >> >> you have to load them ... see fonts-mkiv.pdf > > Thanks, I got it. Two next steps are required and one turned out as > redundant. > > 1) Create a sample LFG file > 2) Place it into the folder where other LFG files are stored > 3) NEW! Execute 'mtxrun --generate' command to include newly added LFG file > into a file database > 4) NEW! Specify a new font feature referencing to this goodie: > \definefontfeature[dotlessi][mode=base,goodies=pala,unicoding=yes] > \definefontfamily[mainface][rm][Palatino > Linotype][features={default,quality,dotlessi}] > 5) Trigger the generating > > It does something, but not what I need :-) > > My MWE: > \definefontfeature[dotlessi][mode=base,goodies=pala,unicoding=yes] > \definefontfamily[palatino][rm][Palatino > Linotype][features={default,quality,dotlessi}] > \setupbodyfont[palatino] > \starttext > Athenians \sc{Athenians} > \stoptext > > This LFG core settings: > unicodes = { > ["a.sc"] = 97, (1) > ["b.sc"] = 983261, (2) > }, > > (1) replaces all small 'a' into small caps variants - just for testing > purposes > (2) doesn't replace small caps 'i' to small caps 'b', but when small caps > text is selected, b is copied into the clipboard - so some replacement is > performed, but incomplete. > > Maybe other tables need to be tweaked as well... > Has anybody any experience with this? this mechanism assumes that the shapes match the one that unicode expects so the (default) tounicode is used ... originally this features was meant for fonts with a faulty mapping (some dingbat fonts have that) Hans -- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 1

sagemath in context (like sagetex)
by Xan 29 Nov '13

29 Nov '13

Hi, Is there any kind of package for embedded sagemath in ConTeXt (like sagetex in latex). I found the same question previosly asked (http://www.ntg.nl/pipermail/ntg-context/2009/040483.html) but more things are changed until 2009... so perhaps there is now a solution By the other hand, I see lua lunatic code: http://wiki.contextgarden.net/User:Luigi.scarso/luatex_lunatic#SageMath but this is very programmer centric code, in my opinion. Is there any easy way to do that? I use MKIV Thanks, Xan.

1 0

Unexpected behaviour of enumeration in mkiv
by Thomas Möbius 28 Nov '13

28 Nov '13

Hi, please have a look at the minimal example at the bottom. I am typesetting theorems and lemmata which are numbered consecutively within chapters in a book. I used the same code for a document written in mkii, and I thought I could just reuse it in mkiv. Obviously, there is something I am missing. Question: How do I get the same output when compiling the following code with 'context' as when compiled with 'texexec'. When compiled with 'context', the chapter number is missing in the numbering of theorems. Lemmas are not numbered at all. ~~~snip~~~ \setupenumerations [title=yes, style=normal, list=all, before={\blank[big]}, after={\blank[big]}, location=serried, width=broad, distance=0.5em, headstyle=bold, titlestyle=bold, way=bychapter, conversion=numbers] \defineenumeration [theorem] [text=Theorem, listtext={Theorem }] \defineenumeration [lemma] [text=Lemma, listtext={Lemma }, number=theorem] \starttext \chapter{First chapter} \theorem Hello \theorem Hello \lemma Hello \theorem Hello \stoptext ~~~snip~~~

2 3

Line numbers and tabulate cells in Mark IV
by Adam Khan 28 Nov '13

28 Nov '13

The lines of a tabulate cell may be numbered with code like the following under Mark II, but not under Mark IV. \starttabulate[|p|p|] \NC \input knuth \NC \startlinenumbering \input knuth \stoplinenumbering \NC\NR \stoptabulate How may the lines of a tabulate cell be numbered under Mark IV? Sincerely yours, Adam Khan

2 2

Re: [NTG-context] [***SPAM***] Incorrect internal font processing
by Hans Hagen 28 Nov '13

28 Nov '13

On 11/27/2013 11:35 PM, Jan Tosovsky wrote: > On 2013-11-27 Jan Tosovsky wrote: >> On 2013-11-27 Hans Hagen wrote: >>> On 11/27/2013 10:20 PM, Jan Tosovsky wrote: >>>> On 2013-11-27 Hans Hagen wrote: >>>>> On 11/27/2013 9:53 PM, Jan Tosovsky wrote: >>>>>> On 2013-11-27 Hans Hagen wrote: >>>>>>> On 11/27/2013 8:44 PM, Jan Tosovsky wrote: >>>>>>>> >>>>>>>> during my attempts to patch the Palatino's dotless 'i' I found >>>>>>>> that this font is parsed incorrectly by ConTeXt. >>>>>>>> >>>>>>>> Comparing index/name info of individual glyphs in the font >>>>>>>> software and resulting pala.tma file there is the following >>>>>>>> difference: >>>>>>>> >>>>>>>> Index | Name - font | Name - tma >>>>>>>> 1110 | dotlessi.smcp | i.sc (1) >>>>>>>> 1170 | i.smcp | i.sc (2) >>>>>>>> >>>>>>>> The first one should have IMHO a different name. >>>>>>>> The same name for two glyphs might be dangerous. >>>>>>> >>> >>> the fact that there are two i.sc in the font is suspicious ... best >>> check the font in fontforge ... one never know what kind of things >>> other programs do >> >> Hmm, FontForge glyphs naming corresponds to what we can observe in the >> ConTeXt (doubled i.sc). My previous analysis was based on FontLab. I am >> confused now... > > Actually, there are no names of these glyphs available in the font so they > are calculated(!) > Each of two programs uses a different method. FontLab method is based on > layout tables - GPOS, GSUB, GDEF (it somehow detects that both glyps that is okay to make names unique, although there can still be multiple variants so in fact i.smcp and i.ss01.4 are valid names then, but .smcp and .onum are not understood by name parsers (for adobe glyph names) > differs). The FontForge method is unclear and seems to be buggy. But we some kind of numbering would make more sense i.1 or so > should blame rather the font itself as it is the primary cause of these > problems (= missing glyph names). indeed Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

1 0

Multi-letter variables in math mode
by Thaddäus Töppen 27 Nov '13

27 Nov '13

Hi. Sometimes I use variables (really rather abbreviations) in math formulas. It seems to me that the letterspacing is a bit too wide then. Maybe math mode thinks I want to multiply the letters as if they were variables for themselves. Is there a way to preserve normal letterspacing locally in a formula? Kind regards.

2 1