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

UTF-8 and UTF-16 native string support for performance #2194

Open
xbotuk opened this issue Aug 10, 2021 · 2 comments
Open

UTF-8 and UTF-16 native string support for performance #2194

xbotuk opened this issue Aug 10, 2021 · 2 comments

Comments

@xbotuk
Copy link

xbotuk commented Aug 10, 2021

As sometimes the source and target systems could be using native UTF-16 strings. In some instances one is UTF-8 and other is UTF-16.

Can you please add support to configure native string supports or ways to minimise the unnecessarily string conversions overheads?

@sphaero
Copy link
Contributor

sphaero commented Nov 21, 2021

Any suggestions how to implement this. PR's are welcomed

@sphaero
Copy link
Contributor

sphaero commented Mar 18, 2022

Perhaps as a reference:

"In particular, we believe that the very popular UTF-16 encoding (often mistakenly referred to as ‘widechar’ or simply ‘Unicode’ in the Windows world) has no place in library APIs except for specialized text processing libraries, e.g. ICU."

from http://utf8everywhere.org/

Which argues to use char* with utf-8 everywhere.

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

No branches or pull requests

2 participants