- dev-context - NTG Mailing Lists

Re: [dev-context] little unharmful bug in \showfont & using \iffontchar in \definecharacter
by Taco Hoekwater 25 Jan '06

25 Jan '06

Hans Hagen wrote: > Taco Hoekwater wrote: >> \sl is a language switch now. Those two-letter language switches are >> a bit problematic at times. >> > no, sl is still slanted, language switches are not defined when there is > an existing command and the font mechanism will redefine it anyway; > \mainlanguage[slovenian] should work as well; I guessed wrong, so I owe you something now. Beer at BachoTeX? Taco

2 1

little unharmful bug in \showfont & using \iffontchar in \definecharacter
by Mojca Miklavec 25 Jan '06

25 Jan '06

Hello, I spotted a somehow strange behaviour in \showfont. It seems to be language-dependent for some reason. \showfont draws a gray square if there is no glyph present on some slot, but sometimes the blue numbers are drawn in that square and sometimes not. See for example the number 14 and 15 (gray square, numbers) in comparison to 16 and seventeen (gray square, no numbers) in the next example: \mainlanguage[sl] % try "en" or leave this line out and compare \starttext \showfont[ts1-lmr10] \font\tslmr=ts1-lmr10 % just to test: \page \def\test#1{#1: \getglyph{ts1-lmr10}{\char#1} {\sl\iffontchar\tslmr#1\else (empty)\fi}\par} \startcolumns[n=5] \dostepwiserecurse{0}{39}{1}{\test{\recurselevel}} \stopcolumns \stoptext When trying to understand what \showfont does I started wondering if it would be feasible to do font-depending encoding-depending definitions of glyphs (\definecharacter). If \iffontchar exists: why not using it? It's stupid to tell to ConTeXt that "ijligature" or "ccaron" exists in the font although the slot is empty, if ConTeXt could figure that out from the font itself and then use the fallback definition \buildtextcaron c instead. This would also reduce the need of files such as "enco-ecm.tex". I already asked some time ago if it would be possible to use something like this: \starttypescript [whatever font] \startencoding [ec] \definecharacter ijligature {ij} % or \undefinecharacter ijligature % or \definecharacter ijligature {\takethefallbackdefinitionofijligature} \stopencoding \stoptypescript But even if this was implemented, it would require quite some error-prone manual work. In contrast to that, \iffontchar would offer a fully automatic alternative and would solve many problems with third-party fonts (those that don't mind having TeX-specific characters). Mojca

3 3

[Fwd: Re: little unharmful bug in \showfont & using \iffontchar in \definecharacter]
by Hans Hagen 25 Jan '06

25 Jan '06

1 0

SciTE on linux
by Taco Hoekwater 24 Jan '06

24 Jan '06

Hi, I now have a SciTE environment running on linux, but I've had to tweak some stuff, that perhaps could be backported to the distro. * Especially, setting up the font was a bit weird. The X font server (at least the free version) does not understand OpenType fonts, so I had to convert LMTypewriter10-Regular to truetype using fontforge, then install the truetype font in X. The system name became "LMTypewriter10 Regular", and the addition of " Regular" is crucial. Just "LMTypewriter10" does not work. Also, I found I needed to add an exclamation mark in from of the name to get an antialiased font (it looks awful without that). So I have changed the two lines in context.properties to: font.monospace=font:!LMTypewriter10 Regular,size:16.5 font.errorfont=font:!LMTypewriter10 Regular,size:11.5 Now it works, with the exception that the top of a number of characters like [ and ] is not displayed in a most font sizes (that may be a problem caused by the auto-generated TTF font. does it happen on windows as well?). * I've changed the 'go' command so that it runs $(name.context.acrobat) $(FileName).pdf system() on unix does not automatically resolve file extensions like windows does, so the direct "$(FileName).pdf" did not work. * I also had to create texmfstart: that command does not exist on texlive (but it is in tetex 3.0). Cheers, Taco PS Shouldn't there be a cont-fr-scite.properties as well now?

