March 2006 - ntg-context - NTG Mailing Lists

Re: [NTG-context] Uppercase headings
by Ville Voipio 31 Mar '06

31 Mar '06

> \setuphead[title] > [deeptextcommand=\WORD] > > Does that work? It does, it does!!!! You just saved my night. Can I send you a pint of beer somewhere? --- I tried finding more information about deeptextcommand, but all I found was a brief comment about deep hooks in the release notes (19-Jan-06). I can write something about this into Wiki, but that requires me to understand a bit more. Where do I start looking for? Thanks again, - Ville

2 2

bib module: broken link on ConTeXt Garden
by Renaud AUBIN 31 Mar '06

31 Mar '06

Hi, The following link is broken: http://tex.aanhet.net/bib/t-bib-2006.03.13.zip Question: Is there a beta or this module is the release (after beta) ?

2 1

new module: streams
by Thomas A. Schmitz 31 Mar '06

31 Mar '06

Dear all, as you may have seen in the lates release notes, ConTeXt has a new feature: we have now streams for even and odd pages that can be synchronized at certain points. This is useful for, e.g., typesetting bilingual books: have the original on the even pages, the translation on the odd pages, and synchronize at certain points. I was very tenacious about it, and Hans has been characteristically generous with his skills and his time and has implemented something. I'm sure if some of you are interested, we will be able to refine it. I am uploading a pdf-document displaying this new feature to our institute's website. Due to the system our university uses, it may take until tomorrow until it's really visible at http://www.uni- bonn.de/www/Philologie/Personal/Schmitz/Dateien.html It's a bilingual (Greek-German) edition of a number of Greek texts for my lecture course next semester. It's not perfect, but it shows how powerful this new feature is. Have a look at it; if anybody is interested in seeing the source code, just contact me, and I'll be happy to send it along. Just a very brief explanation, if you want to try this at home: In the module, Hans has suggested a few shortcuts to using it, so I have in the preamble of the document: \usemodule[streams] \def\StartCouple{\page\SwitchToNormal} \def\StopCouple {\SwitchToNormal \SynchronizeLeftAndRight \FlushLeftAndRight} \def\Original {\SwitchToNormal\SynchronizeLeftAndRight\SwitchToLeft} \def\Translation{\SwitchToRight} So you put the part of your document where synchronization should take place between \StartCouple and \StopCouple. After that , \Original and \Translation switches between even and odd pages. I know that several people on the list asked for a similar feature, and I'm very grateful to Hans for providing it. Best Thomas

2 1

Uppercase headings
by Ville Voipio 31 Mar '06

31 Mar '06

I started to edit an old document with capitalized headings. Making the headings was rather difficult (as can be seen on this list about a year ago), and now it seems to have broken again. I have: \setuphead[title] [page=yes, before={\strut\blank[5*big]}, after={\textrule\blank}, align=middle, style=\tfb, textcommand=\WORD ] This worked fine in the past. Not anymore: 8<--- ! You can't use `\relax' after \the. <recently read> \@sl@\@@pnstate \pushmacro ...ame \@sl@ \@@pushedmacro \endcsname \@@pushedmacro \endcsname #1 \makesectionformat ...macro \@@shortsectionnumber \let \@@shortsectionnumber... \rawreference ...veryreference \makesectionformat \writereference {#2} {\sec... <argument> ...\finalsectionnumber }{\asciititle }} }\fi \executeifdefi! Missing \endcsname inserted. <to be read again> \let \@@shortsectionnumber ...@EA \ifx \csname \??se #1 \c!ownnumber \endcsname \r... \makesectionformat ... \@@shortsectionnumber \let \@@shortsectionnumber \@@s... \rawreference ...veryreference \makesectionformat \writereference {#2} {\sec... <argument> ...\finalsectionnumber }{\asciititle }} }\fi \executeifdefined {\?... \douppercase ...rstoftwoarguments \edef \ascii {#1 }\edef \ascii {\expandafte... ... 8<--- Using the trivial solution (\uppercase) does not work because with a non-il1 regime it does not handle the accented characters (A umlat, O umlaut) correctly. I use UTF, as it contains all the characters I need. So, what has changed in the \WORD? It works \WORD{fine} within text but not in the headings. TIA, - Ville

3 3

