Word as HTML editor

I have set up a document management app and plan to use Word as an HTML editor
for my users.  I also include field names in an html document to allow a merging
of data.  My problem is that, if they have automatic spell or grammar checking
on, or automatically suggest new spelling on, Word places characters around each
misspelled word.  My merge process is confused by these characters.  Mostly,
this confusion is caused by the characters separating a line, or separating a
field name across lines, making it impossible to recognize the field name in
order to replace it.

I have tried locating and removing the spell check characters before running the
merge, but this has not worked effectively.

To restate the problem, a user may open a .htm, make some changes, and save it. 
Of course, the field names generate a spell or grammar check, which end up also
saved with the .htm.  Then when they print the .htm, the merge process cannot
locate the merge fields because of these control characters automatically
entered by Word spell/grammar check.

Does anyone have any ideas on what I might do to overcome this problem.  

I thought I might programmatically turn off auto spell and grammar check just
before I programmatically open the .htm in Word.  But I would have to silently
reopen word after they close and save the file, and reset the auto spell/grammar
off so they have it on for their next Word file.  Was hoping there might be a
simpler way.

Many, many thanks for any and all ideas on this,
Mark
  

BTW, I am using ParseHTML.cc from Michael Nuwer and Ed Hoskins ( many thanks)
that works great for filling in the field values.  It just has a problem with
these auto spell/grammar characters.  Maybe Michael or Ed ran into this problem
and have some suggestions I hope.

Thanks again,
Mark

Mark Wrote:

> I have set up a document management app and plan to use Word as an HTML
editor for my users.  I also include field names in an html document to allow a
merging of data.  My problem is that, if they have automatic spell or grammar
checking on, or automatically suggest new spelling on, Word places characters
around each misspelled word.  My merge process is confused by these characters. 
Mostly, this confusion is caused by the characters separating a line, or
separating a field name across lines, making it impossible to recognize the
field name in order to replace it.
> 
> I have tried locating and removing the spell check characters before
running the merge, but this has not worked effectively.
> 
> To restate the problem, a user may open a .htm, make some changes, and save
it.  Of course, the field names generate a spell or grammar check, which end up
also saved with the .htm.  Then when they print the .htm, the merge process
cannot locate the merge fields because of these control characters automatically
entered by Word spell/grammar check.
> 
> Does anyone have any ideas on what I might do to overcome this problem.  
> 
> I thought I might programmatically turn off auto spell and grammar check
just before I programmatically open the .htm in Word.  But I would have to
silently reopen word after they close and save the file, and reset the auto
spell/grammar off so they have it on for their next Word file.  Was hoping there
might be a simpler way.
> 
> Many, many thanks for any and all ideas on this,
> Mark
>   
> 

Mark wrote:
> BTW, I am using ParseHTML.cc from Michael Nuwer and Ed Hoskins ( many
thanks) that works great for filling in the field values.  It just has a problem
with these auto spell/grammar characters.  Maybe Michael or Ed ran into this
problem and have some suggestions I hope.

Mark,

In my copy of Word (2007-USA) the spell checker ignores words that are all caps.

Michael,

Ah yes.  That should work.  I also should be able to use OLE to set that option
on whenever they open Word and load a file to be sure my client has it set.  

Will give this a try, but this should do it.  

Much appreciation.  This was giving me fits since I really wanted to stay with
an editor my clients already use.

Mark

Michael Nuwer Wrote:

> Mark wrote:
> > BTW, I am using ParseHTML.cc from Michael Nuwer and Ed Hoskins ( many
thanks) that works great for filling in the field values.  It just has a problem
with these auto spell/grammar characters.  Maybe Michael or Ed ran into this
problem and have some suggestions I hope.
> 
> Mark,
> 
> In my copy of Word (2007-USA) the spell checker ignores words that are all
caps. 
> Would something like "%#MYFIELD%" work for you?

Bruce,

I thought of that, but then spell check would be off for while they edit. 
Michael's suggestion should do the trick tho.

Thanks,
Mark

Bruce Beacham Wrote:

> Mark wrote:
> 
> > I have tried locating and removing the spell check characters before
> > running the merge, but this has not worked effectively.
> > 
> > To restate the problem, a user may open a .htm, make some changes,
> > and save it.  Of course, the field names generate a spell or grammar
> > check, which end up also saved with the .htm.  Then when they print
> > the .htm, the merge process cannot locate the merge fields because of
> > these control characters automatically entered by Word spell/grammar
> > check.
> > 
> > Does anyone have any ideas on what I might do to overcome this
> > problem.
> 
> How about an autoload macro to switch off spell checking?
> 
> 
> Bruce Beacham