Re: Tenacious Word tag won't die

> Have you tried this?
> 
> http://tidy.sourceforge.net/docs/quickref.html#word-2000
> 

Yes.  That's the first thing I always set.  I've established that the <o:p>
problem was introduced to the  Windows binaries somewhere between 2002 and
2004.  I added the following note to the bug report:
...
"Further work (ie cleaning the same file from within Homesite with different
Tidy versions) suggests this problem was introduced in the Windows build
somewhere between the versions distributed with Homesite (created 16 Jan 01)
or Topstyle 3 (4 May 02) and recent windows binary tidy.exe builds (17 Mar 04,
5 Jul 04 and 6 Oct 04).
The <o:p> tag is removed by old builds and not by the newer ones.  
Also it may be Windows-specific, as the online version of Tidy at
http://infohound.net/tidy/ (on Linux) does not have the problem.  I've also
had success with TidyUI (ca. 2001) but not with HTMLTrim, with (as close as
possible) the same settings."
...

I checked the online Linux version information and it looks to be of 2002
origin, so it may be more general than just Windows.

The <o:p> problem occurs with Word 2000 and Word 2003.  Word 2003 poses
numerous other problems for Tidy, and there are many files Tidy doesn't get
anywhere near fixing, regardless of the Tidy binary build version.

The only Word HTML cleaning soultion I've found that appears to work every
time (so far) is to copy from Word and paste into the design window of
Dreamweaver MX2004.  But it would be very handy to have Tidy fix things
fromwithin Homesite.

DN

> On Wed, 17 Nov 2004 11:09:57 +1000, David Nicholls <[email protected]> wrote:
> > I've been trying to use Tidy to clean up Word 2000/2003 "HTML".
> > 
> > I am unable to find a way to remove the gratuitous <o:p> , </o:p> tags.
> > 
> > I've tried using Tidy (several builds) from within Homesite 5.5, from within
> > Topstyle 3,  and using HTMLTrim and TidyUI.
> > 
> > There does not appear to be a way to tell Tidy to kill non-W3C tags.  It
> > reports tham as illegal and then leaves them in place.  A "kill non-W3C tags"
> > option would be most welcome.
> > 
> > There are two problems: simple empty <o:p></o:p> occurrences and bracketed
> > nbsps and blank spaces: <o:p>&nbsp;</o:p> or <o:p> </o:p>
> > 
> > I have not tried the command line, because, working in a Windows environement,
> > command line  operations are slow and error prone, and it appears likely, in
> > the organisation where I'm working, that command line access will be closed
> > off by a (paranoid) security policy soon.
> > 
> > Does anyone have any guidance on how to kill these pestiferous tags?
> > 
> > A test Word 2000 "HTML" file that shows the problem is located at
> >
https://sourceforge.net/tracker/download.php?group_id=27659&atid=390963&file_id=108929&aid=1067112
> > 
> > See also bug 1067112.
> > 
> > DN

____________________________
David C Nicholls
Nicholls Communications
http://www.dcnicholls.com/
-- 




-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8