- dev-context - NTG Mailing Lists

[Fwd: Re: [NTG-context] setupframedtexts]
by Taco Hoekwater 01 Feb '06

01 Feb '06

AFAICS, margin is indeed ignored, but it is documented in the xml files. Looks like a leftover from the dutch days. Taco Hans van der Meer wrote: > The manual gives as settable parameter "margin = standard,yes,no. > However there is no visible effect when using "margin=no" in the setup. > Inspecting the code for setupframedtexts I could not foun something > like \c!margin. > > Is this an obsolete parameter? Or will it be implemented. > does setting "leftoffset=0pt" work? -- ----------------------------------------------------------------- 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 ----------------------------------------------------------------- _______________________________________________ ntg-context mailing list ntg-context(a)ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context

1 0

collector item #20 (ignored dx/dy in label arranging)
by Taco Hoekwater 30 Jan '06

30 Jan '06

Hi Hans, This patch should do it: \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 %TH three changed lines follow \ifdim\@@ppdx>\zeropoint \else \hss\fi \hskip\@@ppdx \ifdim\@@ppdx>\zeropoint \else \hss\fi \fi \box#1}% \ifnum\arrangedpageM<\arrangedpageX\else \global\setbox\arrangedpageA\vbox \ifdim\@@ppheight>\zeropoint to \@@ppheight \fi {\offinterlineskip \ifvoid\arrangedpageA\else \unvbox\arrangedpageA %TH three changed lines follow \ifdim\@@ppdy>\zeropoint \else \vss\fi \vskip\@@ppdy \ifdim\@@ppdy>\zeropoint \else \vss\fi \fi \box\arrangedpageB}% \doglobal\newcounter\arrangedpageM \fi \ifnum\arrangedpageN<\arrangedpageT\else \poparrangedpages \fi} Cheers, taco

2 1

new release
by Taco Hoekwater 27 Jan '06

27 Jan '06

The latest and (hopefully) greatest: http://wiki.contextgarden.net/Context_2006.01.27 I won't do an official announce yet, I sort of expect another release in the not-so-distant future :-) Taco

2 1

cont-en.xml: duplicate entries
by Patrick Gundlach 26 Jan '06

26 Jan '06

Hi, in cont-en.xml (and probably the others, too), the following entries have duplicates: placecombinedlist placeregister defineinteractionmenu setupstrut Patrick

2 3

Re: [dev-context] How to help ConTeXt?
by Hans Hagen 26 Jan '06

26 Jan '06

Hi Junod I forward your mail to the context dev list. The primary sites to get context are our website (source code) and the internal svn server (manuals). Taco and Patrick are the ones who take care of the wiki, mirroring, announcing and such, so they can best tell what help is needed as soon as files leave our servers. Thanks for offering. >Hello Hans, > >I falled in love with ConTeXt and would like to help the project. I'm >a swiss student in computer science, ie I've no money to donate. But I >would be really happy to host a mirror or somethig equivalent, if >needed, on one of my german servers (big machines, fast networks). > >Let me know if you're interested! > >And thanks for having created ConTeXt! > > you're welcome >-Junod Antoine > > ----------------------------------------------------------------- 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 -----------------------------------------------------------------

4 3

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