[yjftsjthsd-h]

> AFAIK, everything else is fair game, even emojis

FWIW, I generally expect emojis to be more compatible than other symbols, because they have no legacy meanings - ex. ™ has never been a path separator, or indeed anything else.

[extraduder_ire]

Main problem with "emojis" is that they live outside the basic multilingual plane, and so make bad utf-16 handling really obvious. This is a blessing in disguise, because it acts as a no-brown-m&ms thing, since it's more unarguably broken than not being able to use cuneiform, or musical symbols.

[yjftsjthsd-h]

Yeah, point; I probably should have said something more like "emoji shouldn't have alternative meanings, so they should work if your unicode support is functional (which is a big caveat)." On the bright side, yeah, emoji have been great at pushing things to handle unicode nicely and act as a... I dunno, natural fuzzing case?

[wizofaus]

The problems show up when that name gets stored in a VARCHAR column somewhere...

[veave]

™ is not an emoji. It's part of the "Letterlike Symbols" block.

[yjftsjthsd-h]

Oops, good point. I think I'm going to leave it as-is on account of not knowing of any actual emoji that HN allows, but yes that is technically incorrect on my part.

[veave]

I think the confusion comes from the fact that some platforms render it as a drawing as if it was an emoji. I never understood why...

[yjftsjthsd-h]

Speaking only for myself, the confusion comes purely from the fact that I think of all text as "ASCII" or "Unicode" (...or "something else that nobody should use in the modern era"), and I don't really distinguish within "valid unicode that isn't ascii".

[veave]

™ is part of extended ASCII :)