Re: [NTG-context] Problem with font mapping

2009-11-25 Thread Mika Ritola
2009/11/25 Hans Hagen 

> Mika Ritola wrote:
>
>> Hello again,
>>
>> I seem to be running into all sorts of font problems. Now my document has
>> suddenly turned bold. For example, running the following code results in
>> "Test." being rendered in bold characters.
>>
>> \usemodule[simplefonts]
>> \setmainfont[Adobe Garamond Pro]
>>
>> \starttext
>> Test.
>> \stoptext
>>
>> Running "mtxrun --script font --list --pattern="*Garamond*" --all" reveals
>> that there's something fishy about the font mapping:
>>
>> adobegaramondpro => agaramondprosemibold => AGaramondPro-Semibold.otf
>> adobegaramondprobold => agaramondprosemibold => AGaramondPro-Semibold.otf
>> adobegaramondprobolditalic => agaramondprosemibolditalic =>
>> AGaramondPro-SemiboldItalic.otf
>> adobegaramondproitalic => agaramondprobolditalic =>
>> AGaramondPro-BoldItalic.otf
>> adobegaramondpronormal => agaramondproregular => AGaramondPro-Regular.otf
>> adobegaramondproregular => agaramondprobold => AGaramondPro-Bold.otf
>> adobegaramondprosemibold => agaramondprosemibold =>
>> AGaramondPro-Semibold.otf
>> agaramondprobold => agaramondprobold => AGaramondPro-Bold.otf
>> agaramondprobolditalic => agaramondprobolditalic =>
>> AGaramondPro-BoldItalic.otf
>> agaramondproitalic => agaramondproitalic => AGaramondPro-Italic.otf
>> agaramondproregular => agaramondproregular => AGaramondPro-Regular.otf
>> agaramondprosemibold => agaramondprosemibold => AGaramondPro-Semibold.otf
>> agaramondprosemibolditalic => agaramondprosemibolditalic =>
>> AGaramondPro-SemiboldItalic.otf
>>
>
> i cannot check it as i have no adobe garamond
>
>
>  As you can see, agaramond... are mapped properly while adobegaramond...
>> are mapped wrong.
>>
>
> it all depends in what info is in the font ... familyname, weight etc and
> sometimes it's contradicting
>
> I downgraded to the "current" (2009.10.27 16:35) version of ConTeXt to see
if the mappings are different, and this is the result:

adobegaramondpro => Adobe Garamond Pro Bold => AGaramondPro-Bold.otf
adobegaramondprobold => Adobe Garamond Pro Bold => AGaramondPro-Bold.otf
adobegaramondprobolditalic => Adobe Garamond Pro Bold Italic =>
AGaramondPro-BoldItalic.otf
adobegaramondproitalic => Adobe Garamond Pro Italic =>
AGaramondPro-Italic.otf
adobegaramondproregular => Adobe Garamond Pro Regular =>
AGaramondPro-Regular.otf
adobegaramondprosemibold => Adobe Garamond Pro Semibold =>
AGaramondPro-Semibold.otf
adobegaramondprosemibolditalic => Adobe Garamond Pro Semibold Italic =>
AGaramondPro-SemiboldItalic.otf
agaramondprobold => AGaramondPro-Bold => AGaramondPro-Bold.otf
agaramondprobolditalic => AGaramondPro-BoldItalic =>
AGaramondPro-BoldItalic.otf
agaramondproitalic => AGaramondPro-Italic => AGaramondPro-Italic.otf
agaramondproregular => AGaramondPro-Regular => AGaramondPro-Regular.otf
agaramondprosemibold => AGaramondPro-Semibold => AGaramondPro-Semibold.otf
agaramondprosemibolditalic => AGaramondPro-SemiboldItalic =>
AGaramondPro-SemiboldItalic.otf

In other words, the mappings seem to be fine here (though I'm not sure about
the first one). Thus, it seems that some change in ConTeXt has "broken" the
font.

>
>  Changing \setmainfont[Adobe Garamond Pro] to \setmainfont[agaramondpro]
>> fixes the issue but, still, I'd prefer to use the former (as I've done until
>> now) since it's clearer.
>>
>
> how recent is your version of mtxrun / mtx-font / font database? it has
> been a bit in flux last weeks
>
> Do you mean the database that's generated by "mtxrun --script font
--reload"? Updating it didn't solve the problem.