2 14

newpstopdf - only the first page?
by Mojca Miklavec 20 Jan '06

20 Jan '06

Is newpstopdf (without any arguments) supposed to convert the first page of ps only? Mojca

1 0

using xpdf instead of acrobat
by Taco Hoekwater 20 Jan '06

20 Jan '06

Attached is a small patch for texexec (perl version) and a minimalistic shell script. This allows texexec --autopdf --xpdf --pdf test.pdf It will use xpdf instead of acroread. This removes the need to press 'R' in xpdf, nothing else. It is mostly useful when running texexec from an editor Cheers, Taco #!/usr/bin/env sh screen xpdf -remote TeXExec $* &

1 0

Ann-context@ntg.nl and NTG-context@ntg.nl
by Taco Hoekwater 13 Jan '06

13 Jan '06

Hi! Hans, can you add ntg-context as a subscriber of ann-context? That way I eon't have to add the normal list manually for each announcement. TIA, Taco

1 0

texshow (request, what else?) again
by Mojca Miklavec 07 Jan '06

07 Jan '06

Hello, Patrick, a small proposal again: there are some commands in ConTeXt such as \texteuro, \ccaron, \tracewhatever, ... which are not really proper commands like \setupframed[..]. In case you still have any space for manipulation in that way: have you considered a possibility for adding such "pseudo-commands" as well? If you add support for such weird stuff, you can then add flags to commands (in the sense of Categories on wiki), say "context command" (those that are currently present in texshow), "symbol" (texteuro, ccaron, dstroke, ...), "low-level commands" (do not use!), "metafun macros" (although they currently don't really fit in very well), "TeX primitive", "plain TeX macro", "commands from a certain module" (bibliography, lettrine, m-* files, s-* files, ...) The basic search would then consider only commands from the "same" set that is currently present, while "full search" or links from wiki could access the whole set of commands/macros/primitives/... The stubborn Mojca again

1 0

cont-en.xml
by Patrick Gundlach 05 Jan '06

05 Jan '06

Hi, I'll be away for some days over christmas and I know I'll get bored once or twice, so I can have a look into the new texshow. What applications (besides mine) use the xml defintion file? * quick references (pdf) * the perl/tk based browser (can't remember its name, sorry) * ? I am not sure what I want to do yet, but there are cleanups to be done, such as the bodyfont=5...12pt thing, style=normal,...,command. I guess that these should be substituted by a special tag 'you can use a bodyfont instruction' such as cd:fontinstr or cd:style for the other one. But I don't promise anything. Patrick -- ConTeXt wiki and more: http://contextgarden.net

3 14

ConTeXt Revisions project
by Taco Hoekwater 05 Jan '06

05 Jan '06

Hi All, I wrote a few weeks ago, about making old context releases available to everybody: >>I'll start adding stuff next week. The first ones >>will be hard, [..] 122 massive commits later, I am finished putting all cont-tmf.zip files in the subversion repository: https://foundry.supelec.fr/projects/contextrev/ The svn comment is always the release date. There are less than 122 releases in the SVN, more like 110, because sometimes I messed up the commit, and had to add a few files afterwards. Usually, that happened when new directories were added to the zip (it is surprisingly hard to get that right in one iteration). Everything from March 2003 onwards is complete and reliable, there can be tiny errors in the older commits (it took me that long to iron out all of the bugs in the zip compare script). I've lowercased the MS-DOS filenames in the oldest zips, and put them in tex/context/base (these antiquary zips did not have an embedded directory tree). I will create file releases for every zip archive also, but there are problems with the uploads for that, so it'll have to wait until Fabrice has time to debug the site configuration. If you want to make sure you download a 100% accurate version of one of the old releases, it is better to wait for those releases to appear. Happy TeXing! Taco

2 1