Bug fix for encoding prolems under Linux with barely UTF-8 support and add ctypes support for NLPIR #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm using Linux Mint 15 with barely UTF-8 support, running
python demo.pywill give the wrong encoding outputs.Using
unicodeand then encode it to the specified encoding is a good practice and easy to port across platforms.Also a file called
demo_linux-utf8.pydemonstrating encoding problems is presented.Besides
SWIGapproach, people may want to tryctypes, demos for linux32 and win32 are provided with a brief README.