June 2007 - ntg-context - NTG Mailing Lists

metafun/label: utf8 and spaces
by Patrick Gundlach 02 Jul '07

02 Jul '07

Hi, is there any way to get utf-8 labels and without the 'strange' space glyph? -------------------------------------------------- \startMPenvironment[+] \enableregime[utf] \stopMPenvironment \starttext foobar baz äöß % <-- OK \startuniqueMPgraphic{bla} label("foobar baz äöß",(3cm,3cm)); % <-- broken draw btex foobar baz äöß etex % <--- OK \stopuniqueMPgraphic \useMPgraphic{bla} \stoptext -------------------------------------------------- Patrick

3 4

frames and hyphenation
by Hans van der Meer 02 Jul '07

02 Jul '07

I encountered some strange thing with framedtext's in trying to define one where hyphenation is suppressed. The definition is: \defineframedtext[myblock][frame=off,style=\tt,width=0.8 \makeupwidth,before=\nohyphens] But then \startmyblock text \stopmyblock does not stop hyphenation. While \startmyblock\nohyphens text \stopmyblock stops it. Since I would like to have the myblock's all having suppressed hyphenation I am at a loss how to do it. Could it be that the \nohyphens in the "before" is overriden by something? It looks like, because setting lefthyphenmin and righthyphenmin zero at that point did not work either. By the way it is a bit difficult to give an exact example, because hyphenation so much depends on ones linesize and font dimensions. Hans van der Meer

3 3

columns/blank=
by Patrick Gundlach 01 Jul '07

01 Jul '07

Hi, what is the rationale behind \setupblank[\@@klblank]% \ifdim\ctxparskip>\zeropoint\relax \setupwhitespace[\@@klblank]% \fi in page-mul.tex (columns)? It seems to me that blank=line inside a startcolumn does not work if ctxparskip = 0pt, which is the default. So when I'd like to have setupwhitespace[line] to get paragraphs separated by blank lines inside a column, I have to do this some other way?!? Patrick

2 2

chapter names in header
by Patrick Gundlach 01 Jul '07

01 Jul '07

Hi, what is wrong with -------------------------------------------------- \setuppagenumbering[location=] \starttext \setupheadertexts[text][section][chapter] \dorecurse{8}{\chapter{chapter - \recurselevel} \input tufte \dorecurse{8}{\section {section - \recurselevel} \input knuth \input knuth } } \stoptext -------------------------------------------------- ?? The header looks strange - example: on page four I'd expect 'section 4' and 'chapter 1' in the head. Patrick

3 4

white around descriptions
by Hans van der Meer 30 Jun '07

30 Jun '07

