Richard Damon, on Monday, November 11, 2019 11:19 AM, wrote... > UTF-32 is a reasonable internal operation format, if code-point > operations are important. It does not make a good transmission format,
I agree. That is why, I have not created any files for anything as UTF32 for delivery or anything personal. ;-) It's bulky. However, space is cheap now, and **I think** UTF32 will be a good uniform character set to use. But, yes, we are far away from that idea. > as it is usually takes more media than UTF-8 or UTF-16, and for > transmission, the message size is important. The big issue is that > code-point counting is rarely what you want, you generally want Glyph > counting, which even UTF-32 doesn't provide. Yes, agreed. But, I was just pointing out that a name could be displayed as a symbol. > But this shows that 'Unicode' doesn't handle the name, as is, which was > the point of the rule, if you design you software just assuming that > Unicode can handle all names, you will be very occasionally be wrong. I was talking about the artist previously known as Prince. I was trying to say that it would be feasible to insert that image/symbol as UTF32. It was more of a joke than pretending to have found the answer. :-) josé _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
