- ntg-context - Mailing Lists

Footer issue
by Diego Depaoli 05 Jun '08

05 Jun '08

Hi all, why \setupheader[text][after=\thinrule] and \setupfooter[text][before=\textrule] both work, but \setupfooter[text][before=\thinrule] doesn't work? Cheers -- Diego Depaoli

2 3

Re: [NTG-context] several warnings after updating ConTeXt and LM fonts
by Dalyoung Jeong 04 Jun '08

04 Jun '08

Dear Mojca, Thank you for your instruction. After updating XeTeX binaries, warnings are disappeared but a new one. ** WARNING ** Could not open config file "dvipdfmx.cfg". I added the line "TEXFONTSMAPS.dvipdfmx = .;$TEXMF........" in texmf.cnf below the line TEXFONTSMAPS = .;$TEXMF/Font/,ap/..." However, the same warning message still remains. I checked the lm-math.map and lm-rm.map in the folder ../dvipdfm/ context/ as Wolfgang suggested. They are there. How to remove this new warning message? Thank you again. Best regards, Dalyoung

2 1

xml in mkiv
by Hans Hagen 03 Jun '08

03 Jun '08

Hi, [if you never use xml or don't use mkiv, you can skip this message] Currently in mkiv, the mkii method of xml is active at the same time; however, this is not always what you want and eventually i suppose that mkiv xml usage will replace mkii usage (i'm thinking of at some point making the old stream based xml method a module for mkiv) anyhow, one of aspects we need to deal with is mixed usage of documents, more about that later the latest beta has a \setupxml command with the following options (there are a few more): \setupxml[\c!method=mkii] % mixed mkiv and mkii \setupxml[\c!method=mkiv,\c!default=] % mkiv only \setupxml[\c!method=mkiv,\c!default=\v!none] % mkiv only, undefined -> hidden \setupxml[\c!method=mkiv,\c!default=\v!text] % mkiv only, undefined -> text the tricky part is in dealing with entities. By default entities are resolved to utd code, which means that <, > and & are part if the normal text stream. This is tricky because in mkii a dangling < or & gives an error. However, in mkii mode (i.e. mixed mode), these three characters are remapped to some place safe (the location in the unicode table will change once we have active chars in the private planes). i used this test: % \defineXMLenvironment[y]{(}{)} % % \startxmlsetups x % /\xmlflush{#1}/ % \stopxmlsetups % % \startxmlsetups xx % \xmlsetsetup{main}{x}{*} % \stopxmlsetups % % \xmlregistersetup{xx} % % \startbuffer % <x>a <&><y>{b}</y> c</x> % \stopbuffer Another change is that 'context --env=bla whatever.xml' will use mkiv xml mode unless the --mkii flag is passed. The alternative is rather ugly and tricky overloading of the traditional XML macros, an option that i rejected. An example that demonstrates mkiv usage is: context --ctx=x-ldx l-dimen.lua this will produce the documentation of l-dimen.lua and does a transformation as defined in the ctx file. Eventually all those texexec goodies (--pdfwhatever) will become such scripts combined with styles. Much is experimental and I will add more control over specific documents. Take for instance (from x-ldx.tex): \usemodule[mathml] \xmlregisterdocumentsetup{ldx}{xml:mml:define} \xmlregisterdocumentsetup{ldx}{xml:ldx:define} \xmlregisterns{ldx}{ldx} \startxmlsetups xml:ldx:define \xmlgrab {\xmldocument} {ldx:*} {*} \stopxmlsetups This associates the ldx definitions to the document but also mathml. I'm converting all traditional xml handling used in the core into mkiv handling (e.g. clt handling is already converted; clt deals with remapping filesnames into the ones that come out of preprocessing, as for instance in the ldx module). 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

typebuffer extra line
by Hans van der Meer 03 Jun '08

03 Jun '08

Exercising \typebuffer gives an extra blank line afterwards. See the following minimal example. How can I prevent this extra line? Using: ConTeXt ver: 2008.05.21 15:21 MKII fmt: 2008.5.24 int: english/english Example: \startbuffer[A] Contents of buffer A. \stopbuffer \startbuffer[B] Contents of buffer B. \stopbuffer \starttext \typebuffer[A]\typebuffer[B] \stoptext Output: Hans van der Meer

3 2

TeX capacity exceeded
by M.guravage 03 Jun '08

03 Jun '08

Greetings, While updating my minimal ConTeXt instance from version 2008.01.28 to 2008.05.21, the pdftex formats failed to build with the error: "./texmf-linux/web2c/pdftex/cont-en.log:! TeX capacity exceeded, sorry [pattern memory=250000]." Has anyone else experienced this, and can you suggest a correction? Thanks for your help. With kind regards, Michael A. Guravage

2 1

several warnings after updating ConTeXt and LM fonts
by Dalyoung Jeong 03 Jun '08

03 Jun '08

Dear all, Recently, I updated ConTeXt using "ctxtools". I also install latest LM otf fonts and some map file for dvipdfm. After teshashing and creating formats, I tried a simple file. It worked well in ConTeXt, but in XeTeX+ ConTeXt, I got several warnings related with map files as following. However, I got a PDF output. How do I remove those warnings? I am using TeXlive(MacTeX). Thank you Best regards, Dalyoung stdin -> newinstall.pdf [1 ** WARNING ** This .map file looks like a dvips format fontmap file. ** WARNING ** -- Current input buffer is: rsfs7 rsfs5 <rsfs7.pfb ** WARNING ** -- Reading fontmap file stopped at: file="original- base.map", line=3. ** WARNING ** This .map file looks like a dvips format fontmap file. ** WARNING ** -- Current input buffer is: lmbsy5 LMMathSymbols5- Bold "enclmmathsy ReEncodeFont" <lm-mathsy.enc <lmbsy5.pfb ** WARNING ** -- Reading fontmap file stopped at: file="lm-math.map", line=7. ** WARNING ** This .map file looks like a dvips format fontmap file. ** WARNING ** -- Current input buffer is: rm-lmb10 LMRomanDemi10- Regular "enclmrm ReEncodeFont" <lm-rm.enc <lmb10.pfb ** WARNING ** -- Reading fontmap file stopped at: file="lm-rm.map", line=7. ** WARNING ** This .map file looks like a dvips format fontmap file. ** WARNING ** -- Current input buffer is: ucrb8t NimbusMonL- Bold <ec.enc <ucrb8a.pfb ** WARNING ** -- Reading fontmap file stopped at: file="ec-base.map", line=3. ** WARNING ** This .map file looks like a dvips format fontmap file. ** WARNING ** -- Current input buffer is: qcrb <qcr.enc <qcrb.pfb ** WARNING ** -- Reading fontmap file stopped at: file="qx-base.map", line=3. ** WARNING ** This .map file looks like a dvips format fontmap file. ** WARNING ** -- Current input buffer is: ucrr8v VnNimbusMonL- Regu "T5Encoding ReEncodeFont" <t5.enc <ucrr8v.pfb ** WARNING ** -- Reading fontmap file stopped at: file="t5-base.map", line=3. ** WARNING ** This .map file looks like a dvips format fontmap file. ** WARNING ** -- Current input buffer is: ucrb8r NimbusMonL- Bold <8r.enc <ucrb8a.pfb ** WARNING ** -- Reading fontmap file stopped at: file="8r-base.map", line=3. ** WARNING ** This .map file looks like a dvips format fontmap file. ** WARNING ** -- Current input buffer is: lasy5 LASY5 <lasy5.pfb ** WARNING ** -- Reading fontmap file stopped at: file="original-ams- base.map", line=1. ** WARNING ** This .map file looks like a dvips format fontmap file. ** WARNING ** -- Current input buffer is: euex10 EUEX10 <euex10.pfb ** WARNING ** -- Reading fontmap file stopped at: file="original-ams- euler.map", line=1. ** WARNING ** This .map file looks like a dvips format fontmap file. ** WARNING ** -- Current input buffer is: cmb10 CMB10 <lm-rep- cmrm.enc <lmb10.pfb ** WARNING ** -- Reading fontmap file stopped at: file="original- public-lm.map", line=68. ] 4818 bytes written Output written on newinstall.pdf (1 page). Transcript written on newinstall.log. TeXUtil | parsing file newinstall.tui TeXUtil | shortcuts : 169 TeXUtil | expansions: 308 TeXUtil | reductions: 0 TeXUtil | divisions : 0 TeXUtil | loaded files: 1 TeXUtil | temporary files: 0 TeXUtil | commands: 21 TeXUtil | programs: 0 TeXUtil | tuo file saved TeXExec | runtime: 5.159215

2 1

Correction for \getbuffer
by Wolfgang Schuster 02 Jun '08

02 Jun '08

Hi Hans, The definition for \getBUFFER need to be changed because it use the undefined command \dodoprocessTEXbuffer. \def\dodefinebuffer[#1][#2]% {\iffirstargument % else problems \doglobal\increment\nofdefinedbuffers \letvalue{\??bu#1\c!number }\nofdefinedbuffers \letvalue{\??bu#1\c!paragraph}\v!no \setevalue{\e!start#1}{\noexpand\dostartbuffer [#1][def-\nofdefinedbuffers][\e!start#1][\e!stop#1]}% %\setevalue{\e!get #1}{\noexpand\dodoprocessTEXbuffer[#1][def-\nofdefinedbuffers]}% \setevalue{\e!get #1}{\noexpand\dogetbuffer [#1][def-\nofdefinedbuffers]}% \setevalue{\e!type #1}{\noexpand\dotypebuffer [#1][def-\nofdefinedbuffers]}% \getparameters[\??bu#1][#2]% \fi} Greetings Wolfgang

2 1

standardmakeup, frontmatter, bodymatter & page numbering
by Mojca Miklavec 02 Jun '08

02 Jun '08

Hello, I have a document consisting of title page, some introduction which should have pages numbered with roman numerals, and finally the real content \setuphead[subject][page=odd,style=\ss\bfb] \setuppagenumbering[location=] \starttext \startstandardmakeup title page \stopstandardmakeup \startfrontmatter \setuppagenumbering[conversion=romannumerals] \setupfootertexts[page \pagenumber{}] \subject{some intro pages} \input tufte \stopfrontmatter \startbodymatter \setupfootertexts[page \pagenumber{} of \totalnumberofpages] \dorecurse{10}{\subject{real content} \dorecurse{\recurselevel}{\input knuth} } \stopbodymatter \stoptext Now the problems: 1.) The second page starts counting at 1, while counting should start at page 3. This can be solved by using another \startstandardmakeup\strut\stopstandardmakeup. 2.) The last page says "page 26 of 27" - the total page number is indeed 27, but counting started on the second page, so it never reaches the last number. 3.) I would like the page number on the first page of bodymatter to be "page 1 of 23" instead of "page 4 of 27", and the last one to ge "page 23 of 23" instead of "page 26 of 27" There is some way=bychapter setting for page numering, but in that case there are no suitable chapters/sections available. Any hints appreciated ... Thanks a lot, Mojca