Mika
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


[NTG-context] Problem with font mapping

2009-11-25 Thread Mika Ritola
Hello again,

I seem to be running into all sorts of font problems. Now my document has
suddenly turned bold. For example, running the following code results in
"Test." being rendered in bold characters.

\usemodule[simplefonts]
\setmainfont[Adobe Garamond Pro]

\starttext
Test.
\stoptext

Running "mtxrun --script font --list --pattern="*Garamond*" --all" reveals
that there's something fishy about the font mapping:

adobegaramondpro => agaramondprosemibold => AGaramondPro-Semibold.otf
adobegaramondprobold => agaramondprosemibold => AGaramondPro-Semibold.otf
adobegaramondprobolditalic => agaramondprosemibolditalic =>
AGaramondPro-SemiboldItalic.otf
adobegaramondproitalic => agaramondprobolditalic =>
AGaramondPro-BoldItalic.otf
adobegaramondpronormal => agaramondproregular => AGaramondPro-Regular.otf
adobegaramondproregular => agaramondprobold => AGaramondPro-Bold.otf
adobegaramondprosemibold => agaramondprosemibold =>
AGaramondPro-Semibold.otf
agaramondprobold => agaramondprobold => AGaramondPro-Bold.otf
agaramondprobolditalic => agaramondprobolditalic =>
AGaramondPro-BoldItalic.otf
agaramondproitalic => agaramondproitalic => AGaramondPro-Italic.otf
agaramondproregular => agaramondproregular => AGaramondPro-Regular.otf
agaramondprosemibold => agaramondprosemibold => AGaramondPro-Semibold.otf
agaramondprosemibolditalic => agaramondprosemibolditalic =>
AGaramondPro-SemiboldItalic.otf

As you can see, agaramond... are mapped properly while adobegaramond... are
mapped wrong.

Changing \setmainfont[Adobe Garamond Pro] to \setmainfont[agaramondpro]
fixes the issue but, still, I'd prefer to use the former (as I've done until
now) since it's clearer.

I'm running ConTeXt version 2009.11.24 10:13.

Mika
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] Fonts disappeared after updating ConTeXt

2009-11-15 Thread Mika Ritola
2009/11/15 luigi scarso 

> On Sun, Nov 15, 2009 at 11:38 AM, Mika Ritola 
> wrote:
> > Hello,
> >
> > I just updated ConTeXt to the latest version (2009.11.13 12:45), and now
> all
> > the fonts I have installed on my system seem to have mysteriously
> > disappeared from ConTeXt's sight. Running "mtxrun --script fonts --list"
> > displays only the fonts that are installed in the ConTeXt directory. I'm
> > using Linux and fontconfig finds all the fonts just fine. Until now, I
> > haven't had any problems using the fonts on my system after an update
> > without any further actions. I did, however, run
> >
> > luatools --selfupdate
> > mtxrun --selfupdate
> > luatools --generate
> > context --make
> >
> > just to make sure that everything is up-to-date but that didn't make any
> > difference.
> >
> > Have any font-related changes been made to ConTeXt in the past few weeks
> > (the previous version that I used was from maybe a month ago) or what
> could
> > be the cause of this?
> Are you using minimals ?
>
> Yes, I use first-setup.sh to update.

Mika
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


[NTG-context] Fonts disappeared after updating ConTeXt

2009-11-15 Thread Mika Ritola
Hello,

I just updated ConTeXt to the latest version (2009.11.13 12:45), and now all
the fonts I have installed on my system seem to have mysteriously
disappeared from ConTeXt's sight. Running "mtxrun --script fonts --list"
displays only the fonts that are installed in the ConTeXt directory. I'm
using Linux and fontconfig finds all the fonts just fine. Until now, I
haven't had any problems using the fonts on my system after an update
without any further actions. I did, however, run

luatools --selfupdate
mtxrun --selfupdate
luatools --generate
context --make

just to make sure that everything is up-to-date but that didn't make any
difference.

Have any font-related changes been made to ConTeXt in the past few weeks
(the previous version that I used was from maybe a month ago) or what could
be the cause of this?

Mika
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] mkiv vs. mkii

2009-09-26 Thread Mika Ritola
2009/9/26 Taco Hoekwater 

