* Re: Re[2]: New Beta
@ 2001-08-24 16:14 David Arnold
2001-08-25 9:09 ` Re[4]: " Giuseppe Bilotta
2001-08-26 20:27 ` Re[2]: " Hans Hagen
0 siblings, 2 replies; 10+ messages in thread
From: David Arnold @ 2001-08-24 16:14 UTC (permalink / raw)
Cc: cs, ntg-context
Giuseppe,
This is a good question. There is a Miktex Options, upon which is a Tab for
TeX formats, where one can setup and build formats.
However, this is new to Miktex 2, and traditionally I have always followed
the following steps:
1. Download and extract the new Context beta from Pragma.
2. Set environment variables in texexec.rme and rename to texexec.ini.
3. Rename cont-sys.rme to cont-sys.tex.
Actually, in 2 and 3, I usually just adjust my old texexec.ini and
cont-sys.tex.
4. Run texexec --verbose to see if setting look good.
5. Run texexec --make to build the formats. Because the TeXFormatPath is
set in texexec.ini, the formats are created AND moved into the correct
place in my /localtexmf/miktex/fmt.
6. Then I run
texexec --make --alone metafun
This builds metafun.mem. Unfortunately, there is no environment variable I
have found yet in texexec.ini that will move this automatically to the
correct spot in my miktex distribution, so I must manually move metafun.mem
to \localtexmf\miktex\mem.
7. Then I run
texexec --make --alone --format=mptopdf
This places mptopdf.efmt in /locatexmf/miktex/fmt. Then I take runperl.exe
and rename it to mptopdf.exe. These all used to be in
\miktex\context\perltk, but Christian has moved texexec.exe into the
\miktex\miktex\bin directory, which is on the path created when Miktex is
installed. This is a cool piece of software which allows me to type
mptopdf filename.1
where filename.1 is Metapost output. The result is the file filename-1.pdf.
Nice, huh? The command also accepts wildcards, as in
mptopdf filename.? or mptopdf filename.*
Old habits die hard, so I'm not quite sure how I want to setup my new
Miktex, but I am learning.
At 04:14 PM 8/24/01 +0200, you wrote:
>
>OB> I have found that this is not texexec but solely MiKTeX problem, the
problem
>OB> is that it seems that MiKTeX accept only restricted lenght of its
arguments and
>OB> cuts off the rest of argument for each of arguments separately, so if
your
>OB> TeXFormatPath contains f:/LocalTeXMF/miktex/fmt, then command line
argument
>OB> --undump=f:/LocalTeXMF/miktex/fmt/cont-en are cut after /miktex, so
TeX think
>OB> you wish to use miktex.efmt, not cont-en.efmt. Once you changed
--undump= to &,
>OB> command line are shorter and ain't cut off. I don't know whether it's
fixed in
>OB> MiKTeX 2.1.
>
>Is it necessary to use TeXFormatPath? I let MiKTeX find the corred
>path (or rather put the format files in the default path ...)
>
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re[4]: New Beta
2001-08-24 16:14 Re[2]: New Beta David Arnold
@ 2001-08-25 9:09 ` Giuseppe Bilotta
2001-08-25 17:51 ` David Arnold
2001-08-26 19:14 ` Hans Hagen
2001-08-26 20:27 ` Re[2]: " Hans Hagen
1 sibling, 2 replies; 10+ messages in thread
From: Giuseppe Bilotta @ 2001-08-25 9:09 UTC (permalink / raw)
Cc: cs, ntg-context
David,
Friday, August 24, 2001 you wrote:
DA> 5. Run texexec --make to build the formats. Because the TeXFormatPath is
DA> set in texexec.ini, the formats are created AND moved into the correct
DA> place in my /localtexmf/miktex/fmt.
I move the formats by hand. This is basically the difference, I
believe. Anyway, you could probably report the "limited-length
cmdline" to Christian Schenk ... provided that it's a MiKTeX
limitation and not an operating system limitation as I suspect.
DA> 7. Then I run
DA> texexec --make --alone --format=mptopdf
DA> This places mptopdf.efmt in /locatexmf/miktex/fmt. Then I take runperl.exe
DA> and rename it to mptopdf.exe. These all used to be in
DA> \miktex\context\perltk, but Christian has moved texexec.exe into the
DA> \miktex\miktex\bin directory, which is on the path created when Miktex is
DA> installed.
Small question: where does the texexec.exe provided in the latest
MiKTeX look for the Perl things?
DA> This is a cool piece of software which allows me to type
DA> mptopdf filename.1
DA> where filename.1 is Metapost output. The result is the file filename-1.pdf.
DA> Nice, huh? The command also accepts wildcards, as in
DA> mptopdf filename.? or mptopdf filename.*
DA> Old habits die hard, so I'm not quite sure how I want to setup my new
DA> Miktex, but I am learning.
I wonder: doesn't the MiKTeX-prodived epstopdf do the same?
Hear you on the list,
Giuseppe
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Re[4]: New Beta
2001-08-25 9:09 ` Re[4]: " Giuseppe Bilotta
@ 2001-08-25 17:51 ` David Arnold
2001-08-26 18:46 ` Hans Hagen
2001-08-26 19:14 ` Hans Hagen
1 sibling, 1 reply; 10+ messages in thread
From: David Arnold @ 2001-08-25 17:51 UTC (permalink / raw)
Cc: ntg-context
Giuseppe,
At 11:09 AM 8/25/01 +0200, you wrote:
>David,
>
>Friday, August 24, 2001 you wrote:
>
>DA> 5. Run texexec --make to build the formats. Because the TeXFormatPath is
>DA> set in texexec.ini, the formats are created AND moved into the correct
>DA> place in my /localtexmf/miktex/fmt.
>
>I move the formats by hand. This is basically the difference, I
>believe.
I could move the formats by hand. At the moment, the Miktex Options, Tex
Formats tab has no options for metafun and mptopdf formats. These can be
place in there I am sure, but I've always liked the power of texexec.pl.
However, we probably should be thinking of the users that are new to
Context and Miktex and making the transition away from word processors such
as Word as painless as possible. And, right now, the Context installation
is not error free in the Miktex distribution.
>Anyway, you could probably report the "limited-length
>cmdline" to Christian Schenk ... provided that it's a MiKTeX
>limitation and not an operating system limitation as I suspect.
I have. I am waiting to see what information he has for us.
>DA> 7. Then I run
>
>DA> texexec --make --alone --format=mptopdf
>
>DA> This places mptopdf.efmt in /locatexmf/miktex/fmt. Then I take
runperl.exe
>DA> and rename it to mptopdf.exe. These all used to be in
>DA> \miktex\context\perltk, but Christian has moved texexec.exe into the
>DA> \miktex\miktex\bin directory, which is on the path created when Miktex is
>DA> installed.
>
>Small question: where does the texexec.exe provided in the latest
>MiKTeX look for the Perl things?
>
>DA> This is a cool piece of software which allows me to type
>
>DA> mptopdf filename.1
>
>DA> where filename.1 is Metapost output. The result is the file
filename-1.pdf.
>DA> Nice, huh? The command also accepts wildcards, as in
>
>DA> mptopdf filename.? or mptopdf filename.*
>
>DA> Old habits die hard, so I'm not quite sure how I want to setup my new
>DA> Miktex, but I am learning.
>
>I wonder: doesn't the MiKTeX-prodived epstopdf do the same?
Probably. I haven't used it as yet, probably because I have been an Acrobat
user for several years, which I use to convert my Matlab eps files to pdf
for inclusion in pdftex docs. There is a small explanation of mptopdf here:
http://www.pragma-ade.com/general/sources/mptopdf.pdf
A similar explanation exits on page 426 of:
http://www.pragma-ade.com/general/manuals/beta/metafun-s.pdf
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Re[4]: New Beta
2001-08-25 17:51 ` David Arnold
@ 2001-08-26 18:46 ` Hans Hagen
0 siblings, 0 replies; 10+ messages in thread
From: Hans Hagen @ 2001-08-26 18:46 UTC (permalink / raw)
Cc: Giuseppe Bilotta, ntg-context
At 10:51 AM 8/25/2001 -0700, David Arnold wrote:
>However, we probably should be thinking of the users that are new to
>Context and Miktex and making the transition away from word processors such
>as Word as painless as possible. And, right now, the Context installation
>is not error free in the Miktex distribution.
i will change whatever is needed, but need clear specs for that, otherwise
we end up in an add/remove loop; we should also assume the latest miktex; i
assume that both of you can work that out.
btw, there is a --setfile switch in texexec, that you can use to process a
dos-like batch file with set var=val lines; that way, you can for instance
set up winedt on win2k : texexec --setfile=prepare.bat .....
>I wonder: doesn't the MiKTeX-prodived epstopdf do the same?
that uses GS, while mptopdf uses tex and thereby produces small files with
the fonts properly embedded; since mptopdf is a simple plain based format,
it also runs fast.
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re[4]: New Beta
2001-08-25 9:09 ` Re[4]: " Giuseppe Bilotta
2001-08-25 17:51 ` David Arnold
@ 2001-08-26 19:14 ` Hans Hagen
1 sibling, 0 replies; 10+ messages in thread
From: Hans Hagen @ 2001-08-26 19:14 UTC (permalink / raw)
Cc: David Arnold, ntg-context
At 11:09 AM 8/25/2001 +0200, Giuseppe Bilotta wrote:
>I move the formats by hand. This is basically the difference, I
>believe. Anyway, you could probably report the "limited-length
>cmdline" to Christian Schenk ... provided that it's a MiKTeX
>limitation and not an operating system limitation as I suspect.
Context obeys the environment variable "TEXFORMATS" so here i use:
TEXFORMATS=E:\TEX/TEXMF-MSWIN/WEB2C
The current release of web2c / tex live has all internal pool/mem/etc vars
mapped onto this one
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Re[2]: New Beta
2001-08-24 16:14 Re[2]: New Beta David Arnold
2001-08-25 9:09 ` Re[4]: " Giuseppe Bilotta
@ 2001-08-26 20:27 ` Hans Hagen
1 sibling, 0 replies; 10+ messages in thread
From: Hans Hagen @ 2001-08-26 20:27 UTC (permalink / raw)
Cc: Giuseppe Bilotta, cs, ntg-context
At 09:14 AM 8/24/2001 -0700, David Arnold wrote:
>However, this is new to Miktex 2, and traditionally I have always followed
>the following steps:
>
>1. Download and extract the new Context beta from Pragma.
>2. Set environment variables in texexec.rme and rename to texexec.ini.
>3. Rename cont-sys.rme to cont-sys.tex.
>
>Actually, in 2 and 3, I usually just adjust my old texexec.ini and
>cont-sys.tex.
i think that this is not needed, unless there is a big change in texexec;
you only need to move the pl files to the right path [unless you have
context/perltk in your path]
the cont-sys.tex file is never part o fthe zip, so you can leave your local
copy untouched [actually, it should be undec /tex/context/usr so that you
can safely delete the base path] Of course it's always a good idea to look
into cont-sys.rme esp now, since some font defaults go there, but in a
while it will stabelize
>4. Run texexec --verbose to see if setting look good.
ok
>5. Run texexec --make to build the formats. Because the TeXFormatPath is
>set in texexec.ini, the formats are created AND moved into the correct
>place in my /localtexmf/miktex/fmt.
>6. Then I run
>
>texexec --make --alone metafun
no --alone needed there since fmtutil does not support mem's at all
>This builds metafun.mem. Unfortunately, there is no environment variable I
>have found yet in texexec.ini that will move this automatically to the
>correct spot in my miktex distribution, so I must manually move metafun.mem
>to \localtexmf\miktex\mem.
hm. there are three ways to set the path: automatically (kpsewhich),
manually (env var) or in the ini file and i now see that the last one is
not supported for mp. I've added it and let it default to TeXFormatPath so
you don't need to change / add something.
>7. Then I run
>
>texexec --make --alone --format=mptopdf
texexec --make --alone mptopdf
will do too, i'll also make that one alone by default
>This places mptopdf.efmt in /locatexmf/miktex/fmt. Then I take runperl.exe
>and rename it to mptopdf.exe. These all used to be in
>\miktex\context\perltk, but Christian has moved texexec.exe into the
>\miktex\miktex\bin directory, which is on the path created when Miktex is
>installed. This is a cool piece of software which allows me to type
>
>mptopdf filename.1
>
>where filename.1 is Metapost output. The result is the file filename-1.pdf.
>Nice, huh? The command also accepts wildcards, as in
>
>mptopdf filename.? or mptopdf filename.*
>
>Old habits die hard, so I'm not quite sure how I want to setup my new
>Miktex, but I am learning.
never change old habits when they are ok, so let me fix things that are
broken instead -)
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
^ permalink raw reply [flat|nested] 10+ messages in thread
* new beta
@ 2002-12-01 0:15 Hans Hagen
2002-12-01 9:18 ` Giuseppe Bilotta
0 siblings, 1 reply; 10+ messages in thread
From: Hans Hagen @ 2002-12-01 0:15 UTC (permalink / raw)
Hi,
I uploaded a new beta. Most changes / updates / new features will go
unnoticed until documented (column sets, more float placements and control,
more clever and efficient text backgrounds -also in tables, and floats);
since i use these features in some styles, they finally will be documented
-) Of course there are also some fixes.
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
^ permalink raw reply [flat|nested] 10+ messages in thread
* New Beta
@ 2001-08-21 1:02 David Arnold
2001-08-24 8:31 ` Olya Briginets
0 siblings, 1 reply; 10+ messages in thread
From: David Arnold @ 2001-08-21 1:02 UTC (permalink / raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 1099 bytes --]
All,
I don't have the very latest Miktex, but a reasonably new one (Miktex 2
with Update 1). I unpacked the new Context beta (texexec.ini attached) and
used Miktex Options->Tex Formats to build formats for pdfelatex and
pdfetex, refreshing the filename database whenever I could.
texexec --make
seemed to go well (I have the eformats in \localtexmf\miktex\fmt. But when
I compile this sample file,
\starttext \framed {Lets see if it works.} \stoptext
I got this error message:
F:\ConTeXt\MyWork>texexec junk
TeXExec 2.5 - ConTeXt / PRAGMA ADE 1997-2001
executable : pdfetex
format : f:/localtexmf/miktex/fmt/cont-en
inputfile : junk
output : standard
interface : en
current mode : all
TeX run : 1
This is pdfeTeX, Version 3.14159-14f-released-20000525-2.1 (MiKTeX 2 UP 1)
initexmf: don't know how to dump miktex
cannot make f:/localtexmf/miktex.efmt
I can't find the default format file!
run time : 1 seconds
Has anyone experienced this before and know how to cure the problem?
[-- Attachment #2: texexec.ini --]
[-- Type: text/plain, Size: 4590 bytes --]
% == introduction ==
%
% This is 'texexec.ini', the file used by texexec to determine where
% to find files, what TeX to use, what flags to pass, etc. Although
% TeXexec tries to locate things itself, a little help is sometimes
% needed. One can influence texexec by setting some variables. These
% are only needed when the automatic determined settings fail.
%
% == interfacing ==
%
% UsedInterfaces nl,en the formats generated with --make
% UserInterface nl the default format used
%
% == binaries ==
%
% TeXExecutable pdfetex the TeX binary to use
% MpExecutable mpost the MetaPost binary to use
% MpToTeXExecutable mpto the MetaPost to TeX converter
% DviToMpExecutable dvitomp the DVI to MetaPost converter
%
% == Scripts ==
%
% DviSpecialScript dvispec the DVI special filter script
%
% == flags ==
%
% TeXFormatFlag & the format introducer
% TeXVirginFlag -ini the format generation switch
%
% == paths ==
%
set TeXFormatPath to f:/localtexmf/miktex/fmt
set ConTeXtPath to f:/Miktex/tex/context/base
set SetupPath to f:/Miktex/tex/context/base
set TeXScriptsPath to f:/Miktex/context/perltk
% TeXFontsPath texmf font files
%
% == the main shell setting ==
%
% As shown below, one can define his/her own sections. We default to
% the teTeX/fpTeX web2c based settings.
%set TeXShell to tetex
%set TeXShell to fptex
set TeXShell to miktex
%set TeXShell to private
% == setting up the variables ==
%
% Here are some general defaults. They can be overruled later.
set UsedInterfaces to en nl de uk
set UserInterface to en
set TeXExecutable to tex
set MpExecutable to mpost
set MpToTeXExecutable to mpto
set DviToMpExecutable to dvitomp
set DviSpecialScript to dvispec
set MpFormat to metafun
set TeXFormatFlag to &
set MpFormatFlag to &
%set TeXFontsPath to l:/tex/texmf;l:/tex/texmf-local;
% For teTeX the next settings will do.
for tetex set TeXExecutable to pdfetex
for tetex set TeXVirginFlag to -ini
for tetex set TeXPassString to -progname=context
for tetex set TeXBatchFlag to -int=batchmode
for tetex set MpToTeXExecutable to mpto
for tetex set MpVirginFlag to -ini
for tetex set MpPassString to -progname=mpost
for tetex set MpBatchFlag to -int=batchmode
% These also apply to fpTeX.
for fptex set TeXExecutable to pdfetex
for fptex set TeXVirginFlag to -ini
for fptex set TeXPassString to -progname=context
for fptex set TeXBatchFlag to -int=batchmode
for fptex set MpToTeXExecutable to mpto
for fptex set MpVirginFlag to -ini
for fptex set MpPassString to -progname=mpost
for fptex set MpBatchFlag to -int=batchmode
% MikTeX users probably have to set up some paths too.
for miktex set TeXExecutable to pdfetex
for miktex set TeXVirginFlag to --initialize
for miktex set TeXBatchFlag to --interaction=batchmode
for miktex set MpToTeXExecutable to mptotex
for miktex set MpVirginFlag to --initialize
for miktex set MpPassString to
for miktex set MpBatchFlag to --interaction=batchmode
for miktex set TeXFormatFlag to --undump=
for miktex set MpFormatFlag to --undump=
% These are the settings used on some machines at PRAGMA ADE that
% don't use the texmf tree. They can serve as an example for local
% settings. Local settings should either be added to the previous
% one, or go without the 'for' directives. Consider these
% settings as an example.
for private set UsedInterfaces to en nl
for private set UserInterface to nl
for private set ConTeXtPath to t:/sources/
for private set SetupPath to t:/perl/
for private set TeXScriptsPath to t:/perl/
% == read this too ==
%
% If this file is called 'texexec.rme', copy it to 'texexec.ini',
% check the settings above, change them according to your TeX
% distribution, and say:
%
% texexec --verbose
%
% When set up properly, you should see your local settings fly by.
% When these settings are ok, the next call should work:
%
% texexec --make
%
% and you should be able to process a file by saying
%
% texexec filename
%
% See 'mtexexec.pdf' for more information on the flags you can use with
% 'texexec'. Also make sure you have the 'texutil' script installed in
% the same path as 'texexec'.
% Experimental
%
% set TcXPath to d:/tex/texmf/web2c
% set FmtLanguage to pl
% set FmtBodyFont to plr
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: New Beta
2001-08-21 1:02 New Beta David Arnold
@ 2001-08-24 8:31 ` Olya Briginets
2001-08-24 14:14 ` Re[2]: " Giuseppe Bilotta
0 siblings, 1 reply; 10+ messages in thread
From: Olya Briginets @ 2001-08-24 8:31 UTC (permalink / raw)
Hello David,
David Arnold wrote:
[skipped]
> This is pdfeTeX, Version 3.14159-14f-released-20000525-2.1 (MiKTeX 2 UP 1)
> initexmf: don't know how to dump miktex
> cannot make f:/localtexmf/miktex.efmt
> I can't find the default format file!
>
> run time : 1 seconds
>
> Has anyone experienced this before and know how to cure the problem?
I have found that this is not texexec but solely MiKTeX problem, the problem
is that it seems that MiKTeX accept only restricted lenght of its arguments and
cuts off the rest of argument for each of arguments separately, so if your
TeXFormatPath contains f:/LocalTeXMF/miktex/fmt, then command line argument
--undump=f:/LocalTeXMF/miktex/fmt/cont-en are cut after /miktex, so TeX think
you wish to use miktex.efmt, not cont-en.efmt. Once you changed --undump= to &,
command line are shorter and ain't cut off. I don't know whether it's fixed in
MiKTeX 2.1.
Olya
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re[2]: New Beta
2001-08-24 8:31 ` Olya Briginets
@ 2001-08-24 14:14 ` Giuseppe Bilotta
2001-08-24 16:10 ` Hans Hagen
0 siblings, 1 reply; 10+ messages in thread
From: Giuseppe Bilotta @ 2001-08-24 14:14 UTC (permalink / raw)
Cc: ntg-context
OB> I have found that this is not texexec but solely MiKTeX problem, the problem
OB> is that it seems that MiKTeX accept only restricted lenght of its arguments and
OB> cuts off the rest of argument for each of arguments separately, so if your
OB> TeXFormatPath contains f:/LocalTeXMF/miktex/fmt, then command line argument
OB> --undump=f:/LocalTeXMF/miktex/fmt/cont-en are cut after /miktex, so TeX think
OB> you wish to use miktex.efmt, not cont-en.efmt. Once you changed --undump= to &,
OB> command line are shorter and ain't cut off. I don't know whether it's fixed in
OB> MiKTeX 2.1.
Is it necessary to use TeXFormatPath? I let MiKTeX find the corred
path (or rather put the format files in the default path ...)
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re[2]: New Beta
2001-08-24 14:14 ` Re[2]: " Giuseppe Bilotta
@ 2001-08-24 16:10 ` Hans Hagen
0 siblings, 0 replies; 10+ messages in thread
From: Hans Hagen @ 2001-08-24 16:10 UTC (permalink / raw)
Cc: Olya Briginets, ntg-context
At 04:14 PM 8/24/2001 +0200, Giuseppe Bilotta wrote:
>OB> I have found that this is not texexec but solely MiKTeX problem, the
>problem
>OB> is that it seems that MiKTeX accept only restricted lenght of its
>arguments and
>OB> cuts off the rest of argument for each of arguments separately, so if your
>OB> TeXFormatPath contains f:/LocalTeXMF/miktex/fmt, then command line
>argument
>OB> --undump=f:/LocalTeXMF/miktex/fmt/cont-en are cut after /miktex, so
>TeX think
>OB> you wish to use miktex.efmt, not cont-en.efmt. Once you changed
>--undump= to &,
>OB> command line are shorter and ain't cut off. I don't know whether it's
>fixed in
>OB> MiKTeX 2.1.
>
>Is it necessary to use TeXFormatPath? I let MiKTeX find the corred
>path (or rather put the format files in the default path ...)
it depends on how many texmf trees you use: here i have a couple -)
but, you can of course let miktex sort things out since on windows there is
less chance on write permission problems
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2002-12-02 11:38 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-08-24 16:14 Re[2]: New Beta David Arnold
2001-08-25 9:09 ` Re[4]: " Giuseppe Bilotta
2001-08-25 17:51 ` David Arnold
2001-08-26 18:46 ` Hans Hagen
2001-08-26 19:14 ` Hans Hagen
2001-08-26 20:27 ` Re[2]: " Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2002-12-01 0:15 new beta Hans Hagen
2002-12-01 9:18 ` Giuseppe Bilotta
2002-12-01 11:38 ` Re[2]: " Giuseppe Bilotta
2002-12-02 11:38 ` Hans Hagen
2001-08-21 1:02 New Beta David Arnold
2001-08-24 8:31 ` Olya Briginets
2001-08-24 14:14 ` Re[2]: " Giuseppe Bilotta
2001-08-24 16:10 ` Hans Hagen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).