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

can't encode non-GBK Character into GB18030 #1946

Open
Clayblockunova opened this issue Nov 27, 2024 · 2 comments
Open

can't encode non-GBK Character into GB18030 #1946

Clayblockunova opened this issue Nov 27, 2024 · 2 comments
Labels

Comments

@Clayblockunova
Copy link

Clayblockunova commented Nov 27, 2024

Describe the bug
can't encode non-GBK Character (like most extended Latin letters and Emoji) into GB18030

To Reproduce

  1. Choose "Encode text-Simplified Chinese GB18030";
  2. Type non-GBK Character (like "ä" or "😀") in input;
  3. Empty bytes would be returned.

Expected behaviour
non-GBK Character should be encoded into corresponding GB18030 bytes (4 bytes per character).

@Clayblockunova Clayblockunova changed the title can't encode Ext G CJKV Character into GB18030 can't encode Ext Plane Character into GB18030 Nov 27, 2024
@Clayblockunova Clayblockunova changed the title can't encode Ext Plane Character into GB18030 can't encode non-GBK Character into GB18030 Nov 27, 2024
@kryptokazz
Copy link

Have you checked that the output matches the correct encoding type?
#1646

@Clayblockunova
Copy link
Author

Have you checked that the output matches the correct encoding type? #1646

yes. additionaly, when converting with "input character encoding" option, non-GBK Character also become Empty bytes (1 per 4 UTF16 bytes).

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

No branches or pull requests

2 participants