December 2007 - ntg-context - NTG Mailing Lists

Re: [NTG-context] how to change 'figure 1.1' to '?? 1.1' (Mojca Miklavec)
by Dalyoung Jeong 10 Dec '07

10 Dec '07

Dear Mojca, On Dec 8, 2007, at 3:35 AM, ntg-context-request(a)ntg.nl wrote: >> Yesterday, after I reinstalled TeXlive and updated ConTeXt, I got >> "kpathsea: >> Running mktextfm lmtypewriter10-regular " message. As a temporary >> method, I >> renamed mktextfm. > > Just change > MKTEXTFM = 0 > in texmf.cnf I am sorry that now I remembered what you said before about "mktextfm=0". I found it in the mail from you. After setting it, no error messages again. Thank you. lang-kor.tex is modified more by the help of people in KTUG. To make it more usable, I'd like to know a few things more. After defining \chapter in lang-kor, completecontent and completeindex follow the setup of chapter as following: "제 장 contents" or "제 no 장 index" (of course, contents and index are in korean) because \chpater{ch- title} produces in such a way, i.e., "제 ch-no 장 ch-title". But I'd like to write contents and indices in differently. I looked up \setupcombinedlist but I don't know how to make it happen. Is there any sample for this? Thank you. Best regards, Dalyoung

3 2

TeX ligatures in XeTeX/LuaTeX: ``who needs them''?
by Mojca Miklavec 10 Dec '07

10 Dec '07

Hello, just wondering: how many ConTeXt-ers depend on ligatures such as: '' (double quote) and '' (two single quotes) -> right double quote `` -> left double quote ,, -> DOUBLE LOW-9 QUOTATION MARK or even more weird ones: !` -> inverted exclam ?` -> inverted question << -> LEFT POINTING GUILLEMET (never heard of that ligature) >> -> RIGHT POINTING GUILLEMET Some ligatures are handy indeed: -- -> endash --- -> emdash ' -> right single quote (I'm, isn't etc.) I'm posting that question to get some feedback about which ones are expected to work/are fundamental for XeTeX & LuaTeX, so that others might be dropped from default additional font features (for third-party fonts). (I'm thinking about replacing tex-text in XeTeX with something: - more minimalistic - compatible with mkiv. Of course, users are still free to provide "tex-text" mapping explicitely as it's probably going to hang aound forever, together with XeTeX itself.) Mojca

7 12

showfont with xetex (syntax changed?)
by Steffen Wolfrum 10 Dec '07

10 Dec '07

Hi, when in february 2006 I asked for an alternative to fontspec that could show me opentype features, Adam wrote: I find that the lcdf typetools are a tremendous help: otfinfo -f ~/Library/Fonts/WarnockPro-Regular.otf and I can test the features with: \showfont["Warnock Pro: +smcp"] Today this showfont-line doesn't work anymore: \definetypeface[oneliner][rm][Xserif][Warnock Pro][default] \starttext \oneliner Test WQG 0196 \showfont["Warnock Pro: +smcp"] \stoptext Someone knows what to do? Thanks, Steffen

4 26

Re: [NTG-context] "Semi-verbatim" - preserve whitespace - don't escape character
by dexterclarke＠Safe-mail.net 09 Dec '07

09 Dec '07

> Wolfgang Schuster wrote: > > \startlines > verbatin text > \stoplines Thanks! That's almost perfect. I've noticed that space is still inserted after punctuation characters such as '.', ':' and '!'. Is it possible to disable this as well? I've read a little about category codes but I'm not entirely sure if that's what I should be using (perhaps ConTeXt provides a higher level macro for it?). __ dc

2 1

gobbling previous space
by Idris Samawi Hamid 09 Dec '07

09 Dec '07