4 13

Buffers and commands with optional arguments
by Wolfgang Schuster 02 Jun '08

02 Jun '08

Hi Hans, I got yesterday a bug report for my letter module if the \startletter command takes no arguments. The following example show the problem without the module. \def\startletter {\dosingleempty\dostartletter} \def\dostartletter[#1]% {\dostartbuffer[letter][startletter][stopletter]} \starttext % This did work \startletter Text \stopletter \getbuffer[letter] % But this did create a error message from TeX \startletter Text \stopletter \getbuffer[letter] \stopletter One solution for the second text can be solved when I add a \relax after the \startletter command but I wanted a better solution. Because TeX mentions \flushbufferline in error message I tried to modify the macro and came to the following solution. %\def\flushbufferline#1% \long\def\flushbufferline#1% {\iftmpblockstarted \ifsegmentatebuffer \ifemptybufferline \immediate\write\tmpblocks{\string\stopbufferparagraph }% \immediate\write\tmpblocks{\string\startbufferparagraph}% \else \immediate\write\tmpblocks{#1}% \fi \else \immediate\write\tmpblocks{#1}% \fi \else \doifsomething{#1} {\tmpblockstartedtrue %\immediate\write\tmpblocks{\string#1}}% \immediate\write\tmpblocks{#1}}% \fi} The macro has to be defined as long and the \string in the \write command has to be removed. I made a few short tests and saw no negative sideeffects from my changes. Another problem could arise with a few commands in the letter environment if no empty line is written after \startletter. The following result also in a error message. \startletter \dorecurse{2}{\input knuth\par} \stopbuffer With another modification of \flushbufferline also this example could work, my final patch was now: \long\def\flushbufferline#1% {\iftmpblockstarted \ifsegmentatebuffer \ifemptybufferline \immediate\write\tmpblocks{\string\stopbufferparagraph }% \immediate\write\tmpblocks{\string\startbufferparagraph}% \else \immediate\write\tmpblocks{#1}% \fi \else \immediate\write\tmpblocks{#1}% \fi \else \convertargument#1\to\ascii %\doifsomething{#1} \doifsomething\ascii {\tmpblockstartedtrue %\immediate\write\tmpblocks{\string#1}}% %\immediate\write\tmpblocks{#1}}% \immediate\write\tmpblocks{\ascii}}% \fi} Could my seond or at least my first patched version of the \flushbufferline macro integrated into core-buf.mkii because I won't force users of my letter module to put a \relax after \startletter only because they use MkII. Greetings Wolfgang

2 6

InDesign/InCopy vs. TeX and friends
by Charles P. Schaum 01 Jun '08

01 Jun '08

I would say that TeX is a way in which a mathematician / theoretical computer scientist that is well-steeped in music, languages, art, literature, and other areas might approach the issue. InDesign is the way in which a large number in the design community might approach the issue. I use mainly InCopy because I'm an editor, but I work closely with the designers. Here's a few things I see that could stand some improvement: 1. What does it mean to have either an overfull hbox or vbox? You might think, duh! But overfull boxes and copyfitting issues are not sets of the same cardinality or topology in the problem domain. First of all, some do make a distinction between intraword and interword spacing, although this need not necessarily be made. It does become helpful, however, when setting Sperrdruck and noting the rules for commas, periods, etc. The soul package in LaTeX does well here, although if there were essentially two realms, intraword and interword, with different letterspacing controls for each, this could result in the following solution: If (overfull hbox) then Apply an algorithm taking into account aesthetic rules for adjusting intra- and interword spacing within tolerance n and produce a warning that says either: Spacing adjusted to fit copy in hbox on line nnnn or Copyfit warning for hbox in line nnnn Similarly, leading (interline spacing) ought to be considered, but horizontal spacing, especially when pagefitting copy to avoid widows and orphans, can be tied with interline spacing to get the desired result. Tweaking the font size is generally a poor solution. Boxes and glue is good if you are modeling classical typesetting. I believe that is what DEK was shooting for. In 1978, that made good sense because electronic means were not well-defined and were sometimes quite displeasing. For modern digital needs, boxes and glue may not be appropriate in every situation. InDesign and InCopy simply pop up a warning when you have copyfitting issues. Still, there must be a standard approach when a designer fixes such issues (apart from an editor doing some rewording) in order to give one's products a good look and feel. Even with InDesign, copyfitting issues are not a no-brainer. That's where generating a preview that would step through copyfitting issues and allow input for heuristics might be helpful. 2. The box or the text frame? Ever use LaTeX and BibTeX to do a bib and footnotes and all of a sudden your URLs go right off the line? How annoying is that? The text frame should have priority over the boxes in it and should trigger copyfitting rules to enforce that priority unless locally or globally suppressed. 3. Multi-author workflow InCopy works with InDesign to allow an editor to work with a "story" that may be in one text frame or spread over multiple frames. It allows check-out and check-in of a story and locks the story when checked out. Of course, this implies that the workflow happens off a central server. Nevertheless, this allows the document to be constructed in parallel with designers, substantial/copy editors, proofreaders, and so on working on different parts as needed. TeX may be batch-oriented, but it is also single-user oriented unless you have a master with lots of linked input. The problem is that InCopy and InDesign can show you your work in relation to the whole, giving a better idea of what you need to do to fit your work in harmony with the others. TeX cannot do that. 4. TeX is still better at some things. Kinda like GraphViz, TeX has its area where it just shines. Those schemata that I was doing are a major pain to do in something else. TeX's ability to intermix math mode and regular mode is probably unique. I would bet that one could do things like sentence diagrams and grammar theory much more easily in TeX than elsewhere. 5. Toward Generalization, but Keep the Good Stuff It would be neat to sit down with experienced designers or professors of design and see where DEK's solutions and those built on them work well for today's expectations and where they do not. Curiously, if you look at Wikipedia on page design, typography, and other design-related issues and TeX does not really show up in the external links. My design books are almost twenty years old. They are: Collier and Cotton. Basic Desktop Design and Layout Murphy and Rowe. How to Design Trade Marks and Logos Devall. Desktop Publishing Styleguide White. Graphic Design for the Electronic Age Craig. Designing with Type, 3rd ed. Still, one can see even there certain relationships of parts to whole that, in the main, ConTeXt has done better than any other TeX variant to address. I find the \setuplayout and related general layout, makeup, sectioning, and other features to be substantially superior to LaTeX, where the publishers do the styles and the scientists write the content, or plain, where you have to do everything (not always bad, but Herculean for a large project). Charles

3 2