September 2005 - ntg-context - NTG Mailing Lists

Sync with ConTeXt
by Steffen Wolfrum 16 Sep '05

16 Sep '05

Hi, using TeXShop 2.03 I was very glad that syncing seems to work even with ConTeXt's project structure. But unfortunately it "only" works from source to pdf (well, already quite useful): Clicking in the pdf has no effect (although my component file starts with %!TEX TS-program = context %!TEX root = ../main.tex Is syncing with ConTeXt not yet fully supported - or is there a work-around for the pdf->source jump that I don't know? Thanks, Steffen

1 0

Including images in included files in subdirectory
by Giuseppe Bilotta 16 Sep '05

16 Sep '05

Situation: Tree structure: main.tex subdir/inc.tex subdir/fig.1 in main .tex " \include subdir/inc.tex " in subdir/inc.tex " \externalfigure[fig.1] " texexecing main.tex doesn't find the figure fig.1 subdir/inc.tex must use " \externalfigure[subdir/fig.1] " for the figure to be found. IMO this is a bug. Image should be checked for existence using as base the directory of the current input file *first*, then in the others. -- Giuseppe "Oblomov" Bilotta

4 4

mail delay
by Wolfgang Zillig 16 Sep '05

16 Sep '05

Hello, when I sent messages to the list it takes about 1.5 hours until I get them back. It is not really a problem for me, I'm just wondering about. Wolfgang

2 3

czech food
by Vit Zyka 15 Sep '05

15 Sep '05

Hello mostly Czech ConTeXters, I have noticed in the modules.pdf that there are some Czech slot empty in the lang-sla.tex. Most of them are filled up now. All changes are marked by 'new' comment. Main changes: - redefinition of 'dashes' (pomlcek) \c!leftsentence=\thickglue--\thickglue\penalty-20, \c!rightsentence=\thickglue--\thickglue\penalty-20, \c!leftsubsentence=~---~\penalty-20, \c!rightsubsentence=~---~\penalty-20, (intends were: endash size preferable, short stretchable/shrinkable spaces around, line break possible after dash but not before; it conforms Czech typographical rules) It needs some new definitions to core-spa.tex (Hans ??): \unexpanded\def\textormathglue#1#2#3{% {\dimen0=#1\hspaceamount\empty{#3}% \skip0=0pt plus.5\dimen0 minus.3\dimen0 \ifmmode\mskip#1#2% \else\kern#1\hspaceamount\empty{#3}\hskip\skip0\fi\relax}% } \def\thinglue {\textormathglue+\thinmuskip 1} \def\medglue {\textormathglue+\medmuskip 2} \def\thickglue {\textormathglue+\thickmuskip3} - definition of day names - most of empty slot added (Zkratky, Sekce, Subsekce, viz, ...) The file is attached. Suggestions are welcomed. Vit ======================================================= Ing. Vít Zýka, Ph.D. TYPOkvítek database publishing databazove publikovani data maintaining and typesetting in typographic quality priprava dat a jejich sazba v typograficke kvalite tel.: (+420) 777 198 189 www: http://typokvitek.com =======================================================

2 2

\limitatefirstline and the new beta
by Peter Rolf 15 Sep '05

15 Sep '05

Hi Hans, I just installed the latest beta (14.09.2005) and realised, that \limitatefirstline is still unchanged. Just read my last mail from the 12th for the details. Sorry for stealing your time. So I have either to change the description on the wiki, or you have to change the macro :) Greetings, Peter P.S.: This is the version I'am currently using (but with 6ex instead of 2ex tolerance). Using a variable value for the tolerance would make it even more flexible and user friendly. \def\limitatefirstline#1#2#3% {\hbox\bgroup\strut\dontcomplain \setbox\scratchbox\hbox{\begstrut#1\endstrut}% \ifdim\wd\scratchbox>#2\relax \setbox\scratchbox\hbox{#3}% \hsize#2\relax \advance\hsize-\wd\scratchbox \setbox\scratchbox\vbox{\forgetall\veryraggedright#1}% \setbox\scratchbox\vsplit\scratchbox to \lineheight \vbox {\unvbox\scratchbox \global\setbox\plusone\lastbox \global\setbox\plusone\hbox{\strut\unhbox\plusone}% \hbox % to #2 {\ifx\clip\undefined \box\plusone \else\ifdim\wd\plusone>\hsize \lower\strutdepth\hbox{\clip[\c!width=\hsize,\c!height=\lineheight]{\hbox{\raise\strutdepth\box\plusone}}}% \else\ifdim\wd\plusone<\dimexpr\hsize-6ex\relax \lower\strutdepth\hbox{\clip[\c!width=\hsize,\c!height=\lineheight]{\hbox{\raise\strutdepth\hbox{\begstrut#1\endstrut}}}}% \else \box\plusone \fi\fi\fi \removeunwantedspaces#3}}% \removeunwantedspaces\hss#3}}% \else #1% \fi \egroup}

