[
https://issues.jboss.org/browse/JBIDE-9937?page=com.atlassian.jira.plugin...
]
Victor Rubezhny commented on JBIDE-9937:
----------------------------------------
In my case editor uses CharsetEncoder to convert editor's content into ISO-8859-1
encoding and this encoder is set up to report a problem when it faces an Unmappable
Character.
If we would like to change this strategy we have the only "replace" choice to
use but any replacement will kill original content (probably we can replace UTF-8
character by UrlEncoded equivalent but more sophisticated processing is to be performed
for xml content (I though that xml node/attribute names cannod be encoded, and so on).
Other possibility is to prevent the saving for such documents by detecting the problems
prior to saving and doing (in case of decode problems) the save way as Save operation does
(with showing the dialog with the proposal to save in UTF-8 encoding).
SaveAs could not be completed due to issue with character encoding
------------------------------------------------------------------
Key: JBIDE-9937
URL:
https://issues.jboss.org/browse/JBIDE-9937
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: UpStream
Affects Versions: 3.3.0.M4
Reporter: Vitali Yemialyanchyk
Assignee: Victor Rubezhny
Fix For: 3.3.x
Attachments: example.zip, java-save.png, jspx.png, screenshot-1.jpg
1) open some jspx page in 1252 encoding
2) write something in Russian
3) try to save as new jspx page
4) see error dialog !screenshot-1.jpg|thumbnail!
should propose to save in UTF
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira