Extended ASCII support

[GoogleCodeExporter]

I'm very impressed with MinTTY, but I've noticed that extended ascii 
characters don't print correctly.  In my .vimrc I have:

execute 'set 
listchars=tab:'.nr2char(187).nr2char(183).',trail:'.nr2char(183).',extends:
>,precedes:<'

The nr2char commands display '%' as opposed to the characters that they are 
supposed to display.

Original issue reported on code.google.com by ir0nh...@gmail.com on 1 Jan 2009 at 12:17

[GoogleCodeExporter]

Original comment by andy.koppe on 1 Jan 2009 at 12:55

• Changed state: Accepted
• Added labels: Component-Logic, Priority-High, Type-Defect
• Removed labels: Type-Enhancement

[GoogleCodeExporter]

Fixed in r72 on the 0.3 branch. Quite an appalling bug: for some mad reason I'd
changed a couple of variable declarations from unsigned char to plain char, 
which
meant that characters beyond 127 were sign-extended when converting them to 
int. More
worryingly though, this had been broken for a long time and I never noticed.

Original comment by andy.koppe on 1 Jan 2009 at 6:53

• Changed state: Fixed
• Added labels: FixedIn-0.3.1

[GoogleCodeExporter]

Excellent, thanx for the quick fix!  Is there a binary available, or do I need 
to 
compile from source?

Original comment by ir0nh...@gmail.com on 1 Jan 2009 at 1:20

[GoogleCodeExporter]

I just compiled r74 but I'm still experiencing the same behaviour.

Additionally, on compile, I received the following errors (not sure if they are 
expected):

Makefile:53: bufchain.d: No such file or directory
Makefile:53: child.d: No such file or directory
Makefile:53: config.d: No such file or directory
Makefile:53: ctrls.d: No such file or directory
Makefile:53: linedisc.d: No such file or directory
Makefile:53: minibidi.d: No such file or directory
Makefile:53: settings.d: No such file or directory
Makefile:53: term.d: No such file or directory
Makefile:53: termline.d: No such file or directory
Makefile:53: termmouse.d: No such file or directory
Makefile:53: termout.d: No such file or directory
Makefile:53: tree234.d: No such file or directory
Makefile:53: unicode.d: No such file or directory
Makefile:53: winclip.d: No such file or directory
Makefile:53: winctrls.d: No such file or directory
Makefile:53: windialog.d: No such file or directory
Makefile:53: wininput.d: No such file or directory
Makefile:53: winmain.d: No such file or directory
Makefile:53: winprint.d: No such file or directory
Makefile:53: wintext.d: No such file or directory
Makefile:53: wintip.d: No such file or directory
Makefile:53: winres.d: No such file or directory

Original comment by ir0nh...@gmail.com on 1 Jan 2009 at 1:31

[GoogleCodeExporter]

Make sure you checked out branches/0.3 rather than trunk. I'll probably release 
0.3.1
later today.

I'd reproduced the problem and checked the fix with the following command:
/bin/echo -e \\0273\\0267

And yep, those make messages are expected, because the dependency files are 
created
automatically when first compiling. Hints on how to get rid of them would be 
appreciated.

Original comment by andy.koppe on 1 Jan 2009 at 3:16

[GoogleCodeExporter]

Ah, I compiled trunk, not the branch.  I've now compiled the 0.3 branch and it 
works 
like a charm!

Thanx again for the quick fix!

Original comment by ir0nh...@gmail.com on 1 Jan 2009 at 3:26

[GoogleCodeExporter]

You're welcome, and thanks for verifying. This one was just too embarrassing to 
leave
it hanging around for long. :)

Original comment by andy.koppe on 1 Jan 2009 at 4:59

• Changed state: Verified

[GoogleCodeExporter]

Original comment by andy.koppe on 2 Jan 2009 at 10:46

• Added labels: Milestone-0.3.1
• Removed labels: FixedIn-0.3.1