Re: [NTG-context] Uppercase headings
by Ville Voipio 31 Mar '06

31 Mar '06

> it's nearly impossible to get this working for all features > (keep in mind that tex has no real feature to map font chars > to other font chars) esp those with special chars. I know this is not a trivial question due to the number of encodings and languages. However, what makes me a bit puzzled is that the following works fine: \title{\WORD{Text with åäö etc.} } So, the mechanism behind \WORD works well. It is just that I cannot figure out how to use it. I emphasize that it used to work fine even in the \setuphead definition, but that was with an old version (April '05). --- > works ok here (can you try the latest version - beta?) The version I am trying to use is rather a fresh one: TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005 texexec : TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005 texutil : TeXUtil 9.0.1 - ConTeXt / PRAGMA ADE 1992-2006 tex : unknown context : ver: 2006.03.25 13:21 cont-en : unknown cont-nl : unknown Has there been any change after that? If not, I could brew up a minimal example to illustrate the problem. BR, - Ville

1 0

Quotations
by Gerben Wierda 31 Mar '06

31 Mar '06

I use \startquotation and \stopquotation a lot. I would like to visually strengthen the quotations because some are pretty lengthy and a reader might forget that it is not me that is writing here. I have been thinking about applying a light grey background or a border of sorts (which should then be open at the top of bottom if the quotation flows over a page boundary. Can someone tell me how to do this? Thanks, G

2 1

\useURL and URL with spaces
by Tobias Burnus 31 Mar '06

31 Mar '06

Hello, I have an URL with spaces ("foo.cgi?opt=my options with spaces"). The URL link is ok ("\goto[url(...)]"), but the typeset URL (\url[...]) misses all the spaces. This is with 2006.03.23 09:57. Any idea how to fix this? Tobias

2 4

Re: [NTG-context] Problems with Standalone distribution
by wwl＠musensturm.de 31 Mar '06

31 Mar '06

> > First Problem (may be the mother of all the others): > > > > The Batch-Files 'cdemo.bat' and 'cscite.bat' are using for example > > "%~s1" for the first placeholder on the commandline. > > > > My Windowssystem (ME) doesn't understand this. > > > > Are there other Batch-Files that work on older commandoprozessors to > > download? > > > hm, not on my machine; you can try: > > @echo off > usr\local\context\cscite.bat The same problems with cscite.bat. As I said, I can change these two batch-files. But I am not shure if my problems derive from this. > (i dunno if there's a way to test if we run me) > > > A second question: > > > > There exists an directory 'usr\local\context\tex\texmf\texmf' which > > contains fontinformation to one single fontfamily 'cb'. > > > > Is this ok: 'texmf' under 'texmf'? And why ist this there? > > > thats a bug (i thought that i had solved it -) Should I move this subtree one level higher or delete it? Wolfgang

2 1

Problems with Standalone distribution
by wwl＠musensturm.de 31 Mar '06

31 Mar '06

Hallo! Some months ago I have downloaded 'mswincontext.zip'. There were a lot of Problems and I tried to solve them. I could finally compile some files. But then I get new problems and so I decided to start over and ask the list for help. First Problem (may be the mother of all the others): The Batch-Files 'cdemo.bat' and 'cscite.bat' are using for example "%~s1" for the first placeholder on the commandline. My Windowssystem (ME) doesn't understand this. Are there other Batch-Files that work on older commandoprozessors to download? A second question: There exists an directory 'usr\local\context\tex\texmf\texmf' which contains fontinformation to one single fontfamily 'cb'. Is this ok: 'texmf' under 'texmf'? And why ist this there? Wolfgang

2 1

modules on wiki
by Hans Hagen 31 Mar '06

31 Mar '06

