74377 - changing doctype in existing files

Status: VERIFIED DUPLICATE of bug 92525

(SeaMonkey :: Composer, defect)

Description

[Kathleen :Brade]

In bug #34458, Charley says:

>It could even be argued that we should even change *existing* doctype to 4.01,
>since that is what we are actually doing, correct?

This bug is to track and come to a resolution (and fix if required) regarding 
whether we should modify an existing doctype in a file to be 4.01 or not.

Today, we write out a 4.01 transitional doctype for all new pages as well as 
existing pages which have been edited that didn't have any doctype.

Charley's point is that the parser we are using is using a 4.01 dtd so we should 
write out the file with the correct dtd (4.01).  Others will argue that we are 
changing the person's HTML and should at least warn them that we are changing the 
doctype.

Other opinions? ideas? suggestions? criticisms?

Comment 1

[Charles Manske]

In my last discussion with beppe, she preferred to not change an existing
doctype.

Comment 2

[Syd Logan]

spam composer change

Comment 3

[Charles Manske]

*** This bug has been marked as a duplicate of 92525 ***

Comment 4

[sujay]

v