We should detect BOM in Import Tool and use UTF-8 if that is the case regardless of what encoding the user chooses.
In Export Tool, [default] encoding should be UTF-8.
Field | Old Value | New Value |
---|---|---|
Dev Assignee | SachinPrakash (Sachin Prakash) | funfun (Fun Fun) |
QA Assignee | tariqrahiman (Tariq Rahiman) | SachinPrakash (Sachin Prakash) |
Version | 15.0 | 15.1 |
Field | Old Value | New Value |
---|---|---|
Dev Assignee | funfun (Fun Fun) | NielsGron (Niels Gron) |
Version | 15.1 | 15.0 |
Field | Old Value | New Value |
---|---|---|
Version | 15.0 | 16.0 |
Field | Old Value | New Value |
---|---|---|
Version | 16.0 | Future - .9 |
Field | Old Value | New Value |
---|---|---|
Version | Future - .9 | Future - PM |
Issue #10990 |
New |
Completion |
No due date |
No fixed build |
No time estimate |
2 issue links |
relates to #10981
Issue #10981source command assumes file is always in UTF8 encoding |
blocks #10983
Issue #10983sqlexport to file with umlaut in its name - filename not displayed correctly by operating system |
We should detect BOM in Import Tool and use UTF-8 if that is the case regardless of what encoding the user chooses.
In Export Tool, [default] encoding should be UTF-8.