remove get/setForcCloseTags() methods from OutputOptions?

Hi everyone,

Just wondering if I can safely remove the get/setForcCloseTags() methods 
from the OutputOptions class?  That is, if I remove the methods, will this 
break anyone's code?  I believe these methods were added during the XMLC 
2.2 alpha cycle, so I would think it would be somewhat unlikely that anyone 
would be using them yet.  Note that these methods have been replaced with 
the more appropriate methods get/setEnableXHTMLCompatibility().

The difference in the two methods are semantic.  The former method seems to 
say "force all tags to use an explict close tag".  This really makes no 
sense when it comes to XHTML.  The original reason for the method was to 
solve the <script/> -vs- <script></script> issue where the latter is 
compatible with browsers like IE5.5 and IE6.0 but the former isn't, but all 
tags are given an explicit end tag, this will actually break XHTML 
(eg...  <br></br>, <hr></hr> are both totally invalid XHTML).  The new 
method allows for XMLC developers to, internally, do whatever is required 
to maintain browser compatibility when writing XHTML.  Currently the only 
thing taken into account is the <script> issue, but keeping the 
OutputOptions XHTML compatibility methods generic allows for applying 
future XHTML workarounds without adding any new methods to the 
OutputOptions class.


So, if anyone has a problem with this, please speak up.  If not, I will be 
committing it later today.

Jake