HTML2PDF for VMS?

[Joseph Huber_1 · Accepted solution]

I almost never used it, but htmldoc.com setup reads:
$! HTMLDOC.COM
$!
$! Customize this procedure as required for your installation.
$!
$! Note: use unix-style directory format for the HTMLDOC_DATA directory!
$!
$ define HTMLDOC_DATA "disk$www/htmldoc/
$!
$ HTMLDOC :== $DISK$WWW:[HTMLDOC]HTMLDOC.EXE
$!
$ exit

i.e defining htmldoc_data in VMS syntax is wrong.
Define it in Unix syntax:
define htmldoc_data "/device/htmldoc/"
to make it working.
A quick test on my system showed it is working.

[Joseph Huber_1]

In my above define command, there may be a variation of the Unix-style path definition,
depending on "device" being a logical name, and the definition of the Unix-compatibility level and the definition of
DECC$DISABLE_TO_VMS_LOGNAME_TRANSLATION

So either "/device/directory/"
or "device/directory".

[Clark Hayden]

Hi Joseph.

I have tried defining the logical as:
"HTMLDOC_DATA" = "/ALEX04$DKE0/HTMLDOC"
"HTMLDOC_DATA" = "/ALEX04$DKE0/HTMLDOC/"
"HTMLDOC_DATA" = "ALEX04$DKE0/HTMLDOC"
"HTMLDOC_DATA" = "ALEX04$DKE0/HTMLDOC/"

None of which has returned anything other than ERR005: Unable to open font width file.........

I have no previous Unix experience so this is all a learning experience for me. :)

Thanks.
Hayden.

[Oswald Knoppers_1]

Maybe the html2pdf tool doesn't like the $ sign in the (ALEX04$DKE0) logical name.

Oswald

[Volker Halle]

Hayden,

and there is a DKE0:[HTMLDOC.FONT] directory with all the required font files ?

Volker.

[Joseph Huber_1]

On my system (VMS 7.3-1 Alpha) it looks like this:

MPIW10_HUB>sh log htmldoc_data
"HTMLDOC_DATA" = "disk$www/htmldoc/" (LNM$PROCESS_TABLE)
MPIW10_HUB>sh log disk$www
"DISK$WWW" = "AVMP01$DKA100:" (LNM$SYSTEM_TABLE)
MPIW10_HUB>sh log DECC$DISABLE_TO_VMS_LOGNAME_TRANSLATION
"DECC$DISABLE_TO_VMS_LOGNAME_TRANSLATION" = "DISABLE" (LNM$PROCESS_TABLE)
MPIW10_HUB>dir disk$www:[htmldoc]

Directory DISK$WWW:[HTMLDOC]

COPYING.TXT;1 DATA.DIR;1 FONTS.DIR;1 HTMLDOC.COM;2
HTMLDOC.EXE;1 HTMLDOC_VMS.TXT;1 README.TXT;1

Total of 7 files.
MPIW10_HUB>htmldoc -f tmp.pdf ALL.HTML
PAGES: 4
BYTES: 19848

[Clark Hayden]

Ok. I figured out this problem. I used the unix style format you described and it worked. All I had to do was track down the junior system administrator who figured he needed some space and so deleted some of the files that I created yesterday. The files were copied back and HTMLDOC runs.

It now produces a PDF but Adobe can't read it. Is there a limit to which version of Adobe can be used to access the file? I have Adobe Reader 9.

Thanks.
Hayden.

[Joseph Huber_1]

Well I did not extensive tests, but my all.html in last reply is a HTML file containing some

tags, and an

list of links in between.
It produces a table of contentents for the

tags, and correctly lists everything.
XPDF on VMS and the Adobe reader on Linux have no problems with the file produced.
So maybe some HTML elements (graphics ?) produce the errors ?
Can You look at the acroread error ? Maybe run Adobe reader on the command-line to see errors ?

[Clark Hayden]

I was about to post a follwo up. I see that the conversion to PDF produced the following:
ERR014: Text on page 7 too large - truncation or overlapping may occur!

Would this have anything to do with the problem being experienced by Adobe Reader?

Thanks.

[Joseph Huber_1]

Hayden,
since You produce the PDF on VMS, but use Adobe reader on another system (Linux, windows ?, acroread standalone, in a web-browser ?),
how do You transfer the VMS file ?
From a VMS web-server ?
Transferred to the other system by which method ?