November 2011 - ntg-context - NTG Mailing Lists

Zoom image in presentation
by Roger Mason 07 Nov '11

07 Nov '11

Hello all, I'd like to be able to zoom an image during a presentation. My thinking is that it might be possible by turning layers on and off interactively. I see in this message: http://archive.contextgarden.net/message/20110426.183109.fc46c5a5.en.html that Hans said (enigmatically :-)) "And then there are viewerlayers (acrobat) that you can turn on and off with \goto{On}[VideLayer{mylayer}] but that's a different topic." Any hints on how I could do this? I'm using the latest standalone, installed yesterday. Thanks, Roger

1 0

Modifying potrusion parameters
by Simonyi András 06 Nov '11

06 Nov '11

Dear ConTeXt-ers, I am using protrusion and char. expansion for a book project (with MKIV from the latest ConTeXt minimal), and it works wonderfully, with the exception of a minor problem: I find the preset protrusion parameters for "guillemets" (double angle quotes) which occur frequently in my (Italian) text too large, and would like to modify them. Relying on the wiki and mailing-list posts, I realised that the parameters are set in the file font-ext.lua, but changing this file seems to have no effect on the typesetting. How should I rebuild/recompile ConTeXt in order to "apply" my changes? I am a novice ConTeXt user, so please forgive me if my question is trivial. Thanks in advance for your help and best wishes, András Simonyi, Budapest, Hungary

2 2

languagespecifics
by pmlists＠free.fr 06 Nov '11

06 Nov '11

Hello, Is there something like \startlanguagespecifics[fr] ... \stoplanguagespecifics in mkiv? Does it make sense, to keep the module t-french.tex? I would like to integrate \setcharacterspacing[frenchpunctuation] everywhere (text, headers, footers and so on), but when a user loads the module and changes settings for headers or footers afterwards, that setting would be overwritten. Thus, if there are no methods, to do such things, I would drop the module and french specific settings have to be set up on a per document basis. What do you think? -- Peter

3 5

\unknown lost on xml export
by Marco Pessotto 06 Nov '11

06 Nov '11

Hello there. While exporting the ellipses are completely lost. Is there a workaround for cases like that (I have the feeling this is the top of the iceberg)? The following minimal example should be clear enough: %%% start example \setupbackend[export=yes] \starttext Hello\unknown{} world! \stoptext %%% end example Which leads to: <?xml version='1.0' encoding='UTF-8' standalone='yes' ?>     <document language="en" file="prova" date="Sat Nov 5 15:45:09 2011" context="2011.11.02 20:10" version="0.30" xmlns:m="http://www.w3.org/1998/Math/MathML"> Hello world! </document> Best regards -- Marco

3 2

Re: [NTG-context] Problem with mkiv under MacOSX 7 (Lion)
by Robert Blackstone 06 Nov '11

06 Nov '11

> On 6 Nov 2011, at 09:57 , Mojca Miklavec <mojca.miklavec.lists(a)gmail.com> wrote: >> On Sat, Nov 5 2011 at 18:24, Wolfgang Schuster wrote: >>> (Robert Blackstone wrote:) >>> (source /Users/robertblackstone/context-minimal-04-11/tex/setuptex) >> >> Change this to >> source?/Users/robertblackstone/context-minimal-04-11/tex/setuptex?/Users/robertblackstone/context-minimal-04-11/tex > > Or even better to > export PATH=/Users/robertblackstone/context-minimal-04-11/tex/texmf-osx-64/bin:$PATH > context $1 > > And try to delete symb-uni-zapf unless you need it. > > Mojca Thank you. Deleting symb-uni-zapf solved the problem. (There were at least two of these locked folders in my system, both a nuisance in this respect.) As far as the engine is concerned, both Wolfgang's and your suggested alternative engine texts work, as did the original one, in the end. Thank you both You (Mojca) also wrote: Your log implies that you are using TeX Live 2011, not TeX minimals. But later on you sent a different log. That is correct. In the first trials I inadvertently used an Engine with an error in the path name (result of migrating everything from another Mac and not checking things thoroughly) so that the minimals could not be found. Best regards, Robert Blackstone

