Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA | swissarmyknife(*) |
| Priority | Low |
| Complexity | Unknown |
| Component | Tools - ER Modeler |
| Version | 14.0 |
When choosing to Generate Script from ER Model, choosing the "UTF-8 - (8-bit Unicode Transformation Format)" for encoding produces a different file format than using our Save As File as Type: "SQL Script - UTF8" from the Query Analyzer.
It seems only the Generate Script UTF8 encoding isn't truly UTF8 (see attached notepad++ encoding indicator)
Other tools in ADStudio that save to UTF8 encoding show UTF8 (see attached notepad++ encoding indicator)
|
1 KB
|
|
23 B
|
|
5 KB
|
|
5 KB
|
|
190 KB
|
|
210 KB
|
|
240 KB
|
|
208 KB
Tariq informed me that ER Model > Generate Script from Model is based on the Schema Script Generator tool. It also produces same result (not truly UTF8 when choosing to save as "UTF-8 - (8-bit Unicode Transformation Format)")
An UTF-8 without BOM file is a valid UTF-8 encoded file, BOM embedding is optional (see http://en.wikipedia.org/wiki/Byte_order_mark). ADS Query Analyzer should be able to display unicode characters in both UTF-8 with or without BOM files.
I was not able to reproduce this issue the customer is having. I generated a UTF-8 without BOM (with unicode characters) file from ER Generate Script and was able to have it display the unicode characters correctly in Query Analyzer.
An UTF-8 without BOM file is a valid UTF-8 encoded file, BOM embedding is optional (see http://en.wikipedia.org/wiki/Byte_order_mark). ADS Query Analyzer should be able to display unicode characters in both UTF-8 with or without BOM files.
I was not able to reproduce this issue the customer is having. I generated a UTF-8 without BOM (with unicode characters) file from ER Generate Script and was able to have it display the unicode characters correctly in Query Analyzer.
I think this is what I am running into
http://en.wikipedia.org/wiki/Mac_OS_Roman#Application_notes
However, default character encoding inJava for OS X is still MacRoman (see Mac Dev Center), and the keyboard layout with its combination of control, option, and dead keys still map to the original characters in MacRoman. The default character encoding for Java can be changed to UTF-8 by adding the following line to .bashrc:
export set JAVA_OPTS="$JAVA_OPTS -Dfile.encoding=UTF8"
I think this is what I am running into
http://en.wikipedia.org/wiki/Mac_OS_Roman#Application_notes
However, default character encoding inJava for OS X is still MacRoman (see Mac Dev Center), and the keyboard layout with its combination of control, option, and dead keys still map to the original characters in MacRoman. The default character encoding for Java can be changed to UTF-8 by adding the following line to .bashrc:
export set JAVA_OPTS="$JAVA_OPTS -Dfile.encoding=UTF8"
Issue #10669 |
| Closed |
| Duplicate |
| Resolved |
Completion |
| No due date |
| No fixed build |
| No time estimate |
2 issue links |
relates to #10672
Issue #10672Schema Script Generator & Generate Script from Model - save as UTF 8 - always save with BOM |
duplicates #10672
Issue #10672Schema Script Generator & Generate Script from Model - save as UTF 8 - always save with BOM |
Tariq informed me that ER Model > Generate Script from Model is based on the Schema Script Generator tool. It also produces same result (not truly UTF8 when choosing to save as "UTF-8 - (8-bit Unicode Transformation Format)")