> Hi all,
>
> A few days ago I started a wiki page about the intentional and/or
> unavoidable differences between MKIV and MKII.
>
>  http://wiki.contextgarden.net/MkIV_Differences
>
> The page is not intended for actual bugs, but: if you know of
> any 'disturbing' differences please add them to that page, then
> Hans and I can investigate whether the difference is intentional
> or a bug.
>

It says this on the page: "It should come as no surprise that
*mode=node*generates different effects, but even with a traditional
font setup there
are incompatibilies unless you use tfm-only fonts."

Could you explain what mode=node does? I've seen it mentioned many times but
I still don't know what its purpose is. I searched the ConTeXt site (using
the search box), and didn't find any other useful information on it except
that it affects kerning, but how? What are the advantages and disadvantages
of using it? When should you use it?

Mika
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] Another small caps problem with some fonts (and old-style figures)

2009-09-24 Thread Mika Ritola
2009/9/24 Mika Ritola 

> 2009/9/23 Hans Hagen 
>
>> Mika Ritola wrote:
>>
>>> 2009/9/22 Wolfgang Schuster 
>>>
>>>  Am 22.09.2009 um 12:43 schrieb Mika Ritola:
>>>>
>>>>  Hello again,
>>>>
>>>>> I just discovered another weird problem with small caps when using some
>>>>> fonts, e.g. Adobe Jenson Pro or Adobe Garamond Pro.
>>>>>
>>>>> When old-style figures are enabled, the code below generates "GEOff"
>>>>> instead of "GEOFF". Another ligature bug, it seems -- which is strange
>>>>> because I don't see why old-style figures should affect ligatures at
>>>>> all
>>>>> (not that I know anything about these things), and also because the
>>>>> second
>>>>> line should disable ligatures in small caps altogether.
>>>>>
>>>>> \definefontfeature[smallcaps][smallcaps][liga=no]
>>>>>
>>>>>  Did it work with this redefinition of the smallcaps feature?
>>>>
>>>> \definefontfeature[smallcaps][smallcaps][mode=node]
>>>>
>>>>  With \setfontfeature{oldstyle}, I don't seem to get any small caps at
>>> all in
>>> node mode. If I replace it with the line that you suggest below, small
>>> caps
>>> seem to work well regardless of mode. So, problem solved for me. Thanks!
>>>
>>
>> does \addfontfeaturetoset{oldstyle} work?
>>
>> That seems to behave the same as \setfontfeature{oldstyle}, i.e. it
> generates "GEOff". And again, I don't get small caps in node mode. So far,
> the only way to get small caps and old-style figures working properly
> together has been to use \setmainfont[Adobe Jenson
> Pro][oldstylefigures=yes], as suggested by Wolfgang.
>
> Here's my current test file, with all the different variations commented
> out:
>
> \usemodule[simplefonts]
> %\setfontfeature{oldstyle}
> %\addfontfeaturetoset{oldstyle}
> \definefontfeature[smallcaps][smallcaps][liga=no]
> %\definefontfeature[smallcaps][smallcaps][mode=node]
> %\setmainfont[Adobe Jenson Pro]
> \setmainfont[Adobe Jenson Pro][oldstylefigures=yes]
>
> \starttext
> {\sc Geoff} % GEOff or GEOFF?
>
> 1954 % do old-style figures work?
> \stoptext
>

I have to reply to my own mail because I just updated simplefonts and
noticed that the latest version behaves a bit differently. The
[oldstylefigures=yes] option still works perfectly, but now both
\setfontfeature{oldstyle} and \addfontfeaturetoset{oldstyle} result in small
caps not working at all.

Mika
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] Another small caps problem with some fonts (and old-style figures)

2009-09-24 Thread Mika Ritola
2009/9/23 Hans Hagen 

