bugdbsh - Bugs: bug #31191, Charset support

 
 

bug #31191: Charset support

Submitter:  Ben Spencer <dangerousben>
Submitted:  Sat 02 Oct 2010 08:40:28 AM UTC
   
 
Category:  None Severity:  5 - Blocker
Item Group:  None Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open
* Mandatory Fields

Add a New Comment Rich Markup
   

Sat 02 Oct 2010 08:40:28 AM UTC, original submission:  

dbsh currently uses non-unicode ODBC functions for everything and naïvely assumes that the data it receives is in the charset of the current locale.

I think the solution here is to use the unicode ODBC functions but these may not work well with non-unicode drivers.  Alternatively it could support both sets of functions but I don't know if there's a way to detect whether you're using a unicode driver.  When using non-unicode functions it could assume Windows-1252 (or can the codepage be detected), or allow the user to define the source charset, perhaps on a per-DSN basis.

It may also be useful to allow the user to select an output charset (eg when they're redirecting to files), or maybe they should just change their locale.


Ben Spencer <dangerousben>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by dangerousben (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    No changes have been made to this item

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code