| Open SQL-File ignores BOM [message #631185] |
Wed, 06 October 2010 10:03  |
Eclipse User |
|
|
|
Hello,
I have several SQL-Files that are encoded with UTF-16 (LE). The BOM is set correctly.
If I doubleclick one of this files in the Navigator, the SQL-Editor opens and displayes the file corrupted. If I rightclick on the file and select "properties", the encoding is set to "Default (inherited from container: Cp1252)". If I change the encoding manually to UTF-16 the file is displayed fine in SQL-Editor.
If I rename the same files (with the UTF-16-(LE)-BOM) to "x.txt", Eclipse interprets them as textfiles and reads the BOM correctly. The Properties-Dialog displays now "Byte Order Mark is UTF-16 Little-Endian (BOM)".
The files are distributed over several folders of my projects, so setting the file type to UTF-16 manually is no solution.
Is this a Bug in the DTP or the SQL-Editor and I should report a bug or is there any other solution?
|
|
|
| Re: Open SQL-File ignores BOM [message #631218 is a reply to message #631185] |
Wed, 06 October 2010 11:12  |
| Eclipse User |
|
|
|
Hi there...
Please go ahead and report this as a bug against SQL tools for now with
repro steps and a sample SQL file with the troublesome encoding. We'll
see what we can do.
--Fitz
Tomka Kuje wrote:
> Hello,
>
> I have several SQL-Files that are encoded with UTF-16 (LE). The BOM is
> set correctly.
> If I doubleclick one of this files in the Navigator, the SQL-Editor
> opens and displayes the file corrupted. If I rightclick on the file and
> select "properties", the encoding is set to "Default (inherited from
> container: Cp1252)". If I change the encoding manually to UTF-16 the
> file is displayed fine in SQL-Editor.
>
> If I rename the same files (with the UTF-16-(LE)-BOM) to "x.txt",
> Eclipse interprets them as textfiles and reads the BOM correctly. The
> Properties-Dialog displays now "Byte Order Mark is UTF-16 Little-Endian
> (BOM)".
>
> The files are distributed over several folders of my projects, so
> setting the file type to UTF-16 manually is no solution.
>
> Is this a Bug in the DTP or the SQL-Editor and I should report a bug or
> is there any other solution?
|
|
|
Powered by
FUDForum. Page generated in 0.03246 seconds
Home