On 5 Jun 1998, Fabrice POPINEAU wrote:

> Other solution : set $dd to '/' everywhere. Unless you are doing a
> system() command, pathes will be understood and will not need quoting.

That's the problem. One would have to replace '/' by '\' for all system()
calls. And what about paths like "C:/mydir/myfile.tex"? How does
perl handle those? I believe that the usage of native paths is the proper
way. BTW, I implemented all the quoting yesterday. And with the /o
qualifier for regexps that is no overhead at all.

> About pstoimg : there is a perl interface to ImageMagick. Although
> netpbm is fine, it would be more developper-friendly to use
> ImageMagick. I'm pretty sure the switch is easy (convert.exe has most
> options in common with netpbm tools).

Correct. But do ImageMagick ports exist for Win32? Does the perl-Interface
work on Win32, too? If yes, with what perl ports? And last but not least,
"convert" is rather huge. Calling it for e.g. cropping would be a big
overhead. The nice thing about netpbm is that there is an executable for
every little atomic task one can imagine, that means that there is almost
no overhead, because onnly the necessary actions are performed. And
convert is -- AFAIK -- not flexible enough to do the necessary steps
(multiple cropping, padding, converting) in *one* call.

Now that LaTeX2HTML seems to run fine on Win95 (thanks to your ports of
gs, web2c and netpbm! I did a lot of modifications for Win95 yesterday; be
sure to rename pstoimg_nopipes to pstoimg before configuring), I'm against
introducing "convert".
But that does not mean that it will *never* be integrated.

Cheers,

Marek

Reply via email to