ANNOUNCEMENT: community.oracle.com is currently Read only due to planned upgrade until 28-Sep-2020 9:30 AM Pacific Time. Any changes made during Read only mode will be lost and will need to be re-entered when the application is back read/write.
I have experienced how SQL-dev 4.1 behaves when switching between different encodings.
the codings I switced between was utf-8 and cp1252 (tools->preferences->environment->encoding)
The editor is not capable of detecting the (BOM - bit mark order) in the file.
when using utf-8 encoding and then opening a file save in cp-1252-encoding, which contains special signs ie. danish special letters æåøÆÅØ, the editor shows weird- letters and unprintable signs and vice versa.
It is a problem when compiling and saving packages which will be saved containing the weird signs.
I have tried some other editors (even notapad) which are capable of detecting how the file is encoded.