Issue 22011

Summary:

export to HTML reports displayable characters as undisplayable

Product:

Writer

Reporter:

bulbul <bulbul>

Component:

Assignee:

eric.savary

Status:

CLOSED DUPLICATE

QA Contact:

issues@sw <issues>

Severity:

Trivial

Priority:

CC:

issues, tamblyne

Version:

OOo 1.1

Keywords:

oooqa

Target Milestone:

---

Hardware:

OS:

Linux, all

Issue Type:

DEFECT

Latest Confirmation in:

---

Developer Difficulty:

---

Attachments:

Description	Flags
writer file for export to html	none

Description bulbul 2003-11-02 00:35:21 UTC

When exporting a document with characters outside the ISO-8859-1 character set
to HTML in ISO-8859-1, an error message will pop up claiming that the characters
can't be displayed. However, the filter actually translates them (or at least
the Latin extended characters i've tried) correctly to HTML using codes like
"&#265;". The characters are displayed correctly in my browser in the exported
HTML document. The text of the error dialog is this:

   Warning saving the document html-export-chars.html
   Write error.
   The following chars could not be displayed in the selected char set:
   [the characters]

I'm attaching an OOo document with three non-8859-1 characters. With your
Options -> Save/Load -> HTML -> Character Set set to  ISO-8859-1, save the
document to HTML. The dialog will appear even though the output file displays
the characters correctly.

If this is the desired behavior, perhaps the wording of the error dialog could
be revised. It currently gives the impression that the characters will not be
displayed. In any case, the text should be corrected by putting a colon after
the word "warning".

Comment 1 tamblyne 2003-11-02 01:24:56 UTC

Hi, Leston --  

Did you forget the attachment?  

Thanks,  

Tam

Comment 2 bulbul 2003-11-02 04:21:23 UTC

Created attachment 10881 [details]
writer file for export to html

Comment 3 bulbul 2003-11-02 04:22:00 UTC

Yes, i forgot to attach. Thanks for reminding me!

Comment 4 tamblyne 2003-11-02 13:01:23 UTC

Confirmed RH9/1.1.0 and 680m11  

Changed Priority to P4 -- aside from the typo, perhaps the warning
message could more accurately reflect the behavior.

Comment 5 h.ilter 2003-11-03 12:45:53 UTC

Reassigned to ES

Comment 6 eric.savary 2003-11-03 13:09:44 UTC

This message box and the whole encoding behaviour will have to be
redesingned according to issue 19690

*** This issue has been marked as a duplicate of 19690 ***

Comment 7 eric.savary 2003-11-03 13:10:01 UTC

closed