> Mika Ritola wrote:
>
>> 2009/9/22 Wolfgang Schuster 
>>
>>  Am 22.09.2009 um 12:43 schrieb Mika Ritola:
>>>
>>>  Hello again,
>>>
>>>> I just discovered another weird problem with small caps when using some
>>>> fonts, e.g. Adobe Jenson Pro or Adobe Garamond Pro.
>>>>
>>>> When old-style figures are enabled, the code below generates "GEOff"
>>>> instead of "GEOFF". Another ligature bug, it seems -- which is strange
>>>> because I don't see why old-style figures should affect ligatures at all
>>>> (not that I know anything about these things), and also because the
>>>> second
>>>> line should disable ligatures in small caps altogether.
>>>>
>>>> \definefontfeature[smallcaps][smallcaps][liga=no]
>>>>
>>>>  Did it work with this redefinition of the smallcaps feature?
>>>
>>> \definefontfeature[smallcaps][smallcaps][mode=node]
>>>
>>>  With \setfontfeature{oldstyle}, I don't seem to get any small caps at
>> all in
>> node mode. If I replace it with the line that you suggest below, small
>> caps
>> seem to work well regardless of mode. So, problem solved for me. Thanks!
>>
>
> does \addfontfeaturetoset{oldstyle} work?
>
> That seems to behave the same as \setfontfeature{oldstyle}, i.e. it
generates "GEOff". And again, I don't get small caps in node mode. So far,
the only way to get small caps and old-style figures working properly
together has been to use \setmainfont[Adobe Jenson
Pro][oldstylefigures=yes], as suggested by Wolfgang.

Here's my current test file, with all the different variations commented
out:

\usemodule[simplefonts]
%\setfontfeature{oldstyle}
%\addfontfeaturetoset{oldstyle}
\definefontfeature[smallcaps][smallcaps][liga=no]
%\definefontfeature[smallcaps][smallcaps][mode=node]
%\setmainfont[Adobe Jenson Pro]
\setmainfont[Adobe Jenson Pro][oldstylefigures=yes]

\starttext
{\sc Geoff} % GEOff or GEOFF?

1954 % do old-style figures work?
\stoptext

Mika
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] Another small caps problem with some fonts (and old-style figures)

2009-09-23 Thread Mika Ritola
2009/9/22 Wolfgang Schuster 

>
> Am 22.09.2009 um 12:43 schrieb Mika Ritola:
>
>  Hello again,
>>
>> I just discovered another weird problem with small caps when using some
>> fonts, e.g. Adobe Jenson Pro or Adobe Garamond Pro.
>>
>> When old-style figures are enabled, the code below generates "GEOff"
>> instead of "GEOFF". Another ligature bug, it seems -- which is strange
>> because I don't see why old-style figures should affect ligatures at all
>> (not that I know anything about these things), and also because the second
>> line should disable ligatures in small caps altogether.
>>
>> \definefontfeature[smallcaps][smallcaps][liga=no]
>>
>
> Did it work with this redefinition of the smallcaps feature?
>
> \definefontfeature[smallcaps][smallcaps][mode=node]
>
With \setfontfeature{oldstyle}, I don't seem to get any small caps at all in
node mode. If I replace it with the line that you suggest below, small caps
seem to work well regardless of mode. So, problem solved for me. Thanks!

 \setfontfeature{oldstyle}
>> \setmainfont[Adobe Jenson Pro]
>>
>
> \setmainfont[Adobe Jenson Pro][oldstylefigures=yes]
>

Mika
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


[NTG-context] Another small caps problem with some fonts (and old-style figures)

2009-09-22 Thread Mika Ritola
Hello again,

I just discovered another weird problem with small caps when using some
fonts, e.g. Adobe Jenson Pro or Adobe Garamond Pro.

When old-style figures are enabled, the code below generates "GEOff" instead
of "GEOFF". Another ligature bug, it seems -- which is strange because I
don't see why old-style figures should affect ligatures at all (not that I
know anything about these things), and also because the second line should
disable ligatures in small caps altogether.

\usemodule[simplefonts]
\definefontfeature[smallcaps][smallcaps][liga=no]
\setfontfeature{oldstyle}
\setmainfont[Adobe Jenson Pro]

\starttext
{\sc Geoff}
\stoptext

I'm using the latest beta from yesterday. Again, I'd appreciate a workaround
for this, apart from disabling old-style figures.

Thanks,

Mika

P.S. Thanks to everyone who's replied to my bibliography questions. I'll get
back to it as soon as I've had time to try out the suggestions.
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


Re: [NTG-context] Need help with bibliography

2009-09-20 Thread Mika Ritola
2009/9/20 Thomas A. Schmitz 

