Yes, I really should pick up XML because I'm in the publishing industry. I can see 3 milestones for my project:

(1) Perl with text files.

(2) Perl with HTML files for the greater functionality of being able to handle Word document elements such as superscripts, fonts, etc. (Or bite the bullet and do it with VB if this approach fails to work).

(3) Perl with XML. At this point, I should have a marketable product and the big bucks should start flowing in. :-)

What are STM books? STM stands for "scientific, technical, and medical." But it's the IT books that drive us up the wall with the jargon, acronyms, and terms uppercased or not depending on the author's whims. My Perl project is primarily directed toward taming IT books. Most sciences have fairly stable conventions regarding nomenclature, but not IT methinks.

Would you say "I bought two mouses from the store" or "I bought two mice from the store"? And which would choose: keystream, key stream, or key-stream? We had one book where it appeared all three ways.

By the way, are there no well-known freeware Word-to-XML converters?

Thanks, everybody, for all the help.

In reply to Re^2: A copyeditor needs help to get started with a Perl project by wordsmith
in thread A copyeditor needs help to get started with a Perl project by wordsmith

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.