Dear gang, For some macro writing, I need a low-level command that will gobble the space before it so that ========= Here is some text.% \mycommand ========= is equivalent to ========= Here is some text. \mycommand ========= without the %. I'm sure there's a context command for this hidden somewhere... Best Idris -- Professor Idris Samawi Hamid, Editor-in-Chief International Journal of Shi`i Studies Department of Philosophy Colorado State University Fort Collins, CO 80523 -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

2 1

"Semi-verbatim" - preserve whitespace - don't escape characters
by dexterclarke＠Safe-mail.net 08 Dec '07

08 Dec '07

Hi. I'm working on a document processor that has multiple backends for different output formats (XHTML, nroff, plain text, ConTeXt). The processor uses s-expression syntax with commands such as: (para "this is a paragraph") The various backends then convert this statement in their own way (using <p></p> tags in XHTML, for example). There is one command that allows rendering of external files based on whatever backend is selected: (render "file") The XHTML backend includes "file", escaping all 'illegal' characters such as <, >, & etc. The ConTeXt backend reads the file and also escapes characters, placing their TeX equivalent in the output - $\}$, $\backslash$ etc. Both backends place the contents of "file" directly in the output, they don't, for example, use the <object> tags in XHTML, or any ConTeXt file inclusion directives. This is desirable for many reasons that are out of scope for this post... The problem I am having is that one may do this: (para-verbatim (render "file")) The para-verbatim tag is meant to preserve whitespace in the output. For example, this becomes: <pre>contents of file</pre> in the XHTML output. Unfortunately, I've hit a wall when it comes to the ConTeXt equivalent: The ConTeXt backend reads in "file" and prints it to the output, escaping all reserved TeX characters, as mentioned earlier, but unfortunately there doesn't seem to be the equivalent of: \preservewhitespace contents of file \stoppreservingwhitespace "\starttyping" is too heavy handed in that it also escapes characters rather than just preserving whitespace (they've already been escaped by my document processor, as mentioned earlier). What I need is a directive that says "preserve whitespace" but does not escape reserved TeX characters. Does any such thing exist in ConTeXt? Unfortunately, I'm inexperienced with TeX so I don't know how feasible this is. -- dc

3 5

Howard Wilner - 1994 Ford Bronco
by Allison Wallock 08 Dec '07

08 Dec '07

Howard Wilner,The Ford Bronco is in the same category as Chevrolet's big Blazer and the GMC Yukon-somewhat aged but still selling to fans of the big, brawny V8powered four-wheelers. It's our impression that Ford has done a little more upgrading on the Bronco than either Chevrolet or GMC has done with its offerings. We tested an Eddie Bauer Edition and felt as though we just put on an old favorite pair of hunting boots. A word of caution: If you're looking for a 4WD sport utility to complement your suburban gentility, this probably isn't your vehicle. Bronco is a big, powerful off-roader that you have to clamber into. Although its road manners are tame enough, this vehicle is built for more than an occasional trip off the pavement. It also looks good. Like the Chevy K Blazer, the Bronco is a bit of a dinosaur. It's big, bulky, hard to climb into and somewhat outdated in looks and off-road chic. But the vehicle also has a staunch following who love its brawn, bulk and impressive power. Even on the most rugged trails of our test drive, the Bronco exhibited little body roll or choppiness. Add to this an interior that is comfortable, functional and pretty darn good-looking, and the package becomes even more attractive. http://automax-howardwilner.com/

3 2

bug in new context/luatex?
by zs 08 Dec '07

08 Dec '07

Hi all. This simple code causes context/luatex to freeze on my linux box. Could anyone reproduce it to make sure the problem is not on my side. \starttext \starttable[|c|c|] \NC \NC \NC\AR \DC\DL\DR \NC \NC \NC\AR \stoptable \stoptext This is LuaTeX, Version snapshot-0.20.0-2007120712 (Web2C 7.5.6) ConTeXt ver: 2007.12.06 22:52 MKIV fmt: 2007.12.7 int: english/english

4 7

problem with \setupcombinedlist[content][alternative=c]
by Peter Münster 07 Dec '07

07 Dec '07

Hello, With luatex-0.20.0 and ConTeXt-2007.12.6 the \completecontent is messed up and the first paragraphs are supressed: % engine=luatex \setupcombinedlist[content][alternative=c] \starttext \completecontent \dorecurse{10}{ \section{sec} \input tufte \subsection{subsec} \input tufte \subsection{subsec} \input tufte \subsection{subsec} \input tufte } \stoptext Cheers, Peter -- http://pmrb.free.fr/contact/

3 4

Re: [NTG-context] how to change 'figure 1.1' to '?? 1.1'
by Dalyoung Jeong 07 Dec '07

07 Dec '07

Dear Mojca and Wolfgang, Thank you for the comments on lang-kor.tex. > I didn't test, but I would say: forget the dirty hacks and simply > write > \setuplabeltext [\s!ko] [\v!figure=??] > It might not work in pdfTeX, but for XeTeX and LuaTeX it should do > the job. Once you do those changes, feel free to ask again if you > have problems (and don't forget to ask Hans to include the > translations). I modify the files following your advice. It removes the middle variable "\koencoding" and make the file simpler. And I don't need to use "\koencoding{\enableencoding[cjk- uni]}". It worked fine, also. But I'd like to use \setuphead for chapter, section, etc because our writing style of head is different from that of english. I uploaded it in KTUG board to be checked by them, since it may be need more corrections. Thank you again. By the way, do you completely resolve the "lmtypewriter10-regular" problem? which was discussed before in the list? Yesterday, after I reinstalled TeXlive and updated ConTeXt, I got "kpathsea: Running mktextfm lmtypewriter10-regular " message. As a temporary method, I renamed mktextfm. I confirmed that such font file is in texlive opentype font folder and lm*.map files in map/dvipdfm folder. Is there anything that I have to do more? I couldn't see the solution in the list. Thank you for reading. Best regards, Dalyoung

2 1