fuif VS tiny-utf8

But they didn't even explain what FUIF or PIK might be in that section or even the entire article!

To understand that article required me searching for FUIF [1], PIK [2] and a brief explanation of what JPEG XL is trying to achieve.

I double down on my "complaint" - I'd call it constructive criticism - that article was poorly written. It's actually quite a good story that their Free Universal Image Format (FUIF) has achieved what it has. That's a great acronym, especially for a world that thinks JPEG XL is a good acronym! Why not put in in the article.

To save anyone else time:

[1] https://github.com/cloudinary/fuif

here is FUIF (one of JXL parents) author writing about benefits of progressive: https://github.com/cloudinary/fuif

There was also an update to it called FUIF - Free Universal Image Format

https://github.com/cloudinary/fuif

But it too got superseded by JPEG XL (.jxl) https://jpegxl.info/

I've recently been trying to use the tiny-utf8 library in Rcpp in order to handle unicode, but I am having serious issues trying to understand how the "wrap" part of it works. For the "as" part, I've received some help on Stack Overflow, which works great, but without a wrap(), it seems that I cannot convert the data type into those of Rcpp. I've been reading this post and trying to replicate it, but with utter failure after long hours, due likely to a lack of knowledge in C++ templates. Could someone give some pointers as to how I might go about doing this? I am at the end of my wits at this point.