I believe you're right, the resulting PRN files are device dependent. If you produced a PRN file for a PostScript printer, it would be normal PostScript (which if I remember right is a trick "back in the day" to get MS Windows apps to produce PostScript files), if it's a PCL printer it would be that, and so forth.

I am assuming that the OP has a machine running Windows with at least one printer attached, or Win32::OLE won't be able to produce PRN file output. Wouldn't be able to print anything to hard copy, either.

Huh, now that I think about it, I wonder what would happen if you did a print to file to a printer that produces files, such as PDF Creator or Adobe Acrobat? Ugh, don't want to ponder that

In reply to Re^4: DOC TO PRN by Sinistral
in thread DOC TO PRN by prabudass

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.