One simple-minded, OTTOMH approach (unless MS Word's formatting is somehow important):
- in Word 2010, edit in an end_of_record marker of any flavor you like, so long as it won't appear in the test.
- save the whole (edited) .doc as .txt
- read the .txt
- split on EOR to create an array (named for page number) per page of words.
- split each array's contents on spaces to a second-level array (named for the page number from which the first array was extracted) of individual words
- index to your heart's content...
Of course, this may not be the most efficient approach, but it certainly avoids "climbing that (Word object model) curve.
If you didn't program your executable by toggling in binary, it wasn't really programming!
-
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.
|