better support for non-ascii characters? [CORE799] #1184
Comments
|
Commented by: Alice F. Bird (firebirds) Date: 2005-02-01 07:37 sorry, not table name, but user name. |
Modified by: @pcisarissuetype: New Feature [ 2 ] => Improvement [ 4 ] assignee: Dmitry Yemanov [ dimitr ] SF_ID: 1113727 => |
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] => Adriano dos Santos Fernandes [ asfernandes ] |
Modified by: @pcisarWorkflow: jira [ 10823 ] => Firebird [ 15226 ] |
|
Commented by: @asfernandes I suppose this old bug is alread fixed. |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: Cannot be tested Test Details: Non-ascii locale must be on FB test machine (currently this is not so). Script must use 'set names <N>' where <N> = locale, and also script must be encoded using ANSI codepage rather than OEM. Test Specifics: [Platform (Windows/Linux) specific] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: unruledboy (unruledboy)
Votes: 1
SFID: 1113727#
Submitted By: unruledboy
It does have a Simplified Chinese Unit Test in the .net
provider, it works, but not for the system overall, for
example, non-ascii characters cannot be the table name.
====== Test Details ======
Non-ascii locale must be on FB test machine (currently this is not so). Script must use 'set names <N>' where <N> = locale, and also script must be encoded using ANSI codepage rather than OEM.
AFAIK, no problems with this ticket on POSIX (discussed with Alex, 11-sep-2018).
The text was updated successfully, but these errors were encountered: