Marco,

I have a package body source, that has non-standard literal character in it (ASCII function returns 50072). The body compiles without any problems and when I check the compiled source, this character is still there.
There is a problem however, when I try to compare my local source to current database source, because in both Editor.pcf and Database.pcf files that character is transformed to 'O' (ASCII = 79).
Needless to say, that may lead to some problems when for example someone wants to make local source up to date by copying the whole DB source from the comparision tool, which exactly happened in my case.

Best Regards.
Scovron.

P.S. I can't put the problematic character in the post, because PHP Forum Software doesn't cooperate with it, so run "SELECT CHR(50072) FROM dual;" to see, what I mean

I'm sorry, but seems like PHP Forum Software has some problem with the special character, that the post was about, because the post ends in that place although in preview it looks fine.
I'll edit the original post in a moment.

Can you let me know how exactly you compare the sources? Do you use the "Compare Database Objects" tool, or do you use the right-click compare function?

Right click -> Compare to -> Current database source...

The 3rd party difference viewer that we use does unfortunately not support Unicode. This has been enhanced for the upcoming 14.0 release, which has a built-in difference viewer with full Unicode support.

The only alternative in PL/SQL Developer 13.0 and earlier is to configure an external difference viewer that supports Unicode (Configure > Preferences > Tools / Differences).

Marco,

Seems like the problem doesn't lie in difference viewer (I'm using WinMerge by the way), because Editor.pcf and Database.pcf files are generated with that character already translated. I've check them in a hex editor to be 100% sure.

Can you send the source file to support@allroundautomations.com?

Email with example source code containing problematic character has been sent.

Thanks. I see that this is a UTF8 encoded file. Can you also send a screenshot of how the compare function fails? Furthermore, can you go to Help > Support Info and send me the text from the "Info" tab page?