- dev-context - NTG Mailing Lists

Re: [NTG-context] footnote numbering
by Adam Lindsay 26 Sep '05

26 Sep '05

[switched to dev-context for test case discussion] Idris Samawi Hamid said this at Mon, 26 Sep 2005 12:14:50 -0600: > \incrementnumber[footnote] Hmm. I was playing with that command, and couldn't get it to work, because of my particular test case. Is it a bug? \starttext \title{Title\footnote{test}} \incrementnumber[footnote] \incrementnumber[footnote] Test\footnote{test} \stoptext -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. atl(a)comp.lancs.ac.uk Lancaster University, InfoLab21 +44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

1 0

showmathcharacters
by Adam Lindsay 21 Sep '05

21 Sep '05

Is it just me, or does \showmathcharacters get into a loop? tex : pdfeTeX, 3.141592-1.21a-2.2 (Web2C 7.5.4) context : ver: 2005.09.14 (was with 2005.08.19, upgraded to latest beta. Will update pdftex via gwTeX...) \starttext \showmathcharacters \stoptext -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. atl(a)comp.lancs.ac.uk Lancaster University, InfoLab21 +44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

1 0

Typesetting ConTeXt modules?
by Brooks Moses 20 Sep '05

20 Sep '05

Hello! How does one go about converting ConTeXt module files (such as syst-ext.tex and so forth) into typeset documentation? I saw the modules.zip file that Luigi Scarso uses to create his modules.pdf file, here: http://wiki.contextgarden.net/User:Luigi.scarso/modules.pdf But that seems to rely on something else converting the .tex file from the module into a .ted file, and I haven't been able to figure that out on my own.... - Brooks

2 1

Re: [NTG-context] Switching to smaller font more thoroughly
by Taco Hoekwater 19 Sep '05

19 Sep '05

Hi, This sounds like a bug. (there is no point in having a switch if you cannot safely turn it off) Taco Giuseppe Bilotta wrote: > > No, it was because I had disabled \preloadfonts. > Interesting. Is this intentional or unintended? It would > seem that without preloadfonts math never gets properly > initialized. >

1 0

Determining the current text style?
by Brooks Moses 12 Sep '05

12 Sep '05

Hi! I'd like to write some macros that do different things depending on the style of the current font. That is, \mymacro in this example \mymacro {\bf \mymacro} {\it \mymacro} should be able to do something different in each of those three cases. I remember seeing a bit of clever code in a recent message that could test whether or not it was being used in a region of typewriter font and adjust accordingly; are there similar tests that can be used for \bf, \it, and so forth? If so, what are they? (And how reliable are they?) (For those who are curious, I'm thinking about this for the LaTeX-compatiblity code I'm writing. LaTeX's \itshape command will select \it in normal font, but \bi in boldface font. LaTeX handles this by defining extra flags to keep track of the current style, but I'd like to avoid doing that if I don't need to.) Thanks, - Brooks

3 2

Re: [NTG-context] new beta
by Taco Hoekwater 08 Sep '05

08 Sep '05

Hans Hagen wrote: > Hi, > > I'm uploading a beta. I replaces a few font things, i.e. il2 and pl0 > support is now replaced by a combination of regimes and using ec and qx. > > Also, given that up install the latest latin modern zip, you can have > condensed monospaced fonts: Hans, what is the status of the zip? Does it now contain the full distribution, including the latex/dvips support files? > I'd like to see the new dense encoding (discussed on dev list) being > supported as well, but we need to generate metrics for that (can be donw > with metatype tools) I suspect that the 'euro-letter' encoding is somewhat hard to use without a companion 'euro-symbol' encoding and possibly some extra macros to hide the fact that some bits of ascii are not readily available. Pasted from an earlier message: > "quotedbl" , "numbersign", "dollar", "percent", > "ampersand", "asterisk", "plus", "less", > "greater", "backslash", "asciicircum", > "underscore", "braceleft", "bar", "braceright", > "asciitilde" " # $ % & * + < > \ ^ _ { | } ~ While these are unlikely to appear in prose, they are very normal characters inside e.g. urls, filenames and program code (standard macros like \# need to be updated as well). Taco

