Wrong encoding after import sources. about oradew-vscode HOT 9 CLOSED

Yes, "package.encoding" changes only encoding of packaged script (deploy/run.sql).

I had a problem converting to win1250 when exporting / compiling (Node.js related - not remembering exacatly what was the problem) and then settled for UTF-8 for files, but allowing encoding setting for deploy package ("package.encoding": "win1250") which can then be executed with Oracle tools: SQLPlus, SQL Developer. This works for me, my DB charset is also WIN1250.

Compiling a Src file that is UTF-8 to different encoded DB with SqlPlus or SqlDeveloper that is a problem, I agree...

Can you please tell me what exactly is the problem in your case or what are you trying to achieve. In other words: why you cannot have files in UTF-8?

Thanks for your feedback.

from oradew-vscode.

Mainly I have problem with importing source of packages which contains a lot comments with polish characters and after conversion to uft8 they are unreadable (after compile for another users as well).

from oradew-vscode.

Can you please provide a simple example: a text with characters that cause problem, so I can reproduce?

from oradew-vscode.

Comment (NLS_LANG=POLISH_POLAND.EE8MSWIN1250):
// Zażółć gęślą jaźń

from oradew-vscode.

I saved your comment to a DB proc, imported current file and the characters came intact. I also have an NLS_CHARACTERSET=EE8MSWIN1250 🤔

Can you check if your imported .sql file is opened with "UTF-8" encoding? (righ-bottom corner of editor)

from oradew-vscode.

I've tested it, and it works. but now I have to convert all my scripts to uft-8.

from oradew-vscode.

You are right. I will release a new version today with source.encoding parameter, that lets you specifiy the encoding of source files.

from oradew-vscode.

@otherexception , I just released a 0.3.9 version with "source.encoding" setting.

Adding "source.encoding": "win1250" to oradewrc.json should export files in win1250. (default is utf8, similar to package.encoding)

I also use "files.encoding": "windows1250" in settings.json so files are definitely opened in correct encoding, just in case.

from oradew-vscode.

Better setting that affects only plsql files:

"[plsql]": {
    "files.encoding": "windows1250"
  }

from oradew-vscode.