I find a get a lot of whitespace around my defined descriptions. Setting \setupdescriptions[\c!before=,\c!inbetween=,\c!after=] does not much help. Is there something else that can be done. Preferably without resorting to wild guesses like "before=\godown[-10pt]" or the like. Or is there something else I fail to see. A sample of the code involved(don't mind the \@@exm.. parameters, they are defined elsewhere, annotationtext is a token register): \definedescription[annotationblock][margin=no,location=top,width=broad,% before=,inbetween=,after=\strut,% headstyle=\@@exmintrostyle,style=\@@exmstyle,% text=\placeannotationstart] \def\annotation#1\par{\global\annotationtext={#1}}% \long\def\startannotation#1\stopannotation{\global\annotationtext={#1}}% %....................................................................... % placing the annotation indicator in the annotationblock description \def\placeannotationstart{% no white above and below rule \vboxinsideframedtext{% \setuptextrules[style=\@@exmintrostyle]% \textrule{\WWord{\Note}}}} Hans van der Meer

1 0

Wrong SRA3 papersize ?
by luigi scarso 30 Jun '07

30 Jun '07

In page-lay.tex \definepapersize [SRA3] [\c!width=320mm,\c!height=450mm] maybe is wrong. It should be \definepapersize [SRA3] [\c!width=450mm,\c!height=320mm] See http://www.theearthpaper.net/paper-sizes.html but need a confirm -- luigi ---------------------------------------------------------------- If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context(a)ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net

6 9

inmargin
by Hans van der Meer 29 Jun '07

29 Jun '07

I was thinking that things placed in the margin (\inmargin,\inright, \inleft) would not take up vertical space, but it seems to do just that inside an itemize. Example: \starttext \textwidth=4cm \hairline %(1) \startitemize[n,joinedup] \item abc \item cde \stopitemize \hairline %(2) % This seems to me the logical place for the remark. \startitemize[n,joinedup] \inright{pqr} % < squeezing spaces does not help \item abc \item cde \stopitemize \hairline %(3) \startitemize[n,joinedup] % But it has to be placed here to get the result wanted. \item abc \inright{pqr} \item cde \stopitemize \hairline \stoptext I wanted a remark in the right margin logically applying to the itemize as a whole. Placing it as in (2) looked the right way, but then the next item is placed lower on the page. That becomes a problem when a nested itemize is put there resulting in an empty line at the first itemmarker. Placing the \inright on the first item of the inner itemize seems an illogical place to me. It is, of course, not really problem because trial (3) shows how to avoid this. Still the question remains if there is some misbehaviour here in either the code for \inright or for \itemize? Therefore I am pointing this out just in case it might reveal a more or less subtle bug too more wiser ConTeXt-brains then mine. Hans van der Meer

1 0

Labels in figures with wrong bounding box
by nicola 29 Jun '07

29 Jun '07

Hi, I am typesetting a document with XeConTeXt, containing many MetaPost figures. All the labels in the figures are typeset using \sometxt{} and sometxt(). For some reasons, in the final document some of them appear horribly stretched or shrinked as if their bounding box has not been computed correctly (even after typesetting the document n times). I have absolutely no clue why that happens, but I imagine it is some strange interaction in the environment file, because if I typeset any of the problematic figures by itself in a different document with a minimal environment everything is fine. My environment file is quite long and I cannot find a short example showing the problem. The deformed labels seem to be always among those written by \sometxt (but not all of them are wrong!), while those written using sometxt() seem always ok. What may it depend upon? Nicola PS: I am aware of the interaction between sometxt() and \sometxt: I would like to point out that the labels are *not* messed up: they are the correct labels, just appearing deformed.

1 1

using a symbol from the wasy physics symbol set
by Jesse Alama 29 Jun '07

29 Jun '07

I'd like to use the symbol varangle from the wasy physics symbol set. In my file I've got \usesymbols[was] \showsymbolset[wasy physics] $\symbol[varangle]$ In the PDF that's generated, I see the symbols in the wasy physics symbol set just fine, but following the symbol set table, I just see an OE ligature glyph. What might be going on? And is there any way I can use \varangle rather than \symbol[varangle] ? Thanks, Jesse -- Jesse Alama (alama(a)stanford.edu) *65: "thesis" is allowed only inside a proof

2 1

Texfont feature request.
by John R. Culleton 28 Jun '07

28 Jun '07

Texfont is an awesome program. I just created a free and legal Bitstream Charter pseudo small caps font. (The real thing costs money so I can't redistribute it free.) But I have two problems with it in practice. 1. It is designed to work with typescripts. But when I need to use the font with e.g., pdftex I have to use updmap anyway. That means among other things I have to search for the generated map file, determine its name, and add it to updmap.cfg. And even with Context sometimes a typescript is overkill. 2. When I want to distribute a demonstration app in source code format using that font, I have to collect all the generated bits and pieces and put them in the same directory as the app. That will work. But where are all the bits and pieces? More searching. Now here is my request: add a switch that eliminates the movement of bits and pieces elsewhere so that the map file, the tfm files, the vf files etc. are all collected in the current directory. AFAIK such an app would compile and use the special font. -- John Culleton ATTN Publishers/authors: If you don't read you don't succeed. Free short list of publishing/marketing books. http://wexfordpress.com/tex/shortlist.pdf

2 1