[Bug 89866] New: Can not save document because selected encoding does not contain some unicode character - and WHAT?

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
        
http://bugs.kde.org/show_bug.cgi?id=89866        
           Summary: Can not save document because selected encoding does not
                    contain some unicode character - and WHAT?
           Product: kate
           Version: unspecified
          Platform: Debian testing
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kwrite-devel kde org
        ReportedBy: Marcin.Kasperski softax com pl


Version:            (using KDE KDE 3.2.3)
Installed from:    Debian testing/unstable Packages

Background: I use Polish language enviroment, in particular my natural text 
file encoding is iso-8859-2.

Fairly frequent problem:

- I edit some text file in kate (in iso-8859-2 encoding)

- I copy&paste some text from OpenOffice document

- When I try to save in kate, I get the following error:
'Dokument nie mógł być zapisany ponieważ wybrane kodowanie nie może zachować 
każdego unikodowego znaku. Jeśli nie jesteś pewien jakiego kodowania użyć 
spróbuj UTF-8 lub UTF-16.'
(translating to english it meas: Document could not be saved because selected 
encoding could not keep all unicode characters. You can try using UTF-8 or 
UTF-16)

But what if I DO NOT want to convert this to unicode, but I really want it to 
be saved as iso-8859-2?

There are two or even three separate things which would be really useful in 
this situation:

a) An option to force the file save in my preferred encoding even if this means 
leaving some characters out or replacing them with - say - question mark.

b) Some way to find WHICH character (or charactes) caused the problem. I can 
imagine highlighting them or compile-style listing (whatever presentation 
method is chosen, probably there could be some button in the error window 
mentioned above which would activate this show)

c) After reviewing my document I strongly suspect that the whole problem is 
caused by some unicode-encoded space or punctuation (I really can not find any 
character which is not Ascii or Polish). Such characters really could be 
translated automatically in such context.