- ntg-context - NTG Mailing Lists

Blank lines and \noindent
by Martin Althoff 06 Aug '10

06 Aug '10

Just curious about the intented behaviour of \noindent. If I place it as shown in the example, the next paragraph will still be indented. However, if the blank line between \noindent and the following text is deleted or contains a comment, the following text will not be indented. Is this placement dependency intended? I thought I could use blank lines at liberty to "style" the sources. Secondly, is there any way of integrating the \noindent into the \textrule. Means: the paragraph following a textrule should not be indented. Not crucial, but would reduce the clutter in the sources. There are about 600 textrules... Not pretty, I know, but currently they are my indicator, that a page in the original book, from which the text comes, has changed. Thanks again, Martin \setupindenting[yes,small] \indenting[next] \starttext \input{davis} % page 86 Old page header \textrule[top]{Change of Page} \noindent \input{davis} \stoptext

4 7

completelistofunits and completelistofabbreviations in MkIV
by Vedran Miletić 06 Aug '10

06 Aug '10

Are completelistofunits and completelistofabbreviations supposed to be with an empty title in MkIV? Consider this: \usemodule[units] \starttext \completelistofunits \chapter{Something} 1 \Meter. \stoptext List of tables and List of figures work normally. Regards, -- Vedran Miletić

2 2

metapost and lua
by Philipp Gesang 06 Aug '10

06 Aug '10

Hi all! [1] Is there a Lua interface for metapost? I'm thinking of something like cld is for TeX here. All I figured out so far is how to generate mp code (as strings) in Lua and then having it processed by mplib, but as the metafun manual is from 2002 and with context you never know how far it is ahead of your dreams … [1a] If not [1], then: will there ever be something like this? [2] There's an example for “metapost.process()” in mlib-ctx.mkiv but I can't get it to work. I simply copypasted it as follows: ···8<·········································································· \starttext \startluacode mpgraphic = [[ for i=1 upto 1000 : beginfig(0); draw halfcircle scaled 1cm withcolor green ; picture p ; p := "oeps" infont defaultfont scaled .75 rotated 45 ; p := p shifted - (xpart center p,0) ; draw p ; draw boundingbox p ; endfig ; beginfig(0); draw halfcircle scaled 1cm dashed evenly withcolor green ; endfig ; beginfig(0); pickup pencircle xscaled .5mm yscaled .25mm rotated 45 ; draw halfcircle scaled 1cm withcolor red ; endfig ; beginfig(0); draw halfcircle scaled 1cm ; endfig ; beginfig(0); pickup pencircle xscaled .5mm yscaled .25mm rotated 45 ; for k:=1 upto 10 : draw halfcircle scaled uniformdeviate(1cm) withcolor (red/(k/4)) ; endfor ; endfig ; endfor ; ]] metapost.process(metapost.format("metafun"),mpgraphic) \stopluacode \stoptext ···8<·········································································· This fails in mlib-run.lua at line 324. (Same with all my other tries, but I assume code from the context sources has a much higher probability of being valid.) Do I miss something critical? Thanks for your help, Philipp -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments

2 5

Palatino Linotype under MKIV
by Paul Schalck 06 Aug '10

06 Aug '10

Hi, I'm trying to use the full glyph range of the Palatino Linotype font shipped with XP (version 1.40; significantly different from the Windows 7 one) under MKIV. Everything works fine (oldstyle figures, sups for instance), except that the small cap "i" character has a dot whereas it shouldn't. Here's a test file. The result, produced on WinXP / ConTeXt beta 2010-06-23, is attached. \definefontfeature[palatinolt-default][script=latn,kern=yes,liga=yes,trep=yes,tlig=yes,protrusion=quality] \definefontfeature[palatinolt-smcp][script=latn,kern=yes,liga=yes,trep=yes,tlig=yes,protrusion=quality,smcp=yes,onum=yes] \definefontfeature[palatinolt-sups][mode=node,script=latn,kern=yes,liga=yes,trep=yes,tlig=yes,protrusion=quality,sups=yes] \starttypescript[serif][palatinolt][name] \usetypescript[serif][fallback] \definefontsynonym[Serif][file:pala.ttf][features=palatinolt-default] \definefontsynonym[SerifBold][file:palab.ttf][features=palatinolt-default] \definefontsynonym[SerifItalic][file:palai.ttf][features=palatinolt-default] \definefontsynonym[SerifBoldItalic][file:palabi.ttf][features=palatinolt-default] \definefontsynonym[SerifCaps][file:pala.ttf][features=palatinolt-smcp] \stoptypescript \definetypeface[palatinolt][rm][serif][palatinolt][default] \setupbodyfont[palatinolt] \enableprotruding\setuppagenumbering[location=] \starttext {\sc \input knuth } \stoptext As far as I can see, it has to do with the messy name list of the glyphs. Both the normal small cap i and the small cap dotted i are named "i.sc", but the wrong one is picked when the smcp feature is activated. Moreover, the small cap glyphs have no unicode numbers in this font, so I cannot pick them manually with \char"XXXX or even with \charXXXXX. Any ideas how I can get the right dottless i?

