Issue 48268

Summary: Saving an UTF-8 encoded could result in losing encoding
Product: Writer Reporter: frank.loehmann
Component: codeAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: issues
Version: 680m97   
Target Milestone: ---   
Hardware: All   
OS: All   
Issue Type: FEATURE Latest Confirmation in: ---
Developer Difficulty: ---

Description frank.loehmann 2005-04-27 12:58:32 UTC
- create an UTF-8 encoded text document with OOo
- close the file
- drag & drop this file onto OOo from the file system
- Writer correctly decodes the txt file due to the byte order mark at the
beginning of the txt file. But if saved again (i.e. via CTRL+S) after changes
have been made, the UTF-8 encoding is lost. Writer has to set the encoding
correctly or has to show the encoding dialog on saving the file.
Comment 1 frank.loehmann 2005-04-27 13:00:43 UTC
change title
Comment 2 ulf.stroehler 2005-05-27 16:13:25 UTC
Additionally info: fl did a d'n'd from the win explorer to OO.o. Afterwards the
txt file obviously was saved in the desktop encoding which is probably win-1252
or something.

Not sure whether this is really a 'Defect' or an Enhancement.

US->AMA: pls. dispatch. Thx.
Comment 3 andreas.martens 2005-06-07 16:22:47 UTC
It's a good idea and a nice feature request but it's not the goal of a product
update OOo2.0.1 to make Writer a perfect editor for plain text files.
At the moment the encoding information got lost after opening a file. If you
save it without defining the wished encoding we use the default encoding.
We should think about it and see if we want to change this for a later OOo version.
Comment 4 bettina.haberer 2010-05-21 14:42:10 UTC
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".