>
> On Sep 20, 2009, at 1:30 PM, Mika Ritola wrote:
>
>
>> 1. This one's probably very simple: there's the /insertauthors macro for
>> inserting the whole name of the author. But how do you insert just the last
>> name of the author?
>>
>>
> If you just want the last name, you can use \cite[author][], but
> I'm not sure if this what you're after, maybe you'll need to tell us more.
>
I'll try to give a clearer explanation. First of all, when I cite a source
using e.g. \cite[Smith2000], this should appear in the text as "Smith 2000".
I've already managed to do this. Now, each entry in the bibliography should
begin with the same string that was used to identify it within the text. So,
the above example should look something like this:

Smith 2000John Smith. Generic Book Title. Whatever Publishing Company,
New York 2000.

I know I can get the "John Smith" by using \insertauthors in
\setuppublicationlayout. But how do I get just the last name? The answer is
probably so simple that I should be ashamed that I can't figure it out by
myself but I haven't quite gotten the hang of ConTeXt and TeX yet...

>
>  2. This one, on the other hand, is likely to be rather non-trivial: the
>> bibliography needs to be broken up into several categories of sources. For
>> example, audiovisual sources, newspaper sources and books should be listed
>> under separate headings, somewhat like this:
>>
>> BIBLIOGRAPHY
>>
>> I. AUDIOVISUAL SOURCES
>>
>> [some sources]
>>
>> II. NEWSPAPER SOURCES
>>
>> [...]
>>
>> III. BOOKS
>>
>> [...]
>>
>> I've tried to decipher the source code of the Bib module but as I'm not
>> particularly fluent in TeX, I haven't been able to make much headway so far.
>> I'd appreciate some hints on where to start with this. I don't suppose
>> there's any existing code for something like this? Maybe I'd be better off
>> writing the bibliography by hand?
>>
>>  That sounds harder. You basically need three separate bibliographies,
> each of them sorted in some way. I'm not certain the current implementation
> of the bib module can do that (i.e. I'm almost certain it can't). How do you
> want to refer to these items in your text? Again, we'll probably need some
> more information about what you want to achieve.
>
> I think it would be easiest if I could refer to them in the usual way,
using \cite[Smith2000]. Of course, each item in the .bib file should have
some kind of a tag, so that ConTeXt could automagically insert it under the
correct heading.

Thanks,

Mika
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


[NTG-context] Need help with bibliography

2009-09-20 Thread Mika Ritola
Hello,

I'm planning to write my Master's thesis in history using ConTeXt, and I've
done some experimenting on it to see if it's actually suitable for my
purposes. Everything seems to be quite simple except for one thing: the
bibliography. The bibliography guidelines for our history department are
rather complex in comparison to the formats that come packaged with ConTeXt,
and I have no idea how to implement them. So far, I've run into two
problems:

1. This one's probably very simple: there's the /insertauthors macro for
inserting the whole name of the author. But how do you insert just the last
name of the author?

2. This one, on the other hand, is likely to be rather non-trivial: the
bibliography needs to be broken up into several categories of sources. For
example, audiovisual sources, newspaper sources and books should be listed
under separate headings, somewhat like this:

BIBLIOGRAPHY

I. AUDIOVISUAL SOURCES

[some sources]

II. NEWSPAPER SOURCES

[...]

III. BOOKS

[...]

I've tried to decipher the source code of the Bib module but as I'm not
particularly fluent in TeX, I haven't been able to make much headway so far.
I'd appreciate some hints on where to start with this. I don't suppose
there's any existing code for something like this? Maybe I'd be better off
writing the bibliography by hand?

Thanks for reading,

Mika
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___


[NTG-context] Small caps problem/bug with some fonts

2009-09-18 Thread Mika Ritola
Hello all,

For some reason, the snippet below outputs 'ThOMAS' instead of 'THOMAS.'
This seems to be font dependent; at least Adobe Jenson Pro and Adobe
Garamond Pro produce 'Th,' while the other fonts that I've tried produce
'TH', as expected. I don't know whether the bug exists in the fonts
themselves or in the way they are handled by ConTeXt or the Simplefonts
module, or possibly some other part of the system. In any case, could you
suggest a work-around, please?

I'm using ConText version 2009.09.16 20:07 and Simplefonts version
2009.09.15.


\usemodule[simplefonts]
\setmainfont[Adobe Jenson Pro]

\starttext
{\sc Thomas}
\stoptext


Thanks in advance,

Mika
___
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___