[NTG-context] Re: texfont and type-tmf.dat
Nigel King <[EMAIL PROTECTED]> writes: Hi, > I hadn't expected to create such a confusion so I will try to restate my > problem. Well, it is not the first time Hans and I discuss about this issue... Sorry, I don't use texfont and I don't use Gerbens iinstaller TeX. (TeXlive). I can't help you with this. Why do you whish to reinstall all the supplied fonts? Or do you just want to learn how to use texfont? Patrick -- You are your own rainbow! ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Re: texfont and type-tmf.dat
All, I hadn't expected to create such a confusion so I will try to restate my problem. On MacOSX Gerben has provided a restructured version of tetex where the locations of some files have changed. I am not sure of the detailed reasons for this but it certainly much easier to keep up to date. For instance he even provides an updater for ConTeXt to beta or standard using a single click (I only just found that! Thanks Gerben). Now the line texfont --en=8r --ve=urw --co=courier --so=auto Should work but instead gives TeXFont 1.8 - ConTeXt / PRAGMA ADE 2000-2003 processing aborted : unknown subpath ../fonts/afm/urw/courier The subpath exists but maybe at a different root /usr/local/teTeX/share/texmf.tetex/fonts/afm/urw/courier thus I presume that --fontroot should be invoked especially since the help gives me --fontroot=path : texmf font root (default: /usr/local/tetex/share/texmf.local) So I try texfont --en=8r --ve=urw --co=courier --so=auto --fontroot=/usr/local/teTeX/share/texmf.tetex/ on one line of course processing aborted : unknown subpath ../fonts/afm/urw/courier is the result. The apparent error is that the --fontroot option doesn't work. Hopefully that is all I wanted fixed. Texfont has been upgraded with many new options but this 'bug' remains. TIA -- Nigel ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Re: combination figures
Ed L Cashin <[EMAIL PROTECTED]> writes:
> Hi. I have the following code in my source, to try to get a
> combination of two figures in one:
>
> \placefigure
> {10,000 random|-|value pixels added}
> \startcombination[2]
> {\externalfigure[noise1][height=.4\textwidth]}{image 1}
> {\externalfigure[noise2][height=.4\textwidth]}{image 2}
> \stopcombination
>
> ... but I get an error, so I am probably doing something wrong. The
> whole log is below. My context version is pretty new, as the
> transcript shows.
On a hunch I put curly braces around the second argument to
placefigure, and it works now.
\placefigure
{10,000 random|-|value pixels added}
{\startcombination[2]
{\externalfigure[noise1][height=.4\textwidth]}{image 1}
{\externalfigure[noise2][height=.4\textwidth]}{image 2}
\stopcombination}
That's great!
--
--Ed L Cashin| PGP public key:
[EMAIL PROTECTED]| http://noserose.net/e/pgp/
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] combination figures
Hi. I have the following code in my source, to try to get a
combination of two figures in one:
\placefigure
{10,000 random|-|value pixels added}
\startcombination[2]
{\externalfigure[noise1][height=.4\textwidth]}{image 1}
{\externalfigure[noise2][height=.4\textwidth]}{image 2}
\stopcombination
... but I get an error, so I am probably doing something wrong. The
whole log is below. My context version is pretty new, as the
transcript shows.
Thanks for any advice!
system : cont-new loaded
(/opt/teTeX-1.0.7/share/texmf/tex/context/base/cont-new.tex
systems: beware: some patches loaded from cont-new.tex!
)
system : cont-old loaded
(/opt/teTeX-1.0.7/share/texmf/tex/context/base/cont-old.tex
loading: Context Old Macros
)
system : cont-fil loaded
(/opt/teTeX-1.0.7/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 7:2-it-2 2-nl-2 l
oaded
specials : tex,postscript,rokicki loaded
system : p.top loaded
(./p.top
specials : loading definition file tpd
(/opt/teTeX-1.0.7/share/texmf/tex/context/base/spec-tpd.tex
systems: please update your pdfTeX binaries
specials : loading definition file fdf
(/opt/teTeX-1.0.7/share/texmf/tex/context/base/spec-fdf.tex
system (E-TEX) : [line 1907] \ifcsname
)
specials : fdf loaded
)
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
(./p.tuo) (./p.tuo) (./p.tuo) (./p.tuo) (./p.tuo) (./p.tuo) (./p.tuo) (./p.tuo)
(./p.tuo) (./p.tuo) (./p.tuo) (./p.tuo) (./p.tuo) (./p.tuo)
systems: begin file p at line 6
section: 1 Image Conditioning
subsection : 1.1 Noise addition
! Missing { inserted.
\let
\noshowargumenterror ->\let
\expectedarguments \noexpectedarguments
\dodoubleempty #1->\noshowargumenterror
\doifnextcharelse [{\dodoubletestemp...
l.27 \startcombination
[2]
?
! Emergency stop.
\let
\noshowargumenterror ->\let
\expectedarguments \noexpectedarguments
\dodoubleempty #1->\noshowargumenterror
\doifnextcharelse [{\dodoubletestemp...
l.27 \startcombination
[2]
! ==> Fatal error occurred, the output PDF file not finished!
Transcript written on p.log.
return code : 256
run time : 1 seconds
total run time : 1 seconds
make: *** [p.pdf] Error 1
Compilation exited abnormally with code 2 at Thu Oct 9 11:19:52
--
--Ed L Cashin| PGP public key:
[EMAIL PROTECTED]| http://noserose.net/e/pgp/
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] Re: texfont and type-tmf.dat
Hi, > hm, there are more font experts (nelson b, boguslaw j, adam t, tom k, > some people on this list as well, to mention a few), You are right, I should restrict my statement to "font expert with respect to the URW/Adobe base14/35 thing" (but not limited to...) > here is what Nelson Beebe says about this topic in a different > thread .. Well, it is the same thread, and I quoted Walters *answer* to Nelson Beebe. (But I did not have a copy of Nelson's mail yet). Patrick -- You are your own rainbow! ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] Re: texfont and type-tmf.dat
At 11:00 09/10/2003, you wrote:
Hi,
Hans Hagen <[EMAIL PROTECTED]> writes:
>>So what is wrong with adobekb.tex? It is now included in ConTeXt, so
>>with \usetypescript[adobekb][someencoding] your psnfss fonts should
>>work fine.
>
> i can make a default for that but only when i can be absolutely sire
> that the metrics are there that i want there to be -)
According to to the statements from Walter Schmidt, a TeX font expert
(perhaps I should say *the* TeX font expert?) in
http://tug.daimi.au.dk/archives/tex-fonts/msg01328.html
\quote{%
Note, however, that embedding of URW's fonts, while using the
(PSNFSS) Adobe Base35 metrics, will _not_ lead to any bugs!
The character metrics are matching! Differences in the
"character bounding boxes" are irrelevant for the advance widths!
The only drawback is, that you cannot access those glyphs that
are in the URW fonts, but not in the Adobe fonts. Indeed, this
could be overcome by providing particular metrics and VFs for
the URW fonts -- see below. }
hm, there are more font experts (nelson b, boguslaw j, adam t, tom k, some
people on this list as well, to mention a few), here is what Nelson Beebe
says about this topic in a different thread ..
> > Walter confirms what I have assumed: we can use the "Adobe" metrics from
> > the PSNFSS bundle with the URW fonts.
I have serious reservations about this.
While as far as I know, there has been only one release of URW fonts,
and thus only one pair of (.pf[ab],.afm) files for each typeface, with
Adobe fonts, over the last 19 years, there have been silent changes
made to at least AFM files for many fonts, including Times-Roman.
This makes me suspect that the base-14 or base-35 fonts embedded in
tens of millions of laser printers with Adobe PostScript
implementations may in fact not be identical, even though they share
common font names.
Of course, the changes are usually pretty small, and few people would
ever notice. However, precise character positioning demands knowledge
of metrics, and if a TeX job uses metrics which differ from those
embedded with a font in a printer, and uses the resident fonts, rather
than downloading them, then output will certainly not be what TeX (and
the user) intended. That is one reason why I've never been entirely
happy with fontless PostScript and PDF files, and why I was
exceedingly unhappy with the change in Adobe Illustrator last year
that completely ignores embedded fonts, and uses only installed fonts.
The program MIME-attached below can be used to compare AFM files, and
I have just done so with the
texlive7/texmf/fonts/afm/{adobe,urw}/times/*.afm files.
The first thing to note is that the URW fonts contain many more
glyphs: 316 for Times-Roman compared to Adobe's 228. A TeX file that
used any of the additional URW glyphs would print incorrectly with
Adobe's Times-Roman.
The second thing is that the bounding boxes can be a bit different,
and sometimes very different, even when the widths are identical:
% awk -f afmdiff.awk /tmp/afm/adobe/times/ptmr8a.afm
/tmp/afm/urw/times/utmr8a.afm
Comparison of AFM metrics in files:
/tmp/afm/adobe/times/ptmr8a.afm /tmp/afm/urw/times/utmr8a.afm
Font names: Times-Roman NimbusRomNo9L-Regu
...
WX width differences:
Bounding box width differences:
dagger-1 dieresis -1 dotaccent
-1
exclam 1 exclamdown 1 Idieresis
-1
idieresis 39 three -1
threesuperior -1
Bounding box height differences:
Adieresis 1 adieresis 1 aring
-10
Aring-17 asciitilde 6 dieresis
1
dotaccent 1 Edieresis 1 edieresis
1
exclamdown-2 greater -4 Idieresis
1
idieresis 1 less -4 Odieresis
1
odieresis 1 plusminus-62 q
-1
questiondown -2 s 1 Udieresis
1
udieresis 1 Ydieresis 1 ydieresis
1
TeX uses more than just the bare width, so I suspect that we can
readily demonstrate different typesetting with these two
purportedly-compatible Times-Roman fonts from URL and Adobe. As a
simple experiment, I created two DVI files with "tex testfont", like
this:
% tex testfont
This is TeX, Version 3.1415 (C version 6.1)
(/usr/local/lib/tex/inputs/testfont.tex
Name of the font to test = ptmr8r
Now type a test command (\help for help):)
*\table
*\bye
[1]
Output written on testfont.dvi (1 page, 10632 bytes).
Transcript written on testfont.log.
% mv testfont.dvi testfont-ptmr8r.dvi
and similarly for utmr8r. I then ran dv2dt on both, and compared the
output:
%
[NTG-context] Re: texfont and type-tmf.dat
Hi,
Hans Hagen <[EMAIL PROTECTED]> writes:
>>So what is wrong with adobekb.tex? It is now included in ConTeXt, so
>>with \usetypescript[adobekb][someencoding] your psnfss fonts should
>>work fine.
>
> i can make a default for that but only when i can be absolutely sire
> that the metrics are there that i want there to be -)
According to to the statements from Walter Schmidt, a TeX font expert
(perhaps I should say *the* TeX font expert?) in
http://tug.daimi.au.dk/archives/tex-fonts/msg01328.html
\quote{%
Note, however, that embedding of URW's fonts, while using the
(PSNFSS) Adobe Base35 metrics, will _not_ lead to any bugs!
The character metrics are matching! Differences in the
"character bounding boxes" are irrelevant for the advance widths!
The only drawback is, that you cannot access those glyphs that
are in the URW fonts, but not in the Adobe fonts. Indeed, this
could be overcome by providing particular metrics and VFs for
the URW fonts -- see below. }
Patrick
--
You are your own rainbow!
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] first attempt to run mp (system error) -- summary?
Am Mittwoch, 08.10.03, um 22:19 Uhr (Europe/Zurich) schrieb Pawel Jackowski na Onet: From: "Patrick Gundlach" <[EMAIL PROTECTED]> Sent: Wednesday, October 08, 2003 6:32 PM you don't need --automprun. Everything should work fine w/o. I tried to omit this option, but without that MetaPost doesn't run at all. Did you uncomment the MP entries in cont-usr.tex? (That is, copy cont-usr.ori to cont-usr.tex and change that.) After that you must re-generate the formats and run texhash (=mktexlsr). Grüßlis vom Hraban! -- http://www.fiee.net/texnique/ ___ ntg-context mailing list [EMAIL PROTECTED] http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] \index + \definedescription
Hi Pavel
At 06:27 09.10.2003, Pavel Stupin wrote:
Hello,
In my document, I have a description defined in this way:
\definedescription[DictEntry][headstyle=bold,location=serried,width=broad]
I use the DictEntry description like this:
*
\startDictEntry{Walters, Barbara (1931- )}
a US television journalist known especially for her series
Barbara Walters Special...
\stopDictEntry
\startDictEntry{Waterhouse, Keith (1929- )}
an English journalist and writer of novels and plays...
\stopDictEntry
\startDictEntry{West, Rebecca (1892-1983)}
an English writer and journalist. She wrote many novels...
\stopDictEntry
... etc.
*
What I would like to do is to automatically create an \index{}
for every DictEntry so that every entry then appear in the
register. Probably, I should use 'between' parameter when
defining my DictEntry description, but I'm confused with what
should be the proper argument in 'between=\index{???}. I would
appreciate any help.
Possibly the following approach can help:
Define a list \definelist[name][options]
Write to this list at each entry of the description \writetolist[name]{text}
At the spot where the list should occur \placelist[name]
Programmers might write a macro which could be used in the description
definition together with e.g. [after=\TheMacro] which writes into the list.
Willi
___
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context
