Mail Archives: djgpp/1997/12/17/12:31:27
On Wed, 10 Dec 1997, Eli Zaretskii wrote:
> I don't know anything about dviwin, but if it is just another DVI driver,
> you will need to set the necessary environment variables so that dviwin
> will find the fonts under the %DJDIR%/share/texmf directory.
Just my two bits...
dviwin needs the full path name *and* resolution of the .pk files. The
resolution can be expanded with $r (see dviwin docs)
> The problem with that setup is that if dviwin was not built with the
> Kpathsea library (which is used in the DJGPP port), you will have grave
> difficulties making it happen, because non-Kpathsea DVI drivers have
> their own built-in assumptions about the structure of the fonts tree, and
> they might have problems to run the MakeTeX... programs due to
> incompatibilities in the command line processing (lines longer than 126
> characters, quoting, globbing, etc.).
That is, alas, true. dviwin doesnot use the kpathsea functions. Hence
automating pk file production under dviwin would be a major task. The
ugly workaround is to run dvivga once let it generate the mising pk files
and then use dviwin to do the *real* viewing. Ugh!!
> If you have access to the sources and the tools that will let
> you rebuild dviwin,
sorry. As far as I know, dviwin comes binaries only.
- Raw text -