Re: documentation buglet
Thomas Esser <[EMAIL PROTECTED]> writes:
>> I guess xdvik should try to mimick teTeX's defaults as close as
>> possible (because most people installing xdvik will already have
>> teTeX installed).
> Well, the xdvik in teTeX does not install any map or config file nor
> does it install the app-default file. If you want to follow, you need
> to add some works about "manual installation" of these files or provide
> a separate install-target ("install-extradata" or whatever name).
OK, I'll do that.
>> Should we remove (or do nothing for) the .map and .cfg files in
>> the texmf subtree in a teTeX install? I.e. only install XDvi?
> I vote for "do nothing for". For people doing a manual installation of
> these files, I can send you my latest copies if you want.
I guess I can use the files from tetex-beta, which I regularly
update ;-)
Thanks for the suggestions!
--
Stefan Ulrich
Re: documentation buglet
> I guess xdvik should try to mimick teTeX's defaults as close as
> possible (because most people installing xdvik will already have
> teTeX installed).
Well, the xdvik in teTeX does not install any map or config file nor
does it install the app-default file. If you want to follow, you need
to add some works about "manual installation" of these files or provide
a separate install-target ("install-extradata" or whatever name).
> fonts). Do we need some configure stuff for that, or can we maybe
> just rely on falling back to the PK fonts in that case, and maybe
> improve the explanation in the INSTALL file?
I guess that people fetching a separate xdvik will propably be reading
the INSTALL file, too. So, it should suffice to rely on falling back.
> Should we remove (or do nothing for) the .map and .cfg files in
> the texmf subtree in a teTeX install? I.e. only install XDvi?
I vote for "do nothing for". For people doing a manual installation of
these files, I can send you my latest copies if you want.
Thomas
Re: documentation buglet
Thomas Esser <[EMAIL PROTECTED]> writes: > That's why I prefer to use "my own" ps2pk.map file instead of xdvik's. As > a stand-alone package (i.e. when not distributed as part of teTeX), > xdvik is in a much different positon. I don't know what the right thing > to to is. I guess xdvik should try to mimick teTeX's defaults as close as possible (because most people installing xdvik will already have teTeX installed). The problem of course is what to do for the different versions of teTeX (I believe the extensible ps2pk.map came with teTeX-beta, and in teTeX-1.0 it had only support for the 35 standard PS fonts). Do we need some configure stuff for that, or can we maybe just rely on falling back to the PK fonts in that case, and maybe improve the explanation in the INSTALL file? Currently the texmf subtree in the `main' xdvik distro on CTAN or sourceforge is rather outdated (e.g. it doesn't even contain a ps2pk.map, but manually assembled files for the various font bundles). Also the `make install' is broken in that it doesn't touch the files in texmf (which maybe is safer anyway ...). > The problem of installing ps2pk.map into texmf/xdvi whereas teTeX's > updmap maintains the file in texmf/dvips/config is a problem, though. > Imageine that some teTeX user just wants to update xdvik and thus gets > a new ps2pk.map file which disables the file that he wants to use... > Any idea? Should we remove (or do nothing for) the .map and .cfg files in the texmf subtree in a teTeX install? I.e. only install XDvi? Best, Stefan
Re: documentation buglet
> This patch should be self-explanatory. Absolutely, thanks a lot. I just have spotted a related problem with the 20020530-pretest. By "make install" inside xdvik, a ps2pk.map file gets installed in texmf/xdvi. This file should be removed. Otherwise, xdvi will use this file instead of the file generated by updmap... This will be fixed in the next pretest. Thomas
documentation buglet
Folks: This patch should be self-explanatory. --Paul Vojta cut here --- texmf/web2c/updmap.cfg Mon May 20 12:18:16 2002 +++ /tmp/updmap.cfg Sat Jun 15 14:44:32 2002 @@ -5,9 +5,9 @@ # # Should dvips (by default) prefer bitmap fonts or outline fonts # if both are available? Independend of this setting, outlines -# can be forced by putting "p outline.map" into a config file +# can be forced by putting "p psfonts_t1.map" into a config file # that dvips reads. Bitmaps (for the fonts in question) can -# be forced by putting "p pk.map" into a config file. +# be forced by putting "p psfonts_pk.map" into a config file. # We provide such config files which can be enabled via # dvips -Poutline ... resp. dvips -Ppk ... #