Thi sis what we have: Archive: t-bib.zip - this on is ok creating: bibtex/ creating: bibtex/bst/ creating: bibtex/bst/context/ inflating: bibtex/bst/context/cont-ab.bst inflating: bibtex/bst/context/cont-au.bst inflating: bibtex/bst/context/cont-no.bst inflating: bibtex/bst/context/cont-ti.bst creating: doc/ creating: doc/context/ creating: doc/context/third/ creating: doc/context/third/bib/ inflating: doc/context/third/bib/bibmod-doc.pdf inflating: doc/context/third/bib/bibmod-doc.tex creating: tex/ creating: tex/context/ creating: tex/context/third/ creating: tex/context/third/bib/ inflating: tex/context/third/bib/t-bib.tex inflating: tex/context/third/bib/t-bib.xml inflating: tex/context/third/bib/bibl-ams.tex inflating: tex/context/third/bib/bibl-apa-de.tex inflating: tex/context/third/bib/bibl-apa-fr.tex inflating: tex/context/third/bib/bibl-apa.tex inflating: tex/context/third/bib/bibl-aps.tex inflating: tex/context/third/bib/bibl-num-fr.tex inflating: tex/context/third/bib/bibl-num.tex inflating: tex/context/third/bib/bibl-ssa.tex Archive: t-bnf.zip - just bnf, no t-nbf subpath - funny AUTHORS README NEWS file, should go to the doc path don't use'=' in filenames, use lowercase (to avoid problems and inconsistencies), maybe we need to cook up some format, see below creating: doc/context/third/t-bnf/ inflating: doc/context/third/t-bnf/=AUTHORS inflating: doc/context/third/t-bnf/=NEWS inflating: doc/context/third/t-bnf/=README inflating: doc/context/third/t-bnf/t-bnf.pdf creating: tex/context/third/t-bnf/ inflating: tex/context/third/t-bnf/t-bnf.tex Archive: t-construction-plan.zip - remove t- from subpath - move pdf file + example to doc path creating: doc/context/third/t-construction-plan/ inflating: doc/context/third/t-construction-plan/example.pdf inflating: doc/context/third/t-construction-plan/t-construction-plan.pdf creating: tex/context/third/t-construction-plan/ inflating: tex/context/third/t-construction-plan/t-construction-plan.tex Archive: t-degrade.zip - remove t- from subpath - move pdf file + example to doc path creating: doc/context/third/t-degrade/ inflating: doc/context/third/t-degrade/example.pdf inflating: doc/context/third/t-degrade/t-degrade.pdf creating: tex/context/third/t-degrade/ inflating: tex/context/third/t-degrade/t-degrade.tex Archive: t-french.zip - remove t- from subpath - move pdf file + example to doc path - what is the pdf file doing there? creating: doc/context/third/t-french/ inflating: doc/context/third/t-french/example.pdf inflating: doc/context/third/t-french/t-french.pdf creating: tex/context/third/t-french/ inflating: tex/context/third/t-french/t-french.tex Archive: t-greek.zip - no REAMDME inroot, use lowercase - no zip inside zip - remove t- from subpath - ect inflating: README.txt extracting: texmf.zip Archive: t-layout.zip - what is the pdf file doing there creating: doc/context/third/t-layout/ inflating: doc/context/third/t-layout/t-layout.pdf creating: tex/context/third/t-layout/ inflating: tex/context/third/t-layout/t-layout.tex Archive: t-lettrine.zip - doc path creating: doc/context/third/lettrine/ inflating: doc/context/third/lettrine/lettrine.pdf inflating: doc/context/third/lettrine/lettrine.tex inflating: doc/context/third/lettrine/W.pdf creating: tex/context/third/lettrine/ inflating: tex/context/third/lettrine/t-lettrine.tex inflating: tex/context/third/lettrine/t-lettrine.xml Archive: t-lilypond.zip - pdf file? - remove t- from subpath creating: doc/context/third/t-lilypond/ inflating: doc/context/third/t-lilypond/t-lilypond.pdf creating: tex/context/third/t-lilypond/ inflating: tex/context/third/t-lilypond/t-lilypond.tex Archive: t-rsteps.zip - remove t- from subpath creating: tex/context/third/t-rsteps/ inflating: tex/context/third/t-rsteps/t-rsteps.tex how about the following: - either we use t-name or name as subpath, but we need to be consistent and since only t-'s go there, we can omit the t- from the path - only store runtime files in context/third/somename - always provide an doc path - put a file t-somename.xml in the tex path that looks like: <module> <title>verbose title</title> <version></version> <authors> <author></author> <author></author> </authors> <copyright> </copyright> <description> </description> <installation> </installation> </module> (plus some basic x-contml stuff) or whatever we can agree on, but at least let's cook up a format that can be parsed (the wiki already has something like that to generate the modules pages, i dunno the format) 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