bugdbsh - Bugs: bug #31191, Charset support

 
 

bug #31191: Charset support

Submitted by:  Ben Spencer <dangerousben>
Submitted on:  Sat 02 Oct 2010 08:40:28 AM UTC  
 
Category: NoneSeverity: 5 - Blocker
Item Group: NoneStatus: None
Privacy: PublicAssigned to: None
Open/Closed: Open

Add a New Comment (Rich MarkupRich Markup):
   

You are not logged in

Please log in, so followups can be emailed to you.

 

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>
Project Administrator

 

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

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

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

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    No Changes Have Been Made to This Item

    Back to the top


    Powered by Savane 3.1-cleanup