March 2010 - ntg-context - NTG Mailing Lists

Re: [NTG-context] pk-directory
by Wolfgang Werners-Lucchini 28 Mar '10

28 Mar '10

Hallo Hans, > > so it would be nice, if a user could see (from a log) what and > > where luatex is searching. Isn't there any switch? > > --track=resolvers.locating,resolvers.detail Hmm! luatex ignores this and luatex --help does not list an option named --track nor does it context. Wolfgang

2 1

Vertical alignment in combinations
by Vyatcheslav Yatskovsky 28 Mar '10

28 Mar '10

Hi, Please, advise. I want two pictures to stand side-by side. The first picture has much smaller height. In result, the pictures are aligned by the bottom line. How to move the first figure up in the center or top (at least, manually)? \startcombination[2*1] {\externalfigure[lily02.png]}{} {\externalfigure[scr-4-4.png][scale=750]}{} \stopcombination Please, see attachement BR, Vyatcheslav

3 2

Re: [NTG-context] letter: backaddress
by Wolfgang Werners-Lucchini 28 Mar '10

28 Mar '10

Hallo Wolfgang, > You're mixing different things. > > What is the difference between > > > > \setupletterstyle[option][backaddress=yes] > > > With \setupletterstyle[<element>=yes|no] you can show or hide > elements ok! > > \setupletterstyle[backaddress][alternative=yes] > > > > In 'default.nli' I found > > > > \defineletterelement[\v!backaddress][\v!auto] > > {\doifelselettervalue\c!backaddress > > {\lettervalue\c!backaddress} > > {\lettervalue\c!fromname > > \doiflettervalue\c!fromaddress\\ > > \lettervalue\c!fromaddress}} > > > > what I interpret in the following way: > > > > If 'backaddress'=auto > > If exist a constant 'backaddress' > > use it > > else > > compose one from 'fromname' and 'fromaddress' > > > The constant needs a content, if there is no content for > 'backadress' the field is filled with 'fromname' and 'fromaddress'. So let's test if I have understand this: With \setupletterstyle[option][backaddress=no|yes] one can disable|enable a backaddress. With \setupletterstyle[backaddress][alternative=no|yes|auto] one can select between no backadress| a composed backaddress from the fromdata| the yes behaviour if no predefined backaddress is defined And to define such a own backaddress, one uses \setlettervalue{backaddress}{something} Hopefully this is right! Wolfgang

2 1

Re: [NTG-context] pk-directory
by Wolfgang Werners-Lucchini 28 Mar '10

28 Mar '10

> > Is there a debug-switch which informs the user what and where > > luatex is searching? > > If you're working in a shell, try setting the KPATHSEA_DEBUG > environment variable to -1, you will get tons of information about > path lookups and directory searches. > > Arthur I thought luatex does not use kpathsearch anymore? Wolfgang

2 1

Re: [NTG-context] pk-directory
by Wolfgang Werners-Lucchini 28 Mar '10

28 Mar '10

Hallo Taco, > >> Dumping a ready-made pk file in the local directory worked last > >> time I tried it. > > > > > > No success! Neiter *.pk nor *.600pk > > and not with a local subdir /dpi600 > > > > What extension have you used? > > .600pk (but that was ages ago, when I still cared about pk fonts) so it would be nice, if a user could see (from a log) what and where luatex is searching. Isn't there any switch? Wolfgang

2 1

Re: [NTG-context] color problem with columns
by Wolfgang Werners-Lucchini 28 Mar '10

28 Mar '10

> > ---------------------------------------------------------------- > > \setupcolors[state=start] > > \newcounter\V > > \def\Vers#1{\increment\V {\color[darkgreen]\rm\bi \V} #1} > > > \def\Vers#1{\increment\V \dontleavehmode{\color[darkgreen]\rm\bi \V} > #1} > > but i think this is better > > \setupcolors[state=start] > > \definelabel > [Vers] > [headstyle=bolditalic, > headcolor=darkgreen, > command=\groupedcommand\dontleavehmode\space] > > \starttext > \startcolumns > text\par\dorecurse{50}{\Vers Dies ist ein Testsatz der gerade lange > genug ist, um zu zeigen was zu zeigen ist.\par} > \stopcolumns > \stoptext Thank you very much! Wolfgang

1 0

Interlinespace in headertexts
by Willi Egger 28 Mar '10

28 Mar '10

