February 2007 - ntg-context - NTG Mailing Lists

Re: [NTG-context] How to make a "natural" table float.
by Wolfgang Werners-Lucchini 02 Feb '07

02 Feb '07

On 2 Feb 2007 at 19:17, ntg-context-request(a)ntg.nl wrote: > \setupcaptions[location=high] What about 'top'? Wolfgang

1 0

context meeting
by Hans Hagen 02 Feb '07

02 Feb '07

Hi, It's time to start finalizing the programm etc for the upcoming CONTEXT user meeting in Epen NL, *March 24* and *March 25*. http://context.aanhet.net/epen2007/index.htm So far, 20 people have registered and we have room for at most 30 (unless offsite). Any input about talks, topics, tutorials, activities, dev sessions, etc is welcome since we're free to schedule as we like. If you have questions about the how/when/where you can mail taco or me. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------

2 1

Bib module error handling
by Oliver Buerschaper 02 Feb '07

02 Feb '07

Hi Taco, talking about the bib module ... I usually get confused when I cite a reference in the text but accidentally use the wrong citation key or have forgotten to put the record into my bib file at all. Instead of screaming question marks in the pdf output ConTeXt tacidly typesets a reference number and adds an empty entry to the list of references. Is this really desired? After all, it makes tracking down the wrong \cite command a bit of an issue ... admittedly some warnings show up in the log but definitely not on the pdf printout. Would it be possible to adopt the same error handling as for \in and friends? Best, Oliver

2 5

XeTeX and OpenType LM
by Mojca Miklavec 02 Feb '07

02 Feb '07

Hello, Since there are serious problems with XeTeX on non-TeXLive distributions anyway: why not mess it up properly this time? The attached file seems to work OK, although kpathsea complains a bit (but these are only warnings - no serious problems; perhaps other macros could or should be adapted - I didn't dig too much into the internals): kpathsea: Illegal fontname `[lmsans12-regular]': contains '[' kpathsea: Illegal fontname `[lmsans10-bold]': contains '[' kpathsea: Illegal fontname `[lmsans12-oblique]': contains '[' kpathsea: Illegal fontname `[lmtypewriter12-regular]': contains '[' kpathsea: Illegal fontname `[lmtypewriter10-oblique]': contains '[' Can someone please take a look? I don't know how well this integrates with luaTeX. Perhaps the name can be changed from \definexetexfontsynonym to \defineotffontsynonym or something similar, so that the underlying code can then differ depending on whether it's luatex or XeTeX the one which has to access the otf fonts. If this or a modified version of it makes it into the core, I would suggest another (slightly radical) change - to redefine default encoding to "uc" instead of "ec" for XeTeX (and luatex) before loading the formats. It would be really great if the default XeTeX settings would simply work out-of-the-box, contrary to now, when the default ec-lmr is nearly useless. Mojca

3 8

longer ConTeXt+XeTeX compile time than before
by Jeong Dalyoung 01 Feb '07

01 Feb '07

Dear all, Recently I updated TeXlive and ConTeXt. After that the compiling time of a file under ConTeXt+XeTeX became longer than before. However, there is no change when I compiled the files using ConTeXt. I tested the same file using the previous ConTeXt version in the another Mac and found that there was no delay. The big difference between them as follows: 1. part of log file under new version ..... (/usr/local/gwTeX/texmf.pkgs/tex/context/base/cont-err.tex systems : no file 'cont-sys.tex', using 'cont-sys.rme' instead ) ) <at here, it paused for long time> stdin -> speedtest.pdf [1] 8949 bytes written Output written on speedtest.pdf (1 page). Transcript written on speedtest.log. TeXUtil | parsing file speedtest.tui TeXUtil | shortcuts : 169 TeXUtil | expansions: 308 TeXUtil | reductions: 0 TeXUtil | divisions : 0 TeXUtil | loaded files: 1 TeXUtil | temporary files: 0 TeXUtil | commands: 25 TeXUtil | programs: 0 TeXUtil | tuo file saved TeXExec | runtime: 47.741367 In another Mac installed the previous version, "speedtest.xdv -> speedtest.pdf" instead "stdin -> speedtest.pdf" I don't know why two machines made pdf files in different ways, but I assume that "stdin -> speedtest.pdf" is the cause of the delay. My powerbook is 1.33GHz PowerPC G4. Would some one try the following file and see what happen? Thank you. Regards, Dalyoung %%%%%%%%%%%%% \font\A="Hoefler\space Text" at 24pt \starttext \A “Hello world!” \stoptext %%%%%%%%%%%%%%

4 3

Letters in ConTeXt
by Rolf Marvin Bøe Lindgren 01 Feb '07

01 Feb '07

the one thing that stops my total conversion to ConTeXt is my lack of understanding of, er, context. I've studied the manual "Corresponcence" which presupposes far better understanding of ConTeXt than I currently possess. I imagine though that a useful short working example would help. anyone? -- Rolf Lindgren roffe(a)extern.uio.no

6 17

Re: [NTG-context] Portuguese characters under Mac OS X
by Fidel Viegas 01 Feb '07

01 Feb '07

On 1/31/07, Oliver Buerschaper <oliver.buerschaper(a)mpq.mpg.de> wrote: > > > I am having a problem processing my ConText files under Mac OS X. I > > am using TeXShop, and when I render the text written in Portuguese, > > it does not render the characters with accents. I did not have this > > problem under Windows, and so I would like to know from any Mac > > user that typesetts in languages other than english how I can solve > > this problem. > > Have you set the text encoding of TeXShop to UTF8? > > Best Oliver Hi Oliver, I had done that, and it wasn't working. I was still using teTex. I installed the new version of gwTex and it is working now. I had a hello of a nightmare to get it to work. Now, the only problem I am having is in TexShop. It processes the file without any problems, but it does not visualize it. The visualization window comes blank. But, if I open the pdf file externally with Adobe, it is ok. Anyone experienced this? Thanks! Fidel.

1 0