Emoji support

[reavessm]

Doxygen does a great job creating webpages based on markdown files, could it also render the emojis in the files?

I have some files where I would like :smiley: to show up as 😃, for example.

[albert-github]

Is there anywhere a, free, translation table between the :smiley: syntax and the corresponding Unicode character 😀 ?
Analogous also for other formats, especially LaTeX?

There is a nice Unicode list (https://unicode.org/emoji/charts/full-emoji-list.html) with all Emoji characters.
There are also tables with the :smiley: syntax (e.g. https://www.webpagefx.com/tools/emoji-cheat-sheet/ or https://gist.github.com/rxaviers/7360908)

[reavessm]

Like this?

[albert-github]

That is the same list as the first list I mentioned in my comment.

I'm looking for a table that translates the e.g. :smiley: to &#x1F600 or U+1F600

[reavessm]

Wow, I can't read today. Sorry about that. Apparently GitHub has a REST API to download the emojis as pngs. I tested by running wget https://github.global.ssl.fastly.net/images/icons/emoji/smiley.png. They also have a Table view. The Table view has the unicode in the url. I can work on making a table as a text file (json, markdown, etc) if that would help

[albert-github]

That table (https://api.github.com/emojis) looks very interesting, it is not 100% complete (but that is probably a minor detail. missing at least Scotland, England, Wales but they are easily added).
There are a few culprits in the table like :man-wrestling: pointing to https://assets-cdn.github.com/images/icons/emoji/unicode/1f93c-2642.png?v8 so it looks lake 2 codes but in fact it are 4: U+1F93C U+200D U+2642 U+FE0F but comparing this table with the https://unicode.org/emoji/charts/full-emoji-list.html table should do the trick.
This gives a good starting point, translation of this table should not be a big issue for me.

[reavessm]

Yeah there definitely are some holes, but here is a json with the unicodes from the table
emojis.json.txt

[t-b]

Aren't the github names just the unicode "CLDR Short Name" names all lower case and with _ instead of spaces? Standardzing on some arbitrary github names does not sound like a good solution.

[lrineau]

@t-b commented on Sep 17, 2018, 4:48 PM GMT+2:

Aren't the github names just the unicode "CLDR Short Name" names all lower case and with _ instead of spaces? Standardzing on some arbitrary github names does not sound like a good solution.

No. For example, :grin: gives 😁, that is U+1F601 with the short name "beaming face with smiling eyes".

[albert-github]

@reavessm thanks for the table, looks like besides the 3 countries there are some more items missing (in the latest file I see 1508 items and the unicode table has 1644 items), not a big issue I'll have to look into it.

@t-b / @lrineau I was already typing, but you found it as well. No the names are not just the "CLDR Short Name" names all lower case and with _" e.g. code U-1F604 has :smile: as "github name" and "grinning face with smiling eyes" as "CLDR Short Name"

[t-b]

@lrineau @albert-github Thanks for the correction.

[albert-github]

I've just pushed a proposed patch, pull request #6534

[albert-github]

When integrating pay attention to #6608 as here also a new command is added (multiple numbers in cmdmapper.h).

[albert-github]

Code has been integrated in master on github.

[sloriot]

@albert-github Looks like there are some regression introduced (not sure if I should open a new issue).
For example I got this warning:

models:2: warning: Unsupported emoji ':Surface_mesh_approximation:' found while handling command \ref

And this output:

Let me know if you need more details.

[albert-github]

@sloriot Thanks for bringing this to our attention.

At first I thought:
In the new update there is the possibilities for emoji, and :Surface_mesh_approximation: is not an emoji so the message is correct. For cases like these the command \: has been introduced: the way to specify this is \:Surface_mesh_approximation\:.

But I see in the image I see that in some cases it looks like the :: part is not handled properly.

So I do think it is a regression, please file a new issue.
I can build the full documentation but this takes some time, please add to the issue:

• a name of output file where you see the problem
• how to generate documentation of 1 subdirectory (make doc generates all), when easily possible of course)

[sloriot]

Thanks, see #6612

[doxygen]

This issue was previously marked 'fixed but not released',
which means it should be fixed in doxygen version 1.8.15.
Please verify if this is indeed the case. Reopen the
issue if you think it is not fixed and please include any additional information
that you think can be relevant (preferably in the form of a self-contained example).