Hi, When setting up a headertext in a \vbox there is no interlinespacing. Placing the same text in a \vbox in the text area there is the default interlinespacing. Is there a simple explanation for this behaviour? Using LuaTeX, Version beta-0.50.0-2009122422, ConTeXt ver: 2010.03.02 12:34 MKIV Minimal example attached. Willli

3 7

U3D inclusion
by gummybears 28 Mar '10

28 Mar '10

In november last year Hans Hagen was so kind to send me a copy of back-u3d.mkiv which is now included in the latest beta. As Hans mentioned the code he gave me is untested. After a couple of tests here are my findings *) The preview does not work at this moment. I only see a light blue square which can be activated. After which the 3d viewer shows the embedded 3d image *) Specifying several views as shown in back-u3d.mkiv shows up in the resulting pdf as "unknown view" *) I also experimented with different values for coo, c2c, roll etc. When not specifying any of these settings the embedded 3d is always shown with the incorrect roll i.e the roll is always 90 degrees off For anyone interested, the 3d file was produced with Asymptote 1.91 ( http://asymptote.sourceforge.net/) =============== Context sample code ============================== \starttext \startluaparameterset [u3d:myset:display:1] toolbar=false, preview="prcu3d/loading.png", view = { name = 'default', bg = {1,1,1}, mag = 25, coo = {2,2,2}, c2c = {0,0,1}, rot = {40,0,60}, roo = 2, lights = 'CAD' } \stopluaparameterset \useexternalfigure [cubes] [prcu3d/cubes.prc] [width=\textwidth, height=0.5\textwidth, display=u3d:myset:display:1] \placefigure[here]{3d cube}{\externalfigure[cubes]} \stoptext ========================== end of Context sample code =======================================

3 3

color problem with columns
by Wolfgang Werners-Lucchini 28 Mar '10

28 Mar '10

Hallo, on Vers 38 at page 2 (see example) text is green. ---------------------------------------------------------------- \setupcolors[state=start] \newcounter\V \def\Vers#1{\increment\V {\color[darkgreen]\rm\bi \V} #1} \starttext \startcolumns \dorecurse{50}{\Vers{Dies ist ein Testsatz der gerade lange genug ist, um zu zeigen was zu zeigen ist.}\par} \stopcolumns \stoptext ---------------------------------------------------------------- How can this be fixed? Wolfgang PS If a Vers is starting on a new page, the number is black.

2 1

docs (was: Re: Microtype in ConTeXt)
by Michael Saunders 27 Mar '10

27 Mar '10

Peter, that post of Hans's mainly argues that the old manual is good enough and then goes on to talk about development. For example: "Even an old manual can quite well describe functionality as much didn't change." It can if it ever did. I don't think cont-eni.pdf etc., describe the functionality well at all. "As one can visually get all kind of output and as typographical elements can interfere the ultimate manual would show $n!$ variants and become quite unreadable. There is no easy way out of this. " There is: describe each option concisely and abstractly, then you need only be concerned with $n$ elements. Almost every LaTeX package manages to do this successfully, and they are very usable. "More documentation would not help all users. " There needn't be more. It needn't be lengthy, just clear, complete, and concise. "There are quite some options that were never meant for usage beyond our own, but as we ship the full product, they become visible. No, they are not documented apart from the source. Yes, if useful they should be documented but why by me? " Because you are probably the only person on earth who understands them. Getting that knowledge out of your head and into others' will require an act of communication. "I only work on a manual (or article or whatever) if it's fun to do." That may be the problem! Hans, Here are some constructive suggestions. I hope you take them seriously: If you ever write another manual, perhaps when MKIV is complete, 1. Start from scratch. Throw away the old material. 2. Forbid yourself the use of code examples. They are a crutch which impedes communication. First, write the whole manual with normal, abstract, expository prose. When it's complete and explains everything fully---when it {\em makes sense}--- {\em then} illustrate it with as many code samples as you like. 3. Have a standard format, a sort of checklist, for what must be said about each argument, parameter, command and group of commands: ---What is its function? ---How is it used? ---What is it used for (what effect is it supposed to achieve)? ---What are the options? A regular format like this will make it much easier on you. You'll have a regular structure that you simply have to fill in. It might even make the task more fun. 4. Get someone to serve as an editor. These will solve most of your writing problems. I look forward to a new manual someday. Thanks, -- Michael

2 1