Unicode in export of user objects

[Scott A.]

It appears that when I use the "Export User Objects" the files that are created in unicode (utf-8). This does not happen when I save using "save" or "save as". I need to include owner in the file that is generated. Export does this but "Save" does not.

The problem this causes is I have ftp the files to a unix box so our dba's can run the scripts. They are getting errors because of the BOM (Byte Order Mark) in text files that are unicode.

My work around is I have to open the export files in a my text editor and save as ascii. This is a pain and prone to human error (I often forget).

Can export be instructed not to save as unicode or can Save/Save as be instructed to include the owner.

 

[Marco Kalter]

This does not happen when I save using "save" or "save as".

Which "save" or "save as" do you mean?

They are getting errors because of the BOM (Byte Order Mark) in text files that are unicode.

The file is saved as Unicode (with the BOM added) if the file contains Unicode characters that cannot be represented in the character set of your Windows environment.

 

[Scott A.]

When you have a procedure/package open in the editor and you do a file/save or file/save as.

This is pl/sql code (it is going to be ascii) -- if save does not put it in unicode why does exporting have to. I understand if this was text stored in the database but not pl/sql code.