Version: 4.3 (using KDE 3.3.0, compiled sources) Compiler: gcc version 3.3.4 OS: Linux (i686) release 2.6.9 When I open KWrite the I load a new file and I select UTF8 coding, KWrite open File not in UTF8 coding, I suspect it's a bad way of getting the selected encoding from the combobox
How do you select utf8 coding? where is the file from? can you give a precise example please?
> How do you select utf8 coding? where is the file from? can you give a > precise example please? Open KWrite, then from menu File/Open appears a file dialog on the right upper corner there is a combobox with all encodings available. Select UTF8 and select a file that you know it's UTF-8 encoding. For example a translation file: kde-i18n/it/messages/kdeextragear-1/k3b.po from KDE CVS HEAD and see. I think I write correctly the bug description, why did you ask me a precise one?
So you can NEVER set your KWrite on utf-8 encoding? Can you take a screenshot showing your encoding and a bit of the messed file? Is the behaviour the same with Kate? I am interested in your bug as I use a lot of utf-8 (khangman and klettres data plus translations) and I want Kate to be fixed. However I can open KWrite with utf-8, it's only in certain special cases that I have a problem.
Well, sometimes I can load as UTF-8 others time no. It's random. In the shot I attached. You can see "sincerit" and strange character. it has to be "sincerità". It's the Italian KHangman "hard.txt" It is difficult to reproduce this but cause of its random way of doing. Created an attachment (id=8077) kwriteshot.png
I would like to see the View -> Set Encoding menu item on your screenshot. What does it say? Obviously your file is not opened as utf-8 but it will be difficult to make sense of the bug if it's random. It must be related to something. I can open all KHangMan files as utf-8 with KWrite, I just tried with hard.kvtml in kde-i18n/data/kdeedu/khangman. If you could try that one and set KWrite View -> Set Encoding to utf-8 just to see if it resolves it? Maybe your bug is only in 3.3.0.
seems to be this problem 85215 *** This bug has been marked as a duplicate of 85215 ***