3 5

Re: some highlighted \type-ing
by Mojca Miklavec 08 Sep '05

08 Sep '05

Taco Hoekwater wrote: > This makes comments behave like PI instructions, but maybe > you want the entire comment grey, including the leading > '<!' and trailing '>' ? > That would be require a much larger patch though. > ... Taco, thank you for the patch. But I figured out that those pieces of code are not human-readable (human-modifiable) and it's stupid to ask for help for every single character that one would like to change. I played a bit, just removed 80% of the stuff from 2html.vim (another 15% still waiting to be removed, I just wanted to try to test the code) and changed three lines or so to produce ConTeXt-friendly output. (http://pub.mojca.org/tex/vim/syntax/, you have to move 2context.vim to syntax folder and say :runtime! syntax/2context.vim) To test it I opened a simple file: <html> <body> My testfile: <img src="something.abc"> </body> </html> which resulted in: \HiSyntax[Identifier]{<}\HiSyntax[Statement]{html}\HiSyntax[Identifier]{>} \HiSyntax[Identifier]{<}\HiSyntax[Statement]{body}\HiSyntax[Identifier]{>} \HiSyntax[]{ My testfile: }\HiSyntax[Identifier]{<}\HiSyntax[Statement]{img}\HiSyntax[Identifier]{ }\HiSyntax[Type]{src}\HiSyntax[Identifier]{=}\HiSyntax[String]{"something.abc"}\HiSyntax[Identifier]{>} \HiSyntax[Identifier]{</}\HiSyntax[Statement]{body}\HiSyntax[Identifier]{>} \HiSyntax[Identifier]{</}\HiSyntax[Statement]{html}\HiSyntax[Identifier]{>} (sorry, slighlty unreadable, but the file is on the above mentioned link as well) Now two questions: 1. How should the output syntax look like and which exceptions should be considered? It's pretty trivial to replace braces with \} or \rightbrace or whatever, tabs by spaces (if requested), ... but I don't know at which level it is better to do that (to replace characters within the script or to change charcodes as in verbatim ...) Input text can probably be just everything that comes to someone's mind. 2. (I don't need the answer yet since I have to play a bit with the script first, I'll ask later once more.) How can I call vim, execute a couple of commands there and somehow "return" the ConTeXt code back? % lots of settings ... \definetyping[HTML][option=HTML] \setuptyping[mode=vim] % or engine=vim or ? % option would be passed on to vim with ":set syntax=\c!option" \startHTML <html> <body> abc </body> </html> \stopHTML Thank you, Mojca

1 0

encodings
by Hans Hagen 08 Sep '05

08 Sep '05

Hi, I added a new command \showpatterns which produces a table of loaded patterns; btw, czech and polish need testing since we move to latin modern exclusively (pl0 an il2 are only used for plr and csr fonts so we may as well drop loading patterns for these encodings; user can use regimes which will then map onto qx and ec) 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 -----------------------------------------------------------------

1 0

[Fwd: Re: [dev-context] Re: [NTG-context] new beta]
by Hans Hagen 08 Sep '05

08 Sep '05

1 0

Wiki Text Problems.
by Brooks Moses 07 Sep '05

07 Sep '05

(Taking Taco's suggestion, and mentioning this here rather than trying to converse on the Wiki's talk pages.) Patrick, Mojca, Taco, and other Wiki-people: The rendered text on the Wiki has suddenly become ugly -- letters are thinner (too thin!), and the edges of the text are a bit ragged. My guess is that this is a result of the interaction between anti-aliasing and setting the transparency to true -- everything that was anti-aliased to gray is now also set transparent, and thus becomes white when displayed. I don't know if this is browser-dependent or not, but it's repeatable in both Opera and Firefox, on my (Windows) computer. Given this problem, I would recommend reverting to the non-transparent version. - Brooks

4 12