Open Qhilm opened 7 months ago
Hello @Qhilm,
Thank you for the suggestions. Implementing the reverse search feature should be quite straightforward. However, fulfilling your first request is a bit more complex. It would be best to build our own JSON APIs, where tiles and tags are translated into each language. The JSON files would consist of an array of objects structured like this:
[
{
"name": "shrug emoticon 1",
"emoji": "¯\\_(ツ)_/¯",
"title": "shrug emoticon (style 1)",
"tags": [
"¯\\_(ツ)_/¯",
"emoticon",
"doubt",
"ignorance",
"indifference",
"person shrugging",
"shrug"
]
},
{
"name": "shrug emoticon 2",
"emoji": "¯\\(°_o)/¯",
"title": "shrug emoticon (style 2)",
"tags": [
"¯\\(°_o)/¯",
"emoticon",
"doubt",
"ignorance",
"indifference",
"person shrugging",
"shrug"
]
}
]
This setup would allow the community to propose new additions easily.
EDIT : There's also another aspect to consider: how to implement icons for these emoticons? It might be easy for shorter ones, but for longer ones like the "kick emoticon" \|  ̄ヘ ̄|/_______θ☆( o)/, generating PNGs with a square ratio would be impossible.
Hello, I just discovered this alfred workflow, it is really nice, I like it.
This is a feature request for emoticons such as ¯_(ツ)_/¯
Potential source: https://en.wikipedia.org/wiki/List_of_emoticons
If possible, making it reverse searchable would be great, but that's probably a second feature request.