Issue Details (XML | Word | Printable)

Key: CORE-4863
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Alexander Peshkov
Votes: 0
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
Firebird Core

Ensure correct international input on windows text console with OEM codepage selected

Created: 07/Jul/15 10:44 AM   Updated: 07/Jul/15 11:03 AM
Component/s: Charsets/Collation, ISQL
Affects Version/s: 3.0 RC2, 4.0 Initial
Fix Version/s: None

Environment: Windows
Issue Links:
Relate
 

QA Status: No test


 Description  « Hide
When in Windows in text console OEM codepage is used, command line parameters are passed to the program anyway in ANSI codepage, but text typed on console is (as expected) - in OEM. When such data (dbname, login, password) is passed to DPB/SPB or attach/create database call, they are expected to be in ANSI codepage. Therefore in all cases (at least 2 of them are typing password in "connect"/"create database" commands in isql and input of password from terminal when requested by utility switches) when text is initially in OEM codepage, in should be transliterated to ANSI codepage before passing it to parameters block.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Vlad Khorsun added a comment - 07/Jul/15 10:52 AM
> Therefore in all cases (at least 2 of them are typing password in "connect"/"create database" commands in isql and input of password from terminal when requested by utility switches) when text is initially in OEM codepage, in should be transliterated to OEM codepage before passing it to parameters block.

I'd say it should be converted into UTF8, not OEM

Alexander Peshkov added a comment - 07/Jul/15 11:03 AM - edited
Certainly not to OEM. It was mistype, fixed now.

Should it be ANSI (system) or UTF8 encoding depends upon in what codepage does utility build parameters block. Currently all utilities do work with system/ANSI encoding when building dpb/spb, not with UTF8.

So the obvious goal is to have all data in parameters block in same encoding, known to fbclient library. Will it be ANSI or UTF8 is not great deal - fbclient can transliterate from ANSI to UTF8 itself.