Re: [NTG-context] TEXMFMAIN problem in gwTeX (font installation)
Gerben Wierda wrote:
On Apr 29, 2005, at 15:03, Ville Voipio wrote (on the ConTeX list, but
this also is interesting for all gwTeX users):
I have spent some very interesting time trying to install the TeXlive
fonts by using texfont type-tmf.dat. What happened was that a lot of
complaints about unknown subpath ../afm/public/urw were given even
though the path should have been there. This is a known problem, has
been on several mailing lists, as well.
After a lot of thinking it became clear that texfont was really unable
to find any font files. By browsing through the texfont.pl, the reason
became evident: In gwTeX the root variables are:
TEXMFMAIN = /usr/local/teTeX/share/texmf
TEXMFTE = /usr/local/teTeX/share/texmf.tetex
The problem here is that all the TeXlive fonts (and almost everthing
else) is really in the TEXMFTE tree.
My quick'n'dirty was to make new file type-tmf-gwtex.dat by replacing
all occurrences of TEXMFMAIN by TEXMFTE. Running that one in batch
mode works fine.
Problem solved -- this time. But the solution is not a beautiful one.
Could someone suggest something cleaner? Or has this been solved
already (I tried googling after the answer without success)?
TEXMFMAIN in TL is now reserved for only the stuff that is directly
related to the binaries (like the pool files or anything that needs to
stay in sync - grammar wise - with the binaries and scripts). In TeX
Live the 'foundation' now lives in .../texmf-dist (TEXMFDIST) and not in
../texmf
In gwTeX, there are a few foundation trees: TEXMFTE for the teTeX tree
and TEXMFGW for my additions
I think it is a simplification by texfont that it has a hardwired
location. TeX is not set up that way. Probably the correct solution is
for texfont itself to act in a more dynamic way, e.g. by trying to
locate with kpsewhich some elements that are supposed to be there
already and take th eresult of that search as the settin for what it now
assumes to be hardwired.
In the meantime: your fix is correct.
generated fonts metrics are put in a given path:
if (defined($ENV{TEXMFLOCAL})) {
$installpath = TEXMFLOCAL ;
}
if (defined($ENV{TEXMFFONTS})) {
$installpath = TEXMFFONTS ;
}
if ($installpath eq ) {
$installpath = TEXMFLOCAL ; # redundant
}
and later on
my $fontroot= ; #/usr/people/gwhite/texmf-fonts
GetOptions
fontroot=s = \$fontroot,
and
if ($fontroot eq )
{ if ($dosish)
{ $fontroot = `kpsewhich -expand-path=\$$installpath` }
else
{ $fontroot = `kpsewhich -expand-path=\\\$$installpath` }
chomp $fontroot }
etc etc
I've added texmfdist to the search trees list
my $trees = 'TEXMFFONTS,TEXMFLOCAL,TEXMFEXTRA,TEXMFMAIN,TEXMFDIST' ;
(not that i use dist: the first thing i do here when i get tex live is merging
the main/dist/doc/extra trees)
btw, it's interesting that when i asked for a texmffonts entry long ago the
argument against was 'we don't want too many trees' but nowadays we have so many
trees that i no longer feel trouble by my own amount:
texmf
texmf-extra
texmf-local
texmf-fonts
texmf-projects
texmf-mswin
texmf-macosx
texmf-linux
etc -)
normally i try to use kpse to locate and report paths, but this is kind of slow
and the kpsewhich interface is not frozen [which is why in more recent scripts i
use a wrapper system around kpse, so in the end such problems may disappear]
Hans
-
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@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] TEXMFMAIN problem in gwTeX (font installation)
Gerben Wierda wrote: My quick'n'dirty was to make new file type-tmf-gwtex.dat by replacing all occurrences of TEXMFMAIN by TEXMFTE. Running that one in batch mode works fine. one can specify the fontroot on the commandline in most cases texfont is is used for installing fonts not in a tex tree (or in a local tree); given unpredictable changes in patterns and fonts, i'll probably put a context font metrics zip on the website anyway and include patterns in the main zip; moreover, the new fonts by the polish font gurus [lm, antykwa, kurier, iwona, etc] already come with context friendly metrics and names Hans - 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@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] TEXMFMAIN problem in gwTeX (font installation)
generated fonts metrics are put in a given path: And this is not the problem. I have to apologise for the bad wording of my previous message. I am not saying there would be anything wrong with the Perl script. The only slight annoyance there is the error message, which states: unknown subpath ../fonts/afm/$vendor/$collection At least to my eye this seems to refer to the parent directory (..), whereas it really doesn't. It just says that something/something/fonts/afm/$vendor/$collection is missing. Full path in that message would've gotten me to the goal a bit faster. The problem is really in the font installation script (type-tmf.dat). There the root (i.e. the source tree for the fonts) is explicitly given as TEXMFMAIN. And this does not work in gwTeX, because if something is given, it has to be TEXMFTE. As a summary: - texfont.pl is fine - gwTeX is fine - type-tmf.dat is not fine, but I really don't know how to reliably fix it (yes, patching is simple, but then it does not work in other distros) --- But am I doing something stupid (again)? I think I have some kind of understanding of the ConTeXt font mechanisms. However, I am still a bit confused about this mess. So, what is the easy, standard, newbie way to install the TeX Live font collection to be used with ConTeXt? Is it still using the type-tmf.dat batch file? - Ville ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] inserting toc
Hello, I want to insert a table of contents but all I get is the following error message in the created pdf-file: [part,chapter,section,subsection,subsubsection not found/processed] According to the mp-cb-en.pdf page 51/52 documentation I included the following lines to the setup area: \definelist[chapter] \setuplist [chapter] [before=\blank, after=\blank, style=bold] \definelist[section] \setuplist [section] [alternative=d] \definecombinedlist [contents] [chapter,section] [level=subsection] and \placecontent after the \starttext and in front of the first \chapter. What am I doing wrong here? Frank ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] volunteers wanted
Hi, The polish font gurus did it again: two more complete digitized fonts (latin, vietnamese, greek, cyrillic and math are covered); so ... the question is who is prepared to look into the encoding part of greek and cyrillic or more precise: with what encoding tfms should the font be shipped (the context friendly encoding-name scheme is used) Hans - 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@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] volunteers wanted
h h extern said this at Mon, 2 May 2005 15:14:20 +0200: Hi, The polish font gurus did it again: two more complete digitized fonts (latin, vietnamese, greek, cyrillic and math are covered); so ... the question is who is prepared to look into the encoding part of greek and cyrillic or more precise: with what encoding tfms should the font be shipped (the context friendly encoding-name scheme is used) Impressive stuff, there. Thomas, from what I've heard, it seems like they only handle monotonic greek for the moment. So for the Greek scholars/users out there, is the greek-antt.enc encoding that's out there sufficient? Is there a better canonical encoding? -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. [EMAIL PROTECTED] Lancaster University, InfoLab21+44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] volunteers wanted
On 5/2/05, h h extern [EMAIL PROTECTED] wrote: Hi, The polish font gurus did it again: two more complete digitized fonts (latin, vietnamese, greek, cyrillic and math are covered); so ... the question is who Wow, I'm so happy :) is prepared to look into the encoding part of greek and cyrillic or more precise: with what encoding tfms should the font be shipped (the context friendly encoding-name scheme is used) I'll test them for vietnamese support when they are available. Regards, ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] volunteers wanted
On May 2, 2005, at 3:47 PM, Adam Lindsay wrote: Impressive stuff, there. Thomas, from what I've heard, it seems like they only handle monotonic greek for the moment. So for the Greek scholars/users out there, is the greek-antt.enc encoding that's out there sufficient? Is there a better canonical encoding? Adam, was just about to volunteer for Greek... Yes, a quick glance at greek-antt.enc reveals that it seems to be a variation on iso-latin-7; it contains ASCII in the upper 128 bits and monotonic Greek in the lower half. This seems to be the standard for TeX users in Greece, it cannot be used for polytonic Greek. If the fonts are available AND contain Greek Extended (I haven't seen them yet), I would volunteer to cook up an encoding that would correspond to our enco-agr, would that be a useful thing to have? Best Thomas ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] TEXMFMAIN problem in gwTeX (font installation)
The problem is really in the font installation script (type-tmf.dat). There the root (i.e. the source tree for the fonts) is explicitly given as TEXMFMAIN. And this does not work in gwTeX, because if something is given, it has to be TEXMFTE. Just for my understanding. Does texfont.pl only read in TEXMFMAIN or does it also write (can it be a search path or does it require for TEXMFMAIN to be just one directory)? G ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] TEXMFMAIN problem in gwTeX (font installation)
Gerben Wierda said this at Mon, 2 May 2005 17:10:03 +0200: The problem is really in the font installation script (type-tmf.dat). There the root (i.e. the source tree for the fonts) is explicitly given as TEXMFMAIN. And this does not work in gwTeX, because if something is given, it has to be TEXMFTE. Just for my understanding. Does texfont.pl only read in TEXMFMAIN or does it also write (can it be a search path or does it require for TEXMFMAIN to be just one directory)? My understanding is that you can enter a comma-separated list of trees. The default is TEXMFFONTS,TEXMFLOCAL,TEXMFEXTRA,TEXMFMAIN. That suggests to me that the --ro=TEXMFMAIN defaults in the type-tmf.dat file probably should go away, as 1) they get in the way of over-rides at the CLI, and 2) it's covered by the current default, anyway. adam % texfont --help TeXFont 2.2.1 - ConTeXt / PRAGMA ADE 2000-2004 --fontroot=path : texmf destination font root (default: /usr/local/tetex/share/texmf.local) --rootlist=paths : texmf source roots (default: TEXMFFONTS,TEXMFLOCAL,TEXMFEXTRA,TEXMFMAIN) -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. [EMAIL PROTECTED] Lancaster University, InfoLab21+44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: FW: [NTG-context] install help
if you download the latest alpha release, the engine subpath stuff should work; if not, run: Please pardon my tedious questions. I have tried doing what you suggest, but I must be doing something wrong. I downloaded the alpha cont-tmf.zip. Then I unzipped it into an empty ~/texmf. Then I ran texhash and saw that it updated ~/texmf/ls-R. ctxtools --make --all(ruby script) To invoke ctxtools, I ran ruby ~/texmf/scripts/context/ruby/ctxtools.rb --make --all Nothing happened except the following output: CtxTools | version 1.2.2 - 2004/2005 - PRAGMA ADE/POD CtxTools | --bbeditinterfacegenerate bbedit syntax files [--pipe] CtxTools | --contextversion report context version CtxTools | --documentation generate documentation file [--type=] [filename]CtxTools | --jeditinterface generate jedit syntax files [--pipe] CtxTools | --patternfiles generate pattern files [languagecode|all] CtxTools | --purgefiles remove temporary files [--all] [basename] CtxTools | --rawinterface generate raw syntax files [--pipe] CtxTools | --sciteinterface generate scite syntax files [--pipe] CtxTools | --touchcontextfile update context version CtxTools | --translateinterface generate interface files (xml) [nl de ..] Inovking texexec on my tex file in either of the following incantations results in an error: perl ~/texmf/scripts/context/perl/texexec.pl --pdf myfile.tex /usr/TeX/bin/i386-linux/texexec --pdf myfile.tex This is a summary of all `failed' messages and warnings: `pdfetex -ini -jobname=cont-en -progname=context -8bit *cont-en.ini' failed warning: kpathsea: mktexpk output `! I can't read pdfetex.pool; bad path?' instead of a filename. Sorry, I can't find the format `cont-en.fmt'; will try `context.fmt'. kpathsea: Running mktexfmt context.fmt fmtutil: no info for format `context'. I can't find the format file `context.fmt'! So perhaps there are some other steps I am missing? Do I need to move updated scripts into /usr/TeX/bin/i386-linux ? Skip ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
RE: [NTG-context] TEXMFMAIN problem in gwTeX (font installation)
Just for my understanding. Does texfont.pl only read in TEXMFMAIN or does it also write (can it be a search path or does it require for TEXMFMAIN to be just one directory)? texfont.pl checks several places. By a very quick look at the sources, it looks for the following: TEXMFMAIN TEXMFLOCAL TEXMFEXTRA TEXMFFONTS It does not look for TEXMFTE, but by specifying the switch --rootlist, it can be given a list of trees, which it then browses through. Ok, it might be useful to add a few here, such as TEXMFTE (for us gwTeX users), but maybe that's an endless road. But the real problem is really in a font installation script which explicitly overrides the default settings and gives a wrong tree. --- The problem is easy to pinpoint into type-tfm.dat. Unfortunately, just removing the explicit definitions does not seem to solve the problem. The non-standard root seems to be difficult to be told to the system. For encodings, texfont.pl can be force-fed a value which is passed to all scripts in a batch file (using a special --en=? switch). However, no such mechanism exists for other parameters (such as the --ro). Tweaking the TEXMFFONTS to point to TEXMFTE is one possibility, but then the fonts will also be installed into TEXMFFONTS instead of TEXMFLOCAL. Ideally, it would be nice to be able to tell the script that the source fonts are in TEXMFWHATEVER and they are going into TEXMFSOMETHINGELSE. I haven't been able to figure out how to achieve that without tailoring the batch file. - Ville ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Capitalized headings
I've been trying to make capitalized (uppercase)
headings with little success. I'd like to have
the titles simply capitalized as with \cap or
\WORD.
A minimal example:
---
\setuphead[title][style=WORD]
\starttext
\title{This is a title}
The title should be \cap{capitalized} or \WORD{capitalized}.
\stoptext
---
What should I give as the style? I have tried the
following:
style=WORD - no effect
style=Caps - no effect
style=uppercased - no effect
style=CAP - no effect
style=Cap - no effect
style=cap - error
style=kap - error
style=smallcaps - small caps (when the font supports)
It is interesting to get an error message for the
style=cap, because this is one of the listed options
in the definition of \setuphead in the manual.
What did a do wrong?
- Ville
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Two hyphens do not give en dash
I installed a new font (Gentium, TrueType). Everything went relatively smoothly except for one thing: When I type -- I really get two hyphens instead of the expected en dash. I have been able to work around this by using UTF regime and typing the en dash into the source file. However, it would be easier to use -- and ---. What should I do? (Yeah, I know, forget it and be happy that the UTF works :) TIA, - Ville ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Two hyphens do not give en dash
Ville Voipio said this at Mon, 2 May 2005 20:56:28 +0300: I installed a new font (Gentium, TrueType). Everything went relatively smoothly except for one thing: When I type -- I really get two hyphens instead of the expected en dash. I have been able to work around this by using UTF regime and typing the en dash into the source file. However, it would be easier to use -- and ---. What should I do? (Yeah, I know, forget it and be happy that the UTF works :) Hi Ville. I'll assume you did it as you described on the Wiki (I made some suggestions on where to move the page). Try adding the --afmpl switch to your texfont command. It switches over to the afmpl utility, which does better with preserving ligatures and kerns. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. [EMAIL PROTECTED] Lancaster University, InfoLab21+44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
RE: [NTG-context] Two hyphens do not give en dash
Try adding the --afmpl switch to your texfont command. It switches over to the afmpl utility, which does better with preserving ligatures and kerns. Thank you! Now it works. I added this onto the Wiki page, as well. I did a few other changes there, as well (mostly according to your suggestions). - Ville ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] setuppagenumbering way=chapter and indexes
I'd like to reset the page number with each chapter and prepend the chapter number to the page number. Something like Chapter One Foo 1-1 Bar 1-2 Chapter Two Baz 2-1 Qux 2-3 Now here's where it gets complicated: I also need to generate an index using this same numbering. Index B Bar 1-2,2-1 Q Qux 1-1,2-3 I've played with many different approaches and can achieve 85% functionality, but generating the index is turning out to be killer. Any suggestions? Better yet, does anyone already have example code doing this? -- Stuart Jansen [EMAIL PROTECTED] Guru Labs, L.C. signature.asc Description: This is a digitally signed message part ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Capitalized headings
Ville Voipio said this at Mon, 2 May 2005 20:49:45 +0300:
I've been trying to make capitalized (uppercase)
headings with little success. I'd like to have
the titles simply capitalized as with \cap or
\WORD.
A minimal example:
---
\setuphead[title][style=WORD]
\starttext
\title{This is a title}
The title should be \cap{capitalized} or \WORD{capitalized}.
\stoptext
---
What did a do wrong?
I'm not sure you did do anything wrong: WORD is indeed a legal defined
alternativestyle, but it's not working.
However, this is a workaround, another way of attacking it (it can be
better, too, stylistically, as you can change the font independently):
\setuphead [title] [textcommand=\uppercase]
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Adam T. Lindsay, Computing Dept. [EMAIL PROTECTED]
Lancaster University, InfoLab21+44(0)1524/510.514
Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Changing Title Font in \completecontent
Is there a way to change the title font being used for a table of
contents page being displayed by \completecontent? My original
thought was to use the same layout as a regular chapter:
\chapter{Table of Contents}
\placecontents
but after reading the manuals a few times, I realized this was doomed
to fail. Using \completecontent, I'd like to be able to have
'Contents' or 'Table of Contents' written with my standard
\setuphead[chapter] definition. As it stands, \completecontent
generates a single roman 'Contents' at the top of the page while all
my other titles are offset in position, aligned right, and in small
caps...
Any ideas?
Many thanks,
Randall
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Pb compiling s-pre-61.tex
Hello !
Sorry, I'm a bit new to context ... but I try it for presentation
slides... And up to now, I like it very much ...
I tried to compile different examples included in the base
distribution ... but some, I fail to compile ... And I do not know
where I'm wrong ...
For example, I tried s-pre-61.tex to compile and it fails ... here is
the output of the compile process ...
# cp /usr/share/texmf/tex/context/base/s-pre-61.tex .
[EMAIL PROTECTED]:~/E/Context
# texexec --pdf --mode=demo s-pre-61.tex
TeXExec 3.1 - ConTeXt / PRAGMA ADE 1997-2002
executable : pdfetex
format : cont-en
inputfile : s-pre-61
output : pdftex
interface : en
current mode : demo
TeX run : 1
This is pdfeTeX, Version 3.14159-1.10b-2.1 (Web2C 7.4.5)
entering extended mode
(./s-pre-61.tex{/usr/share/texmf/pdftex/config/pdftex.cfg}
ConTeXt ver: 2003.1.31 fmt: 2005.1.21 int: english mes: english
language : language en is active
protectionstate 0
system : cont-new loaded
(/usr/share/texmf/tex/context/base/cont-new.tex
systems: beware: some patches loaded from cont-new.tex!
system (E-TEX) : [line 726] \ifcsname
)
system : cont-old loaded
(/usr/share/texmf/tex/context/base/cont-old.tex
loading: Context Old Macros
)
system : cont-fil loaded
(/usr/share/texmf/tex/context/base/cont-fil.tex
loading: Context File Synonyms
)
bodyfont : 12pt rm is loaded
language : patterns 2:2-en-2 3:2-uk-2 4:2-de-2 5:2-fr-2 6:2-es-2 7:2-it-2
8:2-nl-2 loaded
specials : tex,postscript,rokicki loaded
system : s-pre-61.top loaded
(./s-pre-61.top
specials : loading definition file tpd
(/usr/share/texmf/tex/context/base/spec-tpd.tex
specials : loading definition file fdf
(/usr/share/texmf/tex/context/base/spec-fdf.tex unprotect 3 unprotect 4
system (E-TEX) : [line 1815] \ifcsname
unprotect 5 protect 5 protect 4 protect 3)
specials : fdf loaded
unprotect 3 protect 3)
specials : fdf,tpd loaded
)
pdftex : needs map file: original-context-symbol.map
pdftex : needs map file: pl0-ams-cmr.map
pdftex : needs map file: original-vogel-symbol.map
system : macros of module pre-60 loaded
(/usr/share/texmf/tex/context/base/s-pre-60.tex
javascript : loading script set stp
(/usr/share/texmf/tex/context/base/java-stp.tex)
! Undefined control sequence.
l.38 \defineproperty
[step:busy][layer][state=start]
?
--
Oli
Laetius est, quoties magno sibi constat honestum.
Lucain, Pharsale, IX, 404.
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
