utfcpp
utfcpp copied to clipboard
nemtrif
UTF-8 with C++ in a Portable Way
Hey, I'm working on a project using this, but I use C++20. I'm getting the following warning: ``` In file included from c:\msys64\opt\devkitpro\devkitarm\arm-none-eabi\include\c++\12.2.0\bits\stl_construct.h:61, from c:\msys64\opt\devkitpro\devkitarm\arm-none-eabi\include\c++\12.2.0\bits\char_traits.h:46, from c:\msys64\opt\devkitpro\devkitarm\arm-none-eabi\include\c++\12.2.0\string:40, from c:\msys64\opt\devkitpro\devkitarm\arm-none-eabi\include\c++\12.2.0\bitset:47, from...
Adds the following advantages: - utf8::cpp is available, even when installed - cmake is aware of the library version - compatible with previous usage: target utf8cpp available when installed
Since #92 is not really fixed, we should suppress the compiler warning. I was hardly figuring out a solution without suppression, but to have the `append` as generic as it...
A couple of important missing features is the ability to directly iterate utf16 strings codepoints and appending codepoints to existing utf16 encoded strings. For iterating codepoints, one implementation can be...
In c++20, u8string is added. Is there any plans to add convertion between std::string and std::u8string, and also support something like std::u8string utf8::utf16to8(std::u16string)?
Tested with a **126MB UTF-8 format text file** against ww898's [https://github.com/ww898/utf-cpp] Testing source code here: https://github.com/chipsethan/UTF-test.git It seems yours has a little room to improve. I hope you can optimize...
What is the intended include for this lib? - `#include ` maybe to generic - `#include ` even less generic and can conflict - `#include ` preferred although does not...
Hello, when I include the library (v4.0.5) in my code, I get the 2 following warnings. Not sure it comes from my code. Maybe the way I include it? ```...
