This project was moved to https://github.com/DuffsDevice/tinyutf8/ and is not being maintained on sourceforge anymore.
License
BSD LicenseFollow tiny-utf8
You Might Also Like
Whether natural disaster, cyberattack, or plain-old human error, data can disappear in the blink of an eye. ConnectWise BCDR (formerly Recover) delivers reliable and secure backup and disaster recovery backed by powerful automation and a 24/7 NOC to get your clients back to work in minutes, not days.
Rate This Project
Login To Rate This Project
User Reviews
-
Hello Jake. I'm just posting some of my first impressions on your library. Also, I'm glad that you are developing this project I really miss some easy to use C++ library for working with utf-8 and unicode in general. A slightly more complete (and easier to read) review is available on Pastebin with address: /m4jN6JDw. I posted it there because SourceForge would not keep my line breaks, making it hard to read my review properly. My considerations: I missed a short example of a use case to figure out the most interesting facilities your library has to offer, a short example on the summary page would suffice. I have some doubts: 1. Can I convert other encodings to utf-8 and back? If yes which encodings? This would be great to make my library work on non-utf8 environments. 2. What is the return type of `operator[]`. A suggestion: It might be interesting to add a function like this: ```C++ std::ostream& operator<<(std::ostream& os, const utf8_string& t); ``` So that I could print out the string easily with `std::cout << str << std::endl;`. Outputting the c_str() representation of the string might be enough and would probably make easier to make short examples using the library. However, I understand that there are some encoding concerns regarding the behavior of this function, maybe it is not the right time to implement it. Lastly, about your question on adapting the library for new types like `wchar_t` and `char32_t` or making it header only, I would vote for adapting it to use `char32_t` in special, since `wchar_t` implementations vary too much to use safely. I hope these suggestions help, I will finish reading the header and maybe I will use it.