- ntg-context - NTG Mailing Lists

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 28 Mar '10

28 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

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

27 Mar '10

On 27 Mar 2010 at 12:00, ntg-context-request(a)ntg.nl wrote: > > That being said, I realize that it means Metafont fonts can't be > > used in Mark IV, am I right? > > 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? Is there a debug-switch which informs the user what and where luatex is searching? Wolfgang

3 2

Re: [NTG-context] Microtype in ConTeXt
by Michael Saunders 27 Mar '10

27 Mar '10

> On 27-3-2010 1:15, Yan Zhou wrote: > >> As I can see now ConTeXt is indeed a far more advanced system than LaTeX. But I have one more query. Where can I find the documents. When following these replies and some other messages in the list, I find some commands not documented in the Manual or Reference Manual. In LaTeX, all commands are detailed documented in source2e.tex, in TeX, The TeXBook explains everything. So in ConTeXt, where can I find such detailed documents. I tried the documented source, but it is more like a PDF version or source with only a little documentation. > > as most of the functrionality does not change you can use older docs > (website, wiki etc) for most cases > > newer things i.e. introduced in mkiv using luatex are described in for > instance mk.pdf and articles > > of course the wiki is a good source as well Notice that Yan Zhou isn't complaining that the docs are old. Our problem is that they are sketchy and rambling, bits and pieces of this and that without any systematic explanations. Often they are just some unexplained code samples that communicate nothing (unless you happen to be the guy who invented the language). I can't think of one command that is fully explained along with all its possible parameters. The wiki is better written, but even less complete. It might not be possible to do better, but this is a huge obstacle to anyone who actually wants to use ConTeXt. The docs hint at a lot of features that sound better than LaTeX, but actually getting them to work is a different story.

2 1

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

27 Mar '10

Hallo, > \setupletterstyle[backaddress=yes] > > it's a disabled by default but i forgot to do this also in the > default style > (most styles reset the layout and use default values before they > modify it) > > \setupletterstyle > > [backaddress] > > [alternative=auto, > > > 'auto' is now the default value > > Wolfgang I do not understand the the main principle. What is the difference between \setupletterstyle[option][backaddress=yes] and \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' To use this, I tried to set \setupletterstyle[option][backaddress=auto] or \setupletterstyle[backaddress][alternative=auto] And I tried to set this constant backaddress, with setlettervalue{backaddress}{something} But no combination is working. What worked is \setupletterstyle[option][backaddress=yes] \setlettervalue{backaddress}{something} which should not work, because \defineletterelement[\v!backaddress][\v!yes] {\lettervalue\c!fromname \doiflettervalue\c!fromaddress\\ \lettervalue\c!fromaddress} is composing the 'backaddress' from the fromdata. My skills to read the sourcecode are very limited, so most likely I buhave something misunderstood. Wolfgang

2 1

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

27 Mar '10

On 26 Mar 2010 at 22:09, Hartmut Henkel wrote: > On Fri, 26 Mar 2010, Hans Hagen wrote: > > On 26-3-2010 21:30, Wolfgang Werners-Lucchini wrote: > > > > > > how should the directory be named where a 600 dpi pk-font is > > > searched for by luatex? > > > > i'm not so sure if luatex does pk fonts (i havent't included pk > fonts > > in 15 years) > > it does, with the default kpathsea paths, e. g.: > > hahe@hahepc1:~$ luatex xx > This is LuaTeX, Version beta-0.52.0-2010032122 (rev 3515) > (./xx.tex [1] ) > </home/hahe/.texlive2009/texmf-var/fonts/pk/ljfour/public/cm/cm > r10.600pk> > Output written on xx.pdf (1 page, 3242 bytes). > Transcript written on xx.log. > > or > > This is LuaTeX, Version beta-0.52.0-2010032122 (rev 3515) > (./xx.tex [1] ) > </usr/local/texlive/2009/texmf-dist/fonts/pk/ljfour/public/cm/d > pi600/cmr10.pk> > Output written on xx.pdf (1 page, 3242 bytes). > Transcript written on xx.log. > > Regards, Hartmut Hello Hartmut, hallo Hans, I have tried both variants but nothing works. I use the minimals under windows. What can I do (examine files, logs) to solve the problem? Wolfgang

3 2

letter: backaddress
by Wolfgang Werners-Lucchini 27 Mar '10

27 Mar '10

Hallo, 'backaddress' is composed from 'fromname' and 'fromaddress', but this is to long and must be shortend. How can I overwritte 'backaddress'? Gruß, Wolfgang

4 5

Re: [NTG-context] URL setup
by Vyatcheslav Yatskovsky 27 Mar '10

27 Mar '10

Hi Now I see. Thanks. > \setupinteraction > [state=start, > color=red] % \goto and \from > > \setupurl > [color=orange] % \url B.R. Vyatcheslav

1 0