Saving UTF-8 encoded files?

[Stian]

Hi,

Is is possible to save files at UTF-8 by default in PLSQL Developer? In my current project this is important. Now I have to convert all files I edit in PLSQL Developer to UTF-8 manually.

PLSQL Developer can read UTF-8 with BOM, when edited and saved they are converted to ANSI.

PLSQL Developer doesn't understand UTF-8 files without BOM and multibyte characters show as two characters. UTF-8 wo/BOM is getting more common as it is used as default UTF-8 encoding in Unix/Linux.

The possibility to reade UTF-8 without BOM and save as UTF-8 by default would be a nice feature to have.

Regards
Stian H. Larssen

 

[Marco Kalter]

I have added this to the list of enhancement requests. At the moment PL/SQL Developer will only add a BOM if the file contains Unicode characters beyond the ansi character set.

 

[Stian]

Seems this did not make it in 8.0.

It would be very nice for PLSQL Developer to detect UTF-8 without BOM and a setting in properties to save files in whatever character set you want.

My work would be simpler if all files I saved are in UTF8 without BOM.

Stian

 

[Patricio T]

I have added this to the list of enhancement requests. At the moment PL/SQL Developer will only add a BOM if the file contains Unicode characters beyond the ansi character set.

We are currently evaluating PL/SQL Developer since we need an official tool for this language, but we hit a mayor problem in this area. Currently our automated deploy works in Linux/Java and expects all of our code to be UTF-8 without BOM since there is a problem with this language reading files with BOM (http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4508058). Is there any chance that in the near future there could be a feature where one could stablish the encoding of the source files generated by PL/SQL Developer? can it be done now? how?

Regards

 

[Marco Kalter]

At the moment there is no option to omit the BOM if there are Unicode characters. You would have to preprocess the files before passing them to your deployment tools. The preprocessor can be a very simple program.

 

[Stian]

Hi,

We tried to implement an auto-conversion in subversion but this was post-processing. But very quickly ran into problems with other files we could not convert.

In a large project with mixed platforms, environments and lots of developers it's a nightmare to enforce this after the files are created.

It should be a simple option to force all files to be stored in UTF-8 without BOM.

 

[Marco Kalter]

This is on the list of enhancement requests.

 

[Patricio T]

How long can it take before a feature request hit's the official version?

 

[Marco Kalter]

It will be in the next version (9.0).

 

[Patricio T]

Thanks for the info... i guess that 9.0 could be out next year? any chance of a specific date?

 

[Marco Kalter]

No, we don't have a date yet.

 

[krokyk]

Hi, I'm using v10.0 right now and by default the BOM bytes are saved. Was the option to omit the BOM added at all? If yes, please can you point me in the right direction?

Thanks

 

[Gustavo]

There is an option in Preferences, under Files -> Format. Check the "Encoding" area.

Regards,
Gustavo

 

[protos]

Hi.
Why tool "export user objects" does not use encoding options and always export in ANSI (in my case). Is it a bug?

pl/sql developer v12

 

[Marco Kalter]

Are you exporting from an UTF8 database?

 

[protos]

No, our database is CL8MSWIN1251.
We use export in UTF for source control.

 

[Marco Kalter]

In that case the export will indeed not be in UTF8 format. I have added an option for this to the list of enhancement requests.

 

[protos]

Ok! Nice to hear.