To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=15456





------- Additional comments from [EMAIL PROTECTED] Tue Dec  4 09:38:28 +0000 
2007 -------
Kohei: I should have been clearer. You are right that most text editors do allow
you to set the encoding. What I meant was the following: If I have a file that
is saved in iso-8859-2 and load that into an editor whose encoding is set to
iso-8859-1, then I will see some strange characters if we do not use character
entities, and I will see the character entities in the other case. In the first
case, I need to switch the encoding. In the 2nd case, I can just go ahead. I'm
not using text editors for editing HTML documents too often, and if so, I'm
working mostly with UTF-8. So I don't really know whether todays text editors
auto detect other encodings of HTML documents than UTF-8, but given that the
encoding information is is either in a meta element, or maybe supplied by the
HTTP server only, I don't expect them to do so. In any case, using character
entities instead of the characters itself makes document more independent of the
encoding that is used.

However, I have checked the HTML specification, and did not find any advice to
use character encoding in favor of just using the character codes. All it says
is that character entities can be used for characters that are not existing in a
certain encoding. So, changing OOo seems not to violate any recommendation, and
I'm fine with changing that if you and ama believe that this is reasonable.

However, I'm wondering whether we should change that behavior in general, as I
have outlines above. Anyway, I know that this is beyond the scope of the patch,
so I'm fine with changing the behavior for ISO-8859-2 only, too. If we do so, we
may want to add a note to the source code that says that the new behavior
applies to ISO-8859-2 only because we received only a patch for that encoding,
and not because the new behavior is for whatever reason only reasonable for
ISO-8859-2. This may save people that look at the code later from wondering why
there is this behavior for ISO-8859-2 only.



---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to