comment on

Actually it was the complexity of the RTF format itself, and particularly how it relates to Word documents that steered me away from that solution. Lots of unknowns.

And when I saved a Word document as RTF I expected some kind of style sheet definition and logical markup, but that didn't seem to be the case. To me it seemed that Word would write the visual markup all over the place. I don't know, maybe that's how RTF is supposed to work, maybe Word does it in a brain-dead manner.

Like I said, I didn't have any clue how RTF worked, and I didn't have the time or resources to read up on it. RTF was my first shot but it didn't pan out, so I moved on to solve my actual problem.

Your module looked interesting though and I nearly gave it a test run, but at that time I had already begun looking into automating Word.

In reply to Re^2: Module advice: when is it too insignificant to release? by jplindstrom
in thread Module advice: when is it too insignificant to release? by jplindstrom

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl Monk, Perl Meditation
	PerlMonks