5 10

new beta
by Hans Hagen 05 Aug '10

05 Aug '10

Hi, I uploaded a beta. Peter Rolf and I have spent quite some time on pdfx related issues (mostly trying to figure out the right specs and how to deal with them). We started with a command driven interface but eventually it ended up with a single command: \setupbackend [format=PDF/X-3:2002, intent=sRGB] Lookups are case insensitive. The intent can be a comma separated list of profiles. The name is resolved using colo-icc.xml (or color-icc.lua) but one can also pass a (list of) files using the 'file' key. You can check handling with: \enabletrackers[backend.pdfx] When choosing a format, color spaces, transparency and layers are automatically disabled in the backend code but they do function in the frontend. Of course included images are the user's responsibility but color etc in MP graphics should work out ok. There are probably rough edges. 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 -----------------------------------------------------------------

3 2

font catalogue (re)
by R. Bastian 05 Aug '10

05 Aug '10

Hello, it is not a list of available fonts i need, but a catalogue where one can see the typefaces. In the Minimal directory there are 91 tfm files, 309 pfb files and 2043 thm files. Chap 31 'Fonts and font switches' of ".. an excursion" or Sect 5.1.1 in '...the 'Manual' gives no example hwo to go from a tfm fil (say "tcxr.tfm") to a usable font. A possible test file of typefaces could be (for my use "specimen.tex"): """ azertyu ... AZERTY ... äëÿuüïö ... âêûîô ... ÂÊÛÎÔ ... ÄËŸÜ ... &"'(-è_çà) """ and the font file for making a PDF: %%%%% how to go from TFM to 'normal' %%%%% \starttext \input specimen \stoptext I hope this can help beginners. -- René Bastian www.pythoneon.org www.musiques-rb.org http://www.soundsurvey.org.uk/

2 2

comments, font catalogue
by R. Bastian 05 Aug '10

05 Aug '10

Hello, 1. is there the same in Context than the Latexian \begin{comment} ... \end{comment} --------------------------- 2. In the Minimal tree there are many .afm, .tfm and other font files. Is there a sort of font catalogue (visualization of the fonts) ? The source of such a catalogue would be a good example for beginners - like me. -- René Bastian www.pythoneon.org www.musiques-rb.org http://www.soundsurvey.org.uk/

6 9

vbox construct breaking MKII
by Willi Egger 04 Aug '10

04 Aug '10

Hi all, Any variation of the following construct breaks in MKII as long as there is no new line after the closing } of the vbox. MKIV does not have this problem. \startbuffer[bf4] \vbox{ test }\stopbuffer Please refer to the testfile Kind regards Willi

3 7

Verbatim line numbering: location intext/text, empty lines, wrapped lines
by Stefan Müller 04 Aug '10

04 Aug '10

Hi, I found some issues with verbatim line numbering in MkIV. The appended examples is basically taken from the wiki. http://wiki.contextgarden.net/Verbatim_text#Line_numbering (The wiki uses MkII?) When I want the line numbers to be displayed "intext", I have to use \setuplinenumbering[location=text], although http://wiki.contextgarden.net/Verbatim_text#Line_numbering and http://wiki.contextgarden.net/Reference/en/setuplinenumbering tell me to use "location=intext". Should this be changed in the wiki? In case of "location=text" the lines are typeset over the right margin of the box. I think this is because the space used by the numbers is not subtracted from the available space considered by the word-wrapping algorithm. In the example, line 2 is wrapped over three lines and gets 3 line numbers, while IMHO it only should get one (the wiki says the same). Line 4 gets a number, which is what I would expect, but it is a different behavior as in the wiki (there, the empty line in the example gets no number). Is there an option to choose whether a blank line should be (a) numbered, (b) skipped or (c) get no number but the internal counter is still increased? Example: \starttext \defineframedtext[framedcode][strut=yes, offset=2mm, width=7cm, align=right] \definetyping[code][numbering=line, before={\startframedcode}, after={\stopframedcode}] \setuplinenumbering[location=text] \startcode This is the first line % line 1 This is a rather long line that is wrapped, so look how the line numbering is done % line 2 Another line % line 3 % line 4 Last line after an empty line % line 5 \stopcode \stoptext Thank you in advance for any hints, Stefan.

3 2

module for articles for the Context meeting ?
by luigi scarso 04 Aug '10

04 Aug '10

Is there a module to use for the articles for context meeting ? -- luigi

2 1