Re: [dev-context] Checksum of original font files stored in the cache?

anyhow, i have been thinking of generating (with each beta) an automatically added key 'changedate' or so for changed files but i need to be really bored (or watching a one star movie on tv) to do that Tonight at 20:30 on RTL7: Timecop II: The Berlin decision I think that qualifies

[dev-context] Checksum of original font files stored in the cache?

Dear wise guys, the other day I found myself caught in a trap that might be a frequent source of puzzlement for the casual ConTeXt user :-) I had replaced an OpenType font in the usual OS directory by a new version. Typesetting documents using that font produced surprising results... the PDF

[dev-context] Cache folder in minimals

Hi Mojca, since a few days ago the minimals appear to rsync the cache folder, too... is this intended? Oliver PGP.sig Description: Signierter Teil der Nachricht ___ dev-context mailing list dev-context@ntg.nl

Re: [dev-context] bibtex not finding style files

Ah, nice hint! It turns out kpathsea can NOT find the files, either. Will investigate… Problem solved. The installer package did not run mktexlsr. By the way, can you guys think of any other programs (besides bibtex) in a pure MkIV environment that still need kpathsea? Oliver

Re: [dev-context] bibtex not finding style files

No, it doesn't. bibtex uses kpathsea, so if you want to figure out why it fails, do something like this: kpsewhich --debug=2 cont-no.bst Ah, nice hint! It turns out kpathsea can NOT find the files, either. Will investigate… Oliver ___

[dev-context] bibtex not finding style files

Hi all, does anyone have a quick suggestion on why bibtex refuses to find cont-no.bst and the other style files? I do have BSTINPUTS (and BIBINPUTS) set to BIBINPUTS = .;$TEXMF/bibtex/bib// BSTINPUTS = .;$TEXMF/bibtex/bst// which should be fine for the minimals. I can also locate the style

Re: [dev-context] Mac installation package

*You* want to write a test suite for ConTeXt? The test suite is there. There is even a script in the test suit that compares the outputs of two versions at pixel level. All we need is people to submit tests and then someone to monitor the test suite. See

Re: [dev-context] Mac installation package

MkIV is ConTeXt’s feature without an doubt but it's not so easy as you think. I have myself two modules which work only with MkIV (simplefonts and games) but bigger ones like simpleslides or letter are just complexer styles and you can't expect from a user to upgrade to MkIV just to make a

Re: [dev-context] Mac installation package

What's more important, the exit status of the context command is 0 (via echo $?) indicating that there was no problem at all! This might turn out problematic as soon as documents are processed in a batch run ... (like e.g. a regression test suite ;-) *You* want to write a test suite for

Re: [dev-context] Mac installation package

Would it then be possible to have ConTeXt grind to a complete halt once it encounters a module whose minimum requirements aren't met? \doifolderversionelse\contextversion{2100.01.01}\normalend\donothing %\doifolderversionelse\contextversion{2009.07.01}\normalend\donothing \starttext Hello

[dev-context] Cache path creation

Dear all, here's a thing that's puzzling me ... I set up the cache path in texmf/ web2c/texmfcnf.lua to point to a location which doesn't exist yet. Running luatools --generate now gives me different results with ConTeXt versions 2009.06.11 and 2009.06.13. The former one politely asks me

[dev-context] Mac installation package

Dear all, I've finally got around to actually make the Mac installation package happen :-) So please find a test version of the package (for Intel Macs running Tiger or higher) at http://svn.contextgarden.net/minimals/installer/osx/ This package is identical to the Minimals distribution

[dev-context] removing BibTeX auxiliary files with --purgeall

Hello Hans and Taco, may I also add the request that temporary files created by BibTeX are deleted automatically by --purgeall? That is, *.blg *.aux It'll probably be wise to keep the *.bbl file :-) Although it is created automatically by the BibTeX run I need to tweak it manually at

Re: [dev-context] Making a minimals update svn friendly

To what Aditya has answered: --keep option is probably not the solution to what Oliver wants to achieve. I suspect that he indeed wants to delete obsolete files, but preserve .svn. Yep. (Although I'm not quite sure what --keep exactly does here.) Oliver

Re: [dev-context] Luatex beta 0.31.0

Hi Taco, may I ask a completely uninformed question? I'm wondering whether it's also possible to access the glyphs' path data from within LuaTeX (and/ or MetaPost) ... Best, Oliver Hi all, I have just uploaded the archives for luatex 0.31.0. This is just an intermediate release so

[dev-context] MetaFun freelabel macro

Dear Taco, a minute ago I discovered this lovely macro freelabel() and friends … just a minor thing that confuses me a bit: freelabel(a, origin, dir(90)); places the label below the origin rather than above it. I would have expected the direction vector to point from the anchor point

Re: [dev-context] context program, mtxrun question?

but is texmfcnf.lua loaded? (--verbose) Sure. Both for root and the normal user. ok, another attempt .. new beta Version 2008.05.27 16:31 happily generates the file database and compiles both english and dutch formats! Also, it sticks to the proper cache location I defined in

Re: [dev-context] context program, mtxrun question?

well, i copy a non existing unix stub into the zip is this one ok? #!/bin/sh mtxrun --script context $@ Perfect. It's exactly the one that used to be present in the beta 2008.05.24 20:06 (both in the binaries as well as the unix stubs directories). I was wondering why you removed it at

Re: [dev-context] context program, mtxrun question?

Another question: what part of the LuaTeX chain is responsible for locating the configuration files? Is it the scripts mtxrun.lua and luatools.lua or the binary texlua itself? You mentioned something about luatools only but now that Hans uploaded the entire beta ... this is done in

Re: [dev-context] context program, mtxrun question?

What I mean is this: in the full path /usr/texbin/luatex, texbin can be a symlink to a different directory and that will be followed, but if luatex itself is a symlink to a file in a different directory, that will not be noticed. I think this should be just fine for the moment ... Extended

Re: [dev-context] context program, mtxrun question?

Hi Taco, This new release is available now. I've just had the chance to test this new release and got mixed results ... the 2008.05.21 minimal distribution (LuaTeX only) now sits in /usr/local/context/2008-05-21 and there's a symbolic link /usr/texbin -

Re: [dev-context] context program, mtxrun question?

Hans and I are extending context in this area right now, so any current answer will likely be outdated before much longer. So, a little bit of extra patience is required still. I see. It's just that literally everything about ConTeXt is changing on a daily basis and almost every current

Re: [dev-context] context program, mtxrun question?

Hello Taco, I see. It's just that literally everything about ConTeXt is changing on a daily basis and almost every current answer about just any topic seems to be outdated within a fortnight. Well, what else do you expect from code that is in active development? Sorry, but this rant

Re: [dev-context] context program, mtxrun question?

At the moment for me it would be enough to know where exactly LuaTeX looks for configuration information (path file name) and which files take precedence over others in the case of conflicts ... my current understanding is: 1. Environment variables 2. setuptex.tmf no, this one is