handle non-ASCII emoji names

What does this PR do?

Together with sfm-js!2 (merged), this should provide complete support for non-ASCII names of custom emoji.

In addition to always using the more inclusive regexp for validating emoji names, we also need to normalize emoji names, aliases, categories.

The latter point is necessary to allow matching, for example, ä against a+combining diaeresis.

Contribution Guidelines By submitting this merge request, you agree to follow our Contribution Guidelines

• I agree to follow this project's Contribution Guidelines
• I have made sure to test this pull request

requested review from @fEmber, @esm, @supakaity, @Leah, @luna, and @Marie

assigned to @dakkar

It does let me change the name to include unicode however now emojis don't show up anywhere but the emoji suggestions/autocomplete.

added 1 commit

• b6f41a28 - pull in sfm-js that supports non-ascii in emoji names

Compare with previous version

resolved all threads

Can confirm that in case of text it does get picked up

though using emojis with non-ASCII characters for reactions does not work and results in the default one as there was no logic applied to handle those in reactionservice as this regex fails to match non-ASCII characters

added 1 commit

• 0f3764ff - teach ReactionService about non-ASCII emoji names

Compare with previous version

resolved all threads

approved this merge request

There's a lot of duplicate normalization calls. Is there any way to merge them into a common routine?

approved this merge request

approved this merge request

resolved all threads

merged

mentioned in commit d0a2708f

added federation label