1 0

xtables in custom macros
by "Stefan Müller" 06 Nov '11

06 Nov '11

Hi list, I just played a bit with the nice new xtables. It seems as if "\stopxtable" does not work if used inside a custom macro. I get a "Runaway argument" error with the current standalone if I uncomment "\Doesnt" in the following example. \define\Works{\startxtable \startxrow \startxcell works \stopxcell \stopxrow} \define\Doesnt{\startxtable \startxrow \startxcell does not work \stopxcell \stopxrow \stopxtable} \starttext \Works \stopxtable %\Doesnt \stoptext Did I miss something or is this a bug? Best regards, Stefan. -- _______ ey, leute, ich hab so lange gebraucht um mir plan a auszudenken, fragt jetzt doch nicht auch noch nach plan b! NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone

4 9

Two frames side by side?
by Alasdair McAndrew 06 Nov '11

06 Nov '11

I want two frames side by side: the left frame comprising just text (and some displayed formulas), and the right hand side frame some high level computer algebra code. The right hand side will have a gray background, and will consist mainly of typeset equations separated by horizontal lines. I can get the two frames looking just right, but no matter how thin I make them, they display one under the other, not side by side. Any ideas? Thanks, Alasdair

3 3

Problem with mkiv under MacOSX 7 (Lion)
by Robert Blackstone 05 Nov '11

05 Nov '11

Dear All, Is there anyone who could help me with the following: ConTeXt mkiv does not work on my Mac under MacOSX 10.7 (Lion). This holds not only for the minimals installed yesterday (04-11-2011) but also for older versions (september and october, migrated from another Mac under OSX-10.6) I attach the log file. Could it be that Lion is not yet supported? (mkii seems to work OK) Thanks in advance, Robert Blackstone

5 4

Re: [NTG-context] Problems with linespacing - typescript
by Jan Heinen 05 Nov '11

05 Nov '11

> Regenerate the font database with “mtxrun --script font --reload” and try it again. That was not successful. However, I changed your code a bit and now it seems ok: When I use: \definedfont[name:allerlight*default at 36pt] instead of: \definedfont[file:allerlt*default at 36pt] then it works. Changed: file: -> name: allerlt -> allerlight Do I still use "type-aller"? Or did I destroy the connection to the typescript with my changes? Maybe important? The "aller"-files are ttf not otf. Regards Jannis

2 1

Re: [NTG-context] Problems with linespacing - typescript
by Jan Heinen 05 Nov '11

05 Nov '11

> > Where do you got the font files from, I checked the version from fontsquirrel > [1] > and dalton maag [2] and saw that both use different file names and in my > ypescripts I used the names from fontsquirrel. You are right - my aller und my libertine were from other website with diferences in the naming. Now I have them from font-squirrel and cpan. \setupbodyfont[aller] is now working. But your example above for the typescript does not work: >> \start \setupalign[right,broad]\definedfont[file:allerlt*default at 36pt]\setupinterlinespace >> Ich bin Blindtext. Von Geburt an. Es hat lange gedauert, bis ich begriffen >> habe, was es bedeutet, ein blinder Text zu wer wer wer wer wer wer wer wer wer >> wer wer keinen Sinn. Man wirkt hier und da aus dem Zusammenhang gerissen. Oft >> wird man gar nicht erst gelesen. >> >> Aber bin ich deshalb ein schlechter Text? Ich weiss, dass ich nie die Chance >> haben werde, im Stern zu erscheinen. >> \stop >> \stoptext >> I don't get "allerlt" and also no "36pt". Error-message while compiling: fonts> fallback modern rm 12pt is loaded fonts> defining> font with asked name 'allerlt' is not found using lookup 'file' fonts> defining> unknown font allerlt, loading aborted fonts> defining> unable to define allerlt as \**thedefinedfont** I hope someone knows an answer. Janis

2 1