September 2005 - dev-context - NTG Mailing Lists

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

Re: [NTG-context] Some concerns about the ConTeXt license.
by Taco Hoekwater 06 Sep '05

06 Sep '05

Hi Brooks, Are you on the dev-context(a)ntg.nl list? If not, would you please subscribe? It would make communication about the contextgarden stuff easier ('talking' through the wiki's Talk pages is not optimal), and also the user mailing list is quite large and most people on it are beginners who should probably not be bothered with technical / development things too much. Is that ok? On the license: I believe the context license should essentially be the LPPL, and the two reasons why it is not currently are: 1) there was no usable LPPL when context first became public 2) Hans and I are unhappy with the word "LaTeX" in the name. Cheers, Taco

3 3

[Fwd: Re: LMs 0.99.0, i.e., 0.99.1]
by Hans Hagen 01 Sep '05

01 Sep '05

Hi, The latest latin modern ... shouldn't we make tfm's for our new dense encodings? 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 -----------------------------------------------------------------

3 3