Skip to content
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

Input fields don’t show/handle non-ASCII correctly #6008

Closed
Wuzzy2 opened this issue Feb 7, 2014 · 2 comments

Comments

Projects
None yet
5 participants
@Wuzzy2
Copy link
Contributor

commented Feb 7, 2014

This is an issue regarding the ncurses version of C:DDA.

Input fields still have problems with non-ASCII characters. Well, at least that’s what I suspect.

Here’s an example of the problem:
Create a note on a map with the text “gefährlich” and save it. The input field fails to render the character “ä” correctly, instead, two garbage characters are visible. To me, they are black, bold on a white background and blink. But create this note anyways. On the map itself, the “ä” renders correctly. Now the real fun begins: Edit the same note again, now you will see the word “gefährlich” but it still has a problem. The cursor is on the “h” and not on the field behind it (as usual). And the “ä” is black, block, on a white background and blinks. And if you try to move the cursor or type something, the text field behaves really weird, charcters get overwritten, etc.

The “window” for entering the character template name seems to behave the same way.

A similar but not identical problem exists for the input field of the character name and the world name. If you input a non-ASCII character (I suspect), all you get is some garbage characters instead.

I expect the input fields to either ignore any characters they can’t handle or to properly handle UTF-8 (for example). In any case, there should be no garbage characters. ;-)

C:DDA version: f64ce22
Tested on GNU/Linux with ncurses

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@VlasovVitaly

This comment has been minimized.

Copy link
Contributor

commented Feb 10, 2014

I tried to fix that in #5994. Right now i don't have time to do finish this PR.
You need to wait for fix. I know about this issue and will fix it when I have some available time.

@BevapDin

This comment has been minimized.

Copy link
Contributor

commented Dec 10, 2017

Can anyone still reproduce this? Or similar problems at other places?

@BevapDin BevapDin closed this Jan 10, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.