- ntg-context - NTG Mailing Lists

MKIV and externaligure inside metafun
by Mojca Miklavec 28 Aug '09

28 Aug '09

Hello Hans, nothing urgent (I'm still on MKII), but it seems that MKIV (maybe only on my machine?) has problems with externalfigure("filename.png") Mojca

2 1

Command version of \em
by Matthijs Kooijman 28 Aug '09

28 Aug '09

Hi all, is there any "command version" of \em, like there is for \bold and friends? I can write either \bold{foo} of {\bold foo}, but only {\em foo} and not \em{foo}. Is there any way to do this already, or should I just define \emph myself or something like that? Gr. Matthijs

4 3

Re: [NTG-context] texexec with 2 processors?
by Xan 28 Aug '09

28 Aug '09

En/na Mojca Miklavec ha escrit: > > > You cannot start processing page 500 before you know where page 499 > wil end. TeX is not really a kind of application where you would gain > a lot by parallelization. And honestly, I don't remember seing many > applications using both cores. (Plus: I'm happy if other applications > continue to run smoothly instead of being blocked by TeX using 95% of > both processors.) > I did not say to process page 500 before the page 499. I just say use all power of the multiple processors. > >> It could be useful for offering typesetting services. I'm thinking about >> having a computation service like alpha.wolfram but with ConTeXt. Like >> ConTeXt online but benefit from multiple processors.... >> > > If you would offer a service, you would get multiple requests at the > same time anyway, so there's no real need for that in this case > (you'll face many more serious problems when offering typesetting > service). > > You are right here. >> Joking, perhaps you could fix it in Mark VII ;-) >> > > You can try XeTeX if you want to put load on both processors. It does > offer a parallel process as far as I heard, Is it true? > but then you'll probably > want support for quad-core once you get a better computer :) > > Mojca > Xan.

3 3

texexec with 2 processors?
by Xan 28 Aug '09

28 Aug '09

Hi, I have Intel Core Duo and when I run texexec the CPU resource in gnome is marked about 50%. Is it mean that texexec only use one processor? If it's, can you think to improve it for scalability? Just a curious question. Xan. PS: Please, CCme.

4 6

PDF x1a:2001 and Context
by John Culleton 27 Aug '09

27 Aug '09

PDF X/1a:2001 is an old pdf standard still required by some important American printers. Han The Thanh et al. has created a package for pdfLatex. I wonder if there is a route to this output using Context? -- John Culleton Able Indexers and Typesetters

3 3

A problem with \useURL or \from
by eythanweg＠gmail.com 27 Aug '09

27 Aug '09

Hi, With current context and luatex revision 3038 I use this sample: \setupinteraction[state=start] \setupurl[color=blue] \starttext \useURL[here][http://google.com] \from[here] \stoptext It compiles with the link shown correctly but in greenish color. Pressing on it, the browser tries to visit http://here/ . I am not sure where the source of the problem is, context or luatex. Thank you, Eythan

2 4

lang-ita.tex is broken for spanish
by Enrique Jiménez Gallego 26 Aug '09

26 Aug '09

Hi, I updated context-minimals today and \mainlanguage[es] is broken. Example: \mainlanguage[es] \starttext \chapter[]{Cap1} Hello World. \stoptext $ texexec --pdf example.tex ! Undefined control sequence. <argument> \itulo The problem is lang-ita.tex : *** lang-ita.tex.old 2009-08-21 16:16:03.000000000 +0200 --- lang-ita.tex 2009-08-26 18:15:38.200286872 +0200 *************** *** 266,273 **** \setuplabeltext [\s!ro] [\v!graphic=Graficul ] \setuplabeltext [\s!fr] [\v!chapter=] ! \setuplabeltext [\s!es] [\v!chapter=Cap\'\itulo] ! \setuplabeltext [\s!ca] [\v!chapter=Cap\'\itol] \setuplabeltext [\s!it] [\v!chapter=] \setuplabeltext [\s!la] [\v!chapter=] \setuplabeltext [\s!pt] [\v!chapter=] --- 266,273 ---- \setuplabeltext [\s!ro] [\v!graphic=Graficul ] \setuplabeltext [\s!fr] [\v!chapter=] ! \setuplabeltext [\s!es] [\v!chapter=Cap\'itulo] ! \setuplabeltext [\s!ca] [\v!chapter=Cap\'itol] \setuplabeltext [\s!it] [\v!chapter=] \setuplabeltext [\s!la] [\v!chapter=] \setuplabeltext [\s!pt] [\v!chapter=] Or better: *** lang-ita.tex.old 2009-08-21 16:16:03.000000000 +0200 --- lang-ita.tex 2009-08-26 18:20:17.881411912 +0200 *************** *** 265,305 **** \setuplabeltext [\s!pt] [\v!graphic=Gr\'afico ] \setuplabeltext [\s!ro] [\v!graphic=Graficul ] \setuplabeltext [\s!fr] [\v!chapter=] ! \setuplabeltext [\s!es] [\v!chapter=Cap\'\itulo] ! \setuplabeltext [\s!ca] [\v!chapter=Cap\'\itol] \setuplabeltext [\s!it] [\v!chapter=] \setuplabeltext [\s!la] [\v!chapter=] \setuplabeltext [\s!pt] [\v!chapter=] \setuplabeltext [\s!ro] [\v!chapter=] \setuplabeltext [\s!fr] [\v!section=] ! \setuplabeltext [\s!es] [\v!section=Secci\'on] ! \setuplabeltext [\s!ca] [\v!section=Secci\'o] \setuplabeltext [\s!it] [\v!section=] \setuplabeltext [\s!la] [\v!section=] \setuplabeltext [\s!pt] [\v!section=] \setuplabeltext [\s!ro] [\v!section=] \setuplabeltext [\s!fr] [\v!subsection=] ! \setuplabeltext [\s!es] [\v!subsection=Subsecci\'on] ! \setuplabeltext [\s!ca] [\v!subsection=Subsecci\'o] \setuplabeltext [\s!it] [\v!subsection=] \setuplabeltext [\s!la] [\v!subsection=] \setuplabeltext [\s!pt] [\v!subsection=] \setuplabeltext [\s!ro] [\v!subsection=] \setuplabeltext [\s!fr] [\v!subsubsection=] ! \setuplabeltext [\s!es] [\v!subsubsection=Subsubsecci\'on] ! \setuplabeltext [\s!ca] [\v!subsubsection=Subsubsecci\'o] \setuplabeltext [\s!it] [\v!subsubsection=] \setuplabeltext [\s!la] [\v!subsubsection=] \setuplabeltext [\s!pt] [\v!subsubsection=] \setuplabeltext [\s!ro] [\v!subsubsection=] \setuplabeltext [\s!fr] [\v!subsubsubsection=] ! \setuplabeltext [\s!es] [\v!subsubsubsection=Subsubsubsecci\'on] ! \setuplabeltext [\s!ca] [\v!subsubsubsection=Subsubsubsecci\'o] \setuplabeltext [\s!it] [\v!subsubsubsection=] \setuplabeltext [\s!la] [\v!subsubsubsection=] \setuplabeltext [\s!pt] [\v!subsubsubsection=] --- 265,307 ---- \setuplabeltext [\s!pt] [\v!graphic=Gr\'afico ] \setuplabeltext [\s!ro] [\v!graphic=Graficul ] + %D We don't set these here. One can do that in a style. + \setuplabeltext [\s!fr] [\v!chapter=] ! \setuplabeltext [\s!es] [\v!chapter=] ! \setuplabeltext [\s!ca] [\v!chapter=] \setuplabeltext [\s!it] [\v!chapter=] \setuplabeltext [\s!la] [\v!chapter=] \setuplabeltext [\s!pt] [\v!chapter=] \setuplabeltext [\s!ro] [\v!chapter=] \setuplabeltext [\s!fr] [\v!section=] ! \setuplabeltext [\s!es] [\v!section=] ! \setuplabeltext [\s!ca] [\v!section=] \setuplabeltext [\s!it] [\v!section=] \setuplabeltext [\s!la] [\v!section=] \setuplabeltext [\s!pt] [\v!section=] \setuplabeltext [\s!ro] [\v!section=] \setuplabeltext [\s!fr] [\v!subsection=] ! \setuplabeltext [\s!es] [\v!subsection=] ! \setuplabeltext [\s!ca] [\v!subsection=] \setuplabeltext [\s!it] [\v!subsection=] \setuplabeltext [\s!la] [\v!subsection=] \setuplabeltext [\s!pt] [\v!subsection=] \setuplabeltext [\s!ro] [\v!subsection=] \setuplabeltext [\s!fr] [\v!subsubsection=] ! \setuplabeltext [\s!es] [\v!subsubsection=] ! \setuplabeltext [\s!ca] [\v!subsubsection=] \setuplabeltext [\s!it] [\v!subsubsection=] \setuplabeltext [\s!la] [\v!subsubsection=] \setuplabeltext [\s!pt] [\v!subsubsection=] \setuplabeltext [\s!ro] [\v!subsubsection=] \setuplabeltext [\s!fr] [\v!subsubsubsection=] ! \setuplabeltext [\s!es] [\v!subsubsubsection=] ! \setuplabeltext [\s!ca] [\v!subsubsubsection=] \setuplabeltext [\s!it] [\v!subsubsubsection=] \setuplabeltext [\s!la] [\v!subsubsubsection=] \setuplabeltext [\s!pt] [\v!subsubsubsection=]

2 1

Footnotes and body text
by Vyatcheslav Yatskovsky 26 Aug '09

26 Aug '09

Hello, Looks like my previous message was overlooked. Let me cry again. In my document footnotes' upper line clashes with body text. In result, last line of body text looks underlined. Please, take a look at the attachment. Regards, Vyatcheslav

3 2

Why are pretty printer names uppercased?
by Matthijs Kooijman 26 Aug '09

26 Aug '09

Hi all, according to the wiki, and the current code, the arguments to \installprettytype should be uppercased. E.g.: \installprettytype [PHP] [PHP] Referring to them should be uppercased as well: \definetyping[PHP] [option=PHP] \setuptyping[option=PHP] However, the filename should be lowercase, e.g. pret-php.lua and the pretty printer should register itself in lowercase as well: buffers.newvisualizer("lua"). The first thing that happens to the arguments of installprettytype is to lowercase them, and every option= argument that points to a pretty printer is lowercased by setvisualizer in lua before being used. If everything is lowercased, why do we still recommend the arguments to \installprettytype and option= to be uppercase? IMHO this makes things confusing when trying to understand which PHP refers to which php or PHP in the greater picture of things. Why not recommend people to use lowercase identifiers instead, since we're changing everything into lowercase anyway? Or perhaps go a bit further and remove the lowercasing code alltogether, since I don't see any real gain. If the strings / filenames should just match exactly, things will get a lot more predictable? Gr. Matthijs

2 3

Re: [NTG-context] Section labels in appendices (appendixlabel=)
by Wolfgang Schuster 26 Aug '09

26 Aug '09

Am 26.08.2009 um 10:33 schrieb Mojca Miklavec: > On Wed, Aug 26, 2009 at 10:08, Wolfgang Schuster wrote: >> >> \setuphead >> [\v!section] >> [\v!appendix\c!label=\v!section, >> \v!bodypart\c!label=\v!section] % bijlageconversie= >> \Character > > I'm sorry, but I'm blind ... :( :( :( > Doesn't it also say appendixlabel= here? I just don't see it how it's > used. Maybe I should use something else but "section"? Enable the label with \setuphead, not \setupsection. Wolfgang

2 1