1 0

lgrind...
by Andre van der Vlies 14 Sep '05

14 Sep '05

Hi, I use 'lgrind' to format my 'source code' (C, python, sricpts, etc.). I like the 'layout' (highlighting, line numbering...). Is there something equivalent (or better :) in/for ConTeXt? -- Andre van der Vlies <andre(a)vandervlies.xs4all.nl> Certifiable UNIX engineer Homepage: http://vandervlies.xs4all.nl/~andre Key fingerprint = 397C 7479 67DB 9306 23DC B423 7B58 CD5A 6EFF 5CF8 -- () ascii ribbon campaign - against html e-mail /\ - against microsoft attachments ^[^#] --

5 5

towards some more consistency in regimes & unicode support
by Mojca Miklavec 14 Sep '05

14 Sep '05

Hello, Sorry for a slightly longer mail. I wanted to send it to context-dev, but probably there's someone else besides Adam out there who could contribute (for example to re-chech Greek or Cyrillic section of Unicode or even add some missing Hebrew definitions for example). If someone thinks that it's more appropriate, please feel free to continue the discussion on context-dev. I. in regi-utf it would be fine to add: \defineregimesynonym[utf-8][utf] \defineregimesynonym[utf8][utf] II. After a long time I finally decided to write my first ruby script. I took UnicodeData.txt, adobe glyph list, enco-uc.tex, collected averything together, removed characters >FFFF (in case someone needs them they can trivially be added again, but I don't think that anyone is planning to name them shortly), did some manual corrections ... and here are the results: http://pub.mojca.org/tex/enco/contextlist/ http://pub.mojca.org/tex/enco/contextbase/regi-temp.tex The idea behind is that there is no "definite refence" to the ConTeXt glyph names, which means that every new regime that should be supported needs a lot of manual work and leads to many inconsistencies. The file contextnames.txt contains the Unicode hexadecimal number, pdf name (from Adobe Glyph List), ConTeXt name and the Unicode name. This could then be a source of information when adding new regimes, writing unicode vectors (unic-*), mapping to font encodings, uppercasing/lowercasing information for font encoding and other files can now be derived directly from unicode and this list (unicode already contains information about upper/lowercase variants of the letters) ... There is some more info missing, which should be either packed within the same file or in separate files: - ConTeXt synonyms (like \Dcroat -> \Dstroke, ...) - pdf synonyms (dbar -> dcroat), to help recognize the glyphs in .enc or .afm and automate support for it - faking the characters (\ccaron -> \buildtextaccent\textcaron{C}) - unaccented version of the characters (\Aacute -> A, ...) - other characters not present in unicode (Caron, Acute - these are accents for uppercase letters, ...) - (I'm sure that I wanted to add some more points, but I don't remember any other right now) When I wanted to add the names from unic-34.tex, I realized that we don't really need to have a command for "every single unicode character" (we certainly don't need to map math characters into that region), but if someone already has a file with unicode integrals, it costs nothing to give him those characters in output. (Shortly: 0x2211, "N-ARY SUMMATION" should expand into $\sum$, but not the other way round) I have to slightly change the syntax in the context glyph names file to note this difference and to be able to define math (and other) signs properly. ------------------------------------------------------------------------ III. Now I need some help - someone should help me revise the file contextname.txt (I prepared a HTML version of it): correct mistakes (if any are spotted), add new definitions, help to prepare a list of synonyms, a list of expansions (\buildtextaccent), ... ------------------------------------------------------------------------ Here are some points which I spotted, but can't fix them alone 1. Characters missing (needed by some regimes): 0020-007F section 037A GREEK YPOGEGRAMMENI 0384 GREEK TONOS 0385 GREEK DIALYTIKA TONOS 2015 HORIZONTAL BAR 2017 DOUBLE LOW LINE 20AA NEW SHEQEL SIGN 20AB DONG SIGN 20AF DRACHMA SIGN 2116 NUMERO SIGN 200E LEFT-TO-RIGHT MARK 200F RIGHT-TO-LEFT MARK 1Exx section 2. Greek - there are some name inconsistencies when compared to the unic-031 vector, but I don't know anything about old greek. I didn't check Cyrillic at all. 3. Punctuation and accents - mostly names for quotes and language dependency (lowerleftuppersixquote in comparison to lftdblquote ... or whatever they are called) (+ tricks, I already asked about quotes & hyphenation approximately a week ago). I have problems understanding the difference between letter modifiers (U+02Cx) and usual accents (U+00Bx), "Combining Diacritical Marks" (U+03xx) should be supported somehow as well. I have no idea how to make U+0065 U+0301 (e + combining acute accent) into eacute. 4. should hungarumlaut be doubleacute and hungarumlaut only its synonym or the other way round? 5. tbar vs. tstroke: compare 0166 and 023E 6. cedilla/commaaccent dilema: there's a huge problem with "t with cedilla" (0162): "t with comma below" (021A) sould be used instead (at least this is stated in Unicode reference), but most regimes map a character to "t with cedilla" (0162), which seems stupid to me. Adobe glyph list therefore uses tcommaaccent for "t with cedilla", which looks like "t with comma accent", but is on the wrong place. lmr have both tcommaaccent and tcedilla. \tcedilla should be "t with cedilla" in my opinion and \tcommaaccent "t with comma accent". That currently isn't the case in ConTeXt unless something has changed recently. There are many other letter wrongly named in Unicode ("with cedilla"), although they have a comma. I would suggest to name them \[gklnr]commaaccent and use \[gklnr]cedilla as a synonym (if needed at all for backward compatibility, otherwise it would be better to leave them out; there is no such letter with cedilla in unicode, if someone needs one, he can construct one trivially with \buildtextaccent) 7. there's "a-kind-of-bug-but-not-really-one" in enco-ans.tex. textcedilla maps to 184, which isn't defined in Antykwa for example (it's on place 24). It's more a "bug" in texnansi encoding, which has cedilla on two places, which is pretty stupid. But anyway: \definecharacter textcedilla 24 would solve some problems (and hopefully not introduce new ones). 8. most letters are named "c with cedilla" -> ccedilla what about the names for "open o", "turned e", "long s", "turned r with hook"? \openo or \oopen? \rturnedhook or \turnedrhook? 9. can latin letters and numbers be accessed somehow by name? 10. Adam prepared some dingbats support I think, this could be added here. 11. There's a showunicode pdf document on pragma-ade.com (at least I saw it once), but it's not listed on the overview.htm. 12. I don't know if anyone would ever need to switch from viscii regime to some other, but what would happen to the characters under 128 (some of them are redefined in viscii)? I'm affraid that there would remain Vietnamese leftovers in the lower part of the table. 13. If there are any other comments on the table and/or the script(s), please let me know. IV. With the help of the prepared names list I processed definitions for regimes (taken from Unicode webpage) for ISO-8859-* and cp125* (others should be trivial). They are only preliminary, some (Hebrew, Thai, Arabic) probably don't make any sense yet, but could the rest be added to ConTeXt after someone checks if everything is OK? (iso88595, cp1251, il1, il2, il9, windows and viscii regimes already exist and should be compared for differences) If possible in such a way that it wouldn't be necessary to include the regime definition file manually, but similarly as \usemodule[pre-polish] finds and processes the proper file, the \enableregime[xxx] should find the proper file and load it. (And for those who made it till here - sorry again for that gigantic mail.) Mojca

2 2

Problem following "OpenType installation basics for ConTeXt" article
by Gavin Sinclair 14 Sep '05

14 Sep '05

Greetings (first post), Adam Lindsay's recent article "OpenType installation basics for ConTeXt" in The PracTeX Journal (http://www.tug.org/pracjourn/2005-2/lindsay) is very well written. Unfortunately, I was unable to perform the first step. As the article specified, I ran the command: $ texfont --ma --in --ve=public --co=torunska --lcdf --pre --va=liga,kern It started off OK, but failed to properly create the map file. Selected output follows: extending map file : E:/MiKTeX/local/fonts/map/pdftex/context/texnansi-LIGA-KERN-public-torunska.map font identifier : AntykwaTorunska-Bold -> text -> tfm processing files : otf -> tfm + enc otftotfm: './AntykwaTorunska-Bold.otf': No such file or directory no mapfile from otftotfm : texfont.map font identifier : AntykwaTorunska-BoldItalic -> text -> tfm processing files : otf -> tfm + enc otftotfm: './AntykwaTorunska-BoldItalic.otf': No such file or directory no mapfile from otftotfm : texfont.map [and so on for each .otf file] So, otftotfm is claiming that the files don't exist, but they absolutely 100% do. Perhaps it's looking for them somewhere else? Does anyone have any suggestions? Regards, Gavin

8 20

\setupbodyfont[10dd]
by Mojca Miklavec 14 Sep '05

14 Sep '05

Hello, This question doesn't come from me, but as I wasn't able to answer, I'm posting it here: Consider the following text: \setupbodyfont[20pt] \starttext \input tufte \switchtobodyfont[10pt]\setupinterlinespace\page \input tufte \switchtobodyfont[10dd]\setupinterlinespace\page \input tufte \switchtobodyfont[10.6574803pt]\setupinterlinespace\page % = 10dd \input tufte \stoptext How are the interline distances determined? The last two pages give different results. The line breaking could be influenced by minimal rounding mistakes, but I don't understand why the distances between lines differ substantially. Thank you, Mojca

5 10

Re: [NTG-context] lgrind (An intro to LaTeX package conversion)
by Brooks Moses 14 Sep '05

14 Sep '05

(Andre: I'm sending this reply back to the ConTeXt list, because I think a fair bit of my reply might be generally useful to other people who want to try to convert LaTeX packages to ConTeXt. I hope that's ok!) At 01:58 PM 9/13/2005, Andre van der Vlies wrote: >Brooks Moses said: > > Meanwhile, though, after looking through the code, I don't think there's > > actually much need to modify the executable. Lgrind mostly doesn't write > > LaTeX (which is why Andre found it so obscure) -- it writes TeXcode that > > uses its own simple commands, which are then defined in lgrind.sty. To > > use > > Lgrind in ConTeXt, one needs to translate the style file into a > > t-lgrind.tex, at which point the same Lgrind output files can be used in > > both systems. > >Hmmm, that sure sounds promising. I've just recently using ConTeXt, this >week actually. I am trying to rebuild a, few paged, LaTeX document which >is typical for me... > >I think that renaming the 'sty' file will not be enough :-/ Not really, no. Though it's potentially a start. What you'll need to do then is to translate all of the LaTeX bits in it to ConTeXt bits. (Also, it may be easier to start with the lgrind.dtx file, since that has all the comments that explain what's going on.) >Thus, I produce a t-lgrind.tex, which I can \input and henceforth use >something like \plasterthis{fine.grind}? I should perhaps have explained that more thoroughly. ConTeXt has "modules", which are roughly equivalent to LaTeX's packages; the filename "t-lgrind.tex" indicates a module. (Specifically, the "t-" prefix indicates that it's a "third-party module", which is everything other than the modules that are actually part of ConTeXt itself.) Thus, you'd use it with \usemodule[lgrind] rather than \input. It amounts to pretty much the same thing, except ConTeXt does keep track of things so as not to load it twice, and things like that. One big difference is that LaTeX puts all package code in a \makeatletter / \makeatother block. ConTeXt doesn't do this, so you need to put those in manually -- the ConTeXt equivalent is \unprotect / \protect (which also allow ! and ? in macro names, along with @). >Or, am I on the wrong track??? > >I sure need to to a lot of reading... Feel free to ask questions, too! Some information to get you started: ===== An introduction to translating packages to modules ===== (As exemplified by a detailed discussion of lgrind.dtx) First, copy everything in lgrind.dtx from about line 609 ("Implementation of Lgrind") to the end of the file into t-lgrind.tex. Put a \unprotect command at the beginning, and a \protect command at the end, so that you can use @ in macro names. \newcommand and \renewcommand are LaTeX-specific. The easiest way to deal with this is to simply replace it with TeX \def macros, though that loses the error messages that come from checking whether the command exists or not. \DeclareOption is LaTeX's way of handling package options. For a first pass, it's probably easiest to just delete these. (Or, if you usually use the option, then include the option's code directly.) All of the \sffamily, \rmfamily, \itshape, and other font formatting commands on lines 727-736 are LaTeX-specific; you can replace them with the ConTeXt equivalents, which are on a Wiki page on "Basic Text Formatting". I'm not sure whether \normalfont (lines 893, 901, and so forth) is LaTeX-specific or not. You might have to replace that with the ConTeXt equivalent. At line 818, the "lgrind" environment is defined. The \newenvironment command is definitely a LaTeXism; you'll want to replace that with definitions for \startlgrind and \stoplgrind. The use of the minipage and figure environments in lines 1060 or so and later are going to require a bit of looking at to figure out how to best replace them with ConTeXt equivalents. Luckily, it looks like these are some of the "advanced" bits, so you could just not worry about this until you've got the basic lgrind environment working. And I think that should do it. There may be a few other LaTeXisms in the file that I missed, but a bit of testing should find those.... ===== end ===== Probably by the time you've done that, you'll have had quite a thorough introduction to ConTeXt! :) - Brooks

2 1