Skip to content
This repository was archived by the owner on Nov 9, 2017. It is now read-only.

Conversation

@kblees
Copy link
Contributor

@kblees kblees commented Jul 5, 2012

These patches should fix the Unicode line editing issues in msys bash for most users (see http://groups.google.com/group/msysgit/browse_thread/thread/f365e1c841beef62 ).

The major part of the patch series was backporting the multibyte to wide char conversion functions from newlib 1.20 / cygwin 1.7 to the current msys.dll (based on newlib 1.9), so that bash could be compiled with multibyte support.

I'll send another pull request for the devel branch (binaries only).

Cheers,
Karsten

…tions

Add support for Unicode console input and backport multibyte / wide char
conversion functions from newlib 1.20 (needed by bash for Unicode-aware
line editing).

Signed-off-by: Karsten Blees <[email protected]>
Copy newlib header files to the msys include directory, update msys.dll
import library.

Signed-off-by: Karsten Blees <[email protected]>
Enable multibyte support in the bash release script and fix a small compile
error in the bash multibyte code.

Signed-off-by: Karsten Blees <[email protected]>
Enable multibyte character on input and output and disable ASCII conversion
in etc/inputrc.

Signed-off-by: Karsten Blees <[email protected]>
@kblees
Copy link
Contributor Author

kblees commented Jul 6, 2012

Sorry I forgot to clarify the 'most' in 'most users'.

The console input code in fhandler_console::read currently doesn't decode UTF-16 surrogate pairs (> \u0ffff, e.g. CJK extensions). I couldn't find any hint on how ReadConsoleInputW transmits these (not even in cygwin's fhandler_console), and as I have no way to test this either, I'd like to leave this one to CJK users who actually have that problem.

@stevenkling
Copy link

Want!

@sschuberth
Copy link
Contributor

@stevenkling So if you want this, you could help by

  1. reviewing the code,
  2. applying it to your local clone,
  3. building Git for Windows and verify that it works as expected,
  4. report back here.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants