- ntg-context - Mailing Lists

tex vs etex
by Hans Hagen 05 Aug '05

05 Aug '05

Hi, Is anyone using tex i.e. not pdfetex/aleph/xetex? I'd likt to go etex only which in the end is needed anyway since we run out of token list registers (in etex more we're already past 255) 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

mapping
by Hans Hagen 04 Aug '05

04 Aug '05

Hi, I'm a bit puzzled. Do you really get properly uppercased output while the mapping are actually wrong? With fixed mapping, \WORD works ok, which si actually what i expect because utf is fully expandabel to \namedglyphs which, givven the proper encoding, expand to characters, which can be uppercases. 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

enumerated lists
by Frank Grieshaber 04 Aug '05

04 Aug '05

Dear all, I have a manuscript with long nested numbered enumerations and I want the numbers of all levels to be printed like: 1. one 1.1 one-one 1.2 one-two 2. two 2.1 two-one 2.2.1 two-two-one ... Using the following prints only the current level's number, not all levels: \startitemize[n,packed] \item \item \startitemize[m,packed] \item \item \stopitemize \item \item \stopitemize For Latex there is the package paralist.sty for doing the desired numbering, how can this be done with ConTeXt? Frank

6 6

Re: [NTG-context] uppercasing accented characters, mappings and \WORD
by Mojca Miklavec 04 Aug '05

04 Aug '05

Taco Hoekwater wrote: > > This works (but it is a bit ugly) > > \def\WORD#1{% > \bgroup > \the \everyuppercase > \let \smallcapped \firstofoneargument > \let \WORD \firstofoneargument > \pushmacro \dohandleaccent > \pushmacro \dohandlecommand > \pushmacro \dohandlecharacter > \keepencodedtokens > \edef\tempa{#1}% > \popmacro \dohandleaccent > \popmacro \dohandlecommand > \popmacro \dohandlecharacter > \expandafter \uppercase \expandafter {\tempa}% > \egroup } Thank you, Taco! I cannot judge about the elegance of the solution as I have never seen any elegant TeX macro definitions :), but it works (at least on my examples) which is the most important part. Also the cp1250 regime (where no mappings were defined) is now happy with it :) Just for fun, I also tried it on greek (just copy-pasted some letters from http://www.unics.uni-hannover.de/nhtcapri/multilingual1.html) It doesn't work there, but I didn't even expect it to work as I should probably provide the proper fonts and encodings first anyway. I've seen some strange Greek stuff a while ago, which could have been definitions of capitals, but as I neither understand Greek nor "TeX", I can't judge about it. > do you have a zipped example? Is this still relevant? Well, as it was only 11kb, I attached it anyway. Thank you, Mojca

2 1

encoding comparison table
by Patrick Gundlach 04 Aug '05

04 Aug '05

Hi there, I have set up a small toy for those interested in TeX encodings: http://fun.contextgarden.net/encodingtable/enctable.rb?ec,texnansi,8r,8a You can change the table by selecting different arguments to the http query. Enjoy, Patrick (just a quick hack, so is not beautiful) -- ConTeXt wiki and more: http://contextgarden.net

2 1

uppercasing accented characters, mappings and \WORD
by Mojca Miklavec 04 Aug '05

04 Aug '05

Hello, If I use the latin2 encoding (il2), \WORD works OK if I simply type accented characters. Under UTF-8, uppercasing \zcaron also works OK, but fails if I simply type 'ž'. I saw the \definemapping[il2] and I can write a mapping for windows-1250 regime as well, but how exactly is this done for unicode, where the character codes exceed 255? Could perhaps alternatively \WORD, \defineactivetoken or any other part of code be extended, so that \WORD would be happy with the typed accented characters as well? \Zcaron is already defined somewhere to be the uppercased \zcaron, so defining the same for every single regime/encoding manually seems redundant and error-prone. Thank you, Mojca (I don't have any editor to support latin2 under windows (except Mozilla), even for unicode vim and Windows are fighting against each other, so windows-1250 is the only reasonable thing that I can use comfortably.)

3 4

Antwort: Re: [NTG-context] Presentation
by Jessica Holle 04 Aug '05

04 Aug '05

Hey, thanks for this information :-) I will look after these things to build my own presentations. Greetings Jessica

1 0

Presentation
by Jessica Holle 04 Aug '05

04 Aug '05

Hi, I've searching for a dokumentation how to build a presentation, like in Powerpoint but better :-) with ConTeXt. I haven't found somethink in the PDF's on the Pragma page and on the Wiki. Only the Raw Steps module, which I doesn't understand. Has somebody information to this theme? Greetings Jessica

5 5

XY arranging ignores dx/dy
by Angus Lees 04 Aug '05

04 Aug '05

The XY arranging macro basically ignores dx/dy parameters by always padding out the space between "pages". Here's the existing ConTeXt macro for reference - removing \vss and \hss makes it do the right thing (imo). I'd give a simple patch, but I think the ideal behaviour might be to pad if (and only if) dx/dy were not specified, which is starting to push my TeX skills. \def\pusharrangedpageXY#1% {\doglobal\increment\arrangedpageN \reportarrangedpage\arrangedpageN \doglobal\increment\arrangedpageM \global\setbox\arrangedpageB\hbox \ifdim\@@ppwidth>\zeropoint to \@@ppwidth \fi {\ifvoid\arrangedpageB\else \unhbox\arrangedpageB\hss\hskip\@@ppdx\hss \fi \box#1}% \ifnum\arrangedpageM<\arrangedpageX\else \global\setbox\arrangedpageA\vbox \ifdim\@@ppheight>\zeropoint to \@@ppheight \fi {\offinterlineskip \ifvoid\arrangedpageA\else \unvbox\arrangedpageA\vss\vskip\@@ppdy\vss \fi \box\arrangedpageB}% \doglobal\newcounter\arrangedpageM \fi \ifnum\arrangedpageN<\arrangedpageT\else \poparrangedpages \fi} Minimal test, note the dx/dy distances: \definepapersize[label][width=30mm,height=20mm] \setuppapersize[label][A4] \setuppaper[dx=1mm,dy=1mm,nx=2,ny=6] \setuparranging[XY] \showframe[edge] \starttext \dorecurse{6}{test \recurselevel \page} \stoptext -- - Gus

1 0

Scite spelling support
by Willi Egger 03 Aug '05

03 Aug '05

Hi Hans, Yesterday I installed the support files you provided on the website. Interesetingly it worked with the version 1.62 of Scite. But not with version !.64 which I downloaded today. Though there are the CTX menue lines in the tools menue I can't get the spellchecker working. Anlike in the older version 1.62. There are no messages during starting Scite. So I am a bit puzzled. During my first tests with the older 1.62 Version I collected some remarks: Uk-wordlist Caps at the beginning of a word are not recognized e.g. "The" is underlined red indicating an error. The section "m" is uncomplete in the spell-uk.txt. It ends with meningo... NL-word-list The word "rug" misses in the Dutch word-list Dutch words are not recognized when starting with a capital letter. e.g. Betreft The article "de" misses in the Dutch word-list. Althogh the "De" is not recognized it is also not underlined with red. At line 8904 in de word-list: d\'eg‚n‚r‚ - Meaning? The word "mag" is not included in the Dutch word-list Otherwise it looks like we will have a nice tool! Willi

4 16