To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=48165
User as changed the following:
What |Old value |New value
================================================================================
Status|NEW |RESOLVED
--------------------------------------------------------------------------------
Resolution| |FIXED
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Tue Apr 26 22:59:35 -0700
2005 -------
The problem: I make my own UTF-8 check and encoding on merging the filter
fragments together. The reason for that: to many developers checked in wrong
encoded files into the cvs and nobody detected such "damaged filter UINames"
later in the product. But the encoding algorithm of UTF-8 was not right ...
The fix for that needs some time ... so I've decided to use the java UTF-8
encoding
again. But: then we loose the UTF-8 check. Because java does not detect errors
inside a wrong encoded file.
=> QA must check more then before if filter UINames are encoded right. Because
it's temporary not done by the filter build process ... till I'm back with a
new UTF8
implementation .-)
---------------------------------------------------------------------
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]
