New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect encoding tooltips (ko_KR) #1206

Closed
to302 opened this Issue Oct 31, 2017 · 3 comments

Comments

Projects
None yet
4 participants
@to302
Copy link

to302 commented Oct 31, 2017

Details for the issue

same as #1107
but I use in korean.
sqlite3

Useful extra information

I'm opening this issue because:

  • DB4S is crashing
  • DB4S has a bug
  • DB4S needs a feature
  • DB4S has another problem

I'm using DB4S on:

  • Windows: ( version: win 7 pro )
  • Linux: ( distro: ___ )
  • Mac OS: ( version: ___ )
  • Other: ___

I'm using DB4S version:

  • 3.10.1
  • 3.10.0
  • 3.9.1
  • Other: 3.10.99

I have also:

@karim karim added the bug label Oct 31, 2017

mgrojo added a commit that referenced this issue Nov 1, 2017

Fixed incorrect display of SQL calltips containing non-US-ASCII chara…
…cters.

QScintilla was incorrectly converting the text of the calltips to Latin1
although the encoding was set to UTF-8.

This fixes #1107 (Russian) and  #1206 (Korean).
@MKleusberg

This comment has been minimized.

Copy link
Member

MKleusberg commented Nov 2, 2017

Thanks to @mgrojo this should be fixed by the way. Can you test the latest nightly build and check if it's working on your system as well, @to302? 😄

@justinclift

This comment has been minimized.

Copy link
Member

justinclift commented Nov 9, 2017

Closing this due to lack of response.

@to302 This should be fixed now in our latest nightly builds. If you get a chance to test it, and it doesn't work for you, please reopen this issue so we can investigate. 😄

@to302

This comment has been minimized.

Copy link
Author

to302 commented Nov 13, 2017

@MKleusberg @justinclift It works well., thanks you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment