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

Support for Euro character encode properly in GBK/GB18030. #115

Closed
wants to merge 2 commits into from

Conversation

lygstate
Copy link

GB18030 already supported.
// TODO: Support GB18030 (~27000 chars + whole unicode mapping, cp54936)

@lygstate lygstate force-pushed the master branch 2 times, most recently from 0fe89e5 to 12e235e Compare January 16, 2016 11:35
    // TODO: Support GB18030 (~27000 chars + whole unicode mapping, cp54936)
Refactoring gbkTableGetter out, cause it's should be cached.
@ashtuchkin
Copy link
Owner

Fixed in recent commit. I used encodeAdd and encodeSkipVals options for dbcs codec, they were introduced just for this purpose. Also, I skipped the option of euro encoding of gbk - it's much easier without it, hope it's fine.

@ashtuchkin ashtuchkin closed this Nov 21, 2016
@ashtuchkin
Copy link
Owner

Also, table caching is not needed because it's only loaded once to convert to internal representation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants