strf VS text

You might get interested in trying strf library instead:

If you want a formatting library that supports well char8_t and UTF, you might get interested in the one I'm developing: Strf.

You might like the strf formatting library then

You can also use https://github.com/robhz786/strf to convert utf-8 to utf-32 ( as demonstrated here).

Format strings enable the use of tools like gettex. However, with the strf formatting library, It is possible to use them without a format string.

So it is a formatting library (strf), and if one wants to make a type xyz printable, one can either specialize a template or overload tag_invoke function, like below:

The Strf formatting library may solve your problem:

There is the strf formatting library. Its current version (0.14) is not working well in CUDA, but I'm working to fix this into the next release, which should come soon. The usage would be:

strf

It sounds like a generic length function in Unicode in 2023 is no longer a good idea. These articles complaining about the variety of lengths in Unicode are annoying at this point. Pretty much all of them can be summed up as, "Well, it depends." And, that isn't wrong. But nerds love to argue until they are blue in the face about the One Correct Answer. Sheesh.

This is the most interesting comparison article I have seen in years about Unicode processing in C++: https://thephd.dev/the-c-c++-rust-string-text-encoding-api-l...

The author is also the lead on an open source C++ Unicode library called ztd.txt: https://github.com/soasis/text

How does this compare with https://github.com/tzlaine/text and https://github.com/soasis/text ?

You might consider https://github.com/soasis/text (https://ztdtext.readthedocs.io/en/latest/index.html) which is a proof of concept of this proposal that we may get in C++26

from this link for the tested option that was the only one to check all the boxes green in the article... it makes me ask myself if the article was written biased with the purpose of promoting ztd.text and that these boxes/criteria were to an extent cherry-picked with that purpose in mind.

Github: https://github.com/soasis/text

That's a huge misrepresentation of the reality. Of course it has its own string class, because there has not been a proper type in the standard library for Unicode text, and for many, we are not there yet (otherwise we would not be having other libraries filling the empty space).

You can checkout ztd.text, which implements presented ideas. Few years passed, so they were more polished too.

The library you talk about is https://github.com/soasis/text and he has an account here.

Project Link: https://github.com/soasis/text Announcement/Blog Link: https://thephd.dev/any-encoding-ever-ztd-text-unicode-cpp

PS: found some example code in the github project which seems to take care of the special Windows situation:

https://github.com/soasis/text/blob/main/examples/documentat...

Unfortunately this doesn't look so simple anymore.