Emoji Çevirici

15 dilde emoji adlarını ve anahtar kelimelerini görün. Herhangi bir emojinin Japonca, Korece, İspanyolca ve daha fazlasında nasıl adlandırıldığını bulun.

Converter

Dil Ad Anahtar Kelimeler

How to Use

  1. 1
    Enter or select an emoji

    Type an emoji directly into the input or search by English keyword to find the emoji you want. The tool looks up the emoji's CLDR annotation data to retrieve its official name and keywords in each supported language.

  2. 2
    Select target languages

    Choose from up to 15 languages including English, Korean, Japanese, Chinese (Simplified), Spanish, French, German, Portuguese, Arabic, Hindi, Turkish, Indonesian, Vietnamese, Russian, and Thai. All name data comes from the CLDR dataset.

  3. 3
    Read official CLDR names

    Review the official CLDR short name (used by screen readers and input methods) and the keyword list for each language. Note that names are localized independently — a direct translation of the English name is not always used, as cultural adaptation sometimes produces different but culturally appropriate names.

About

Emoji translation — providing names and keywords across multiple languages — is made possible by the Unicode CLDR (Common Locale Data Repository) project, which maintains multilingual annotation data for the entire Unicode emoji set. CLDR annotations serve two purposes: the 'tts' field provides the pronunciation used by screen readers and voice assistants, while the keywords field powers emoji search in keyboards, browsers, and messaging apps. Both fields are independently localized, meaning that emoji names in Japanese, Arabic, or Spanish reflect authentic usage in those languages rather than mechanical translation from English.

The internationalization of emoji names reveals interesting cultural dimensions of the emoji system. Food emoji tend to retain their culture-of-origin names (sushi, ramen, bento), while gesture and expression emoji often receive culturally adapted names that better match local interpretive norms. Some emoji that are unambiguous in one culture carry different connotations in another, leading CLDR contributors to choose annotations that prioritize local meaning over global consistency.

For accessibility, CLDR annotations are the primary mechanism by which emoji become comprehensible to screen reader users. The Web Content Accessibility Guidelines (WCAG) encourage developers to ensure that emoji used in content either have accessible text alternatives or are purely decorative. When emoji convey meaning, the CLDR 'tts' name — exposed through proper ARIA attributes or by surrounding the emoji with invisible accessible text — ensures that the content remains usable by people who access the web through assistive technology. Understanding CLDR's role in the emoji ecosystem thus bridges Unicode data engineering and inclusive design practice.

FAQ

What is the CLDR emoji annotation dataset?
CLDR (Common Locale Data Repository) is a project maintained by the Unicode Consortium that provides locale-specific data for software internationalization. For emoji, CLDR provides two kinds of annotations: a 'tts' (text-to-speech) short name used by screen readers and voice input, and a set of keywords used by search and input method editors. These annotations are maintained by native speakers through a community contribution process at the CLDR Survey Tool. As of CLDR 45, emoji annotations exist for over 60 locales, making it the most comprehensive multilingual emoji naming dataset available.
Are emoji names translated directly from English in other languages?
Not always — CLDR annotations are localized independently for each language, not mechanically translated from English. For example, the English name for 🍱 is 'bento box', but the Japanese CLDR name uses the native term 弁当 (bentō), which is the original word. Cultural adaptation in CLDR means that food emoji, gesture emoji, and culturally specific objects often receive names reflecting local usage conventions rather than direct translations. This makes CLDR annotations more accurate and useful for native speakers, but it means you cannot reliably derive emoji names in one language by translating from another.
How do screen readers handle emoji?
Screen readers use the CLDR 'tts' (text-to-speech) annotation to pronounce emoji. When a screen reader encounters U+1F600, it looks up its annotation data — in English, this produces 'grinning face' — and speaks that text aloud. The quality of the experience depends on how well the CLDR annotation captures the semantic content for the context. When emoji are used decoratively or in high density (such as '🎉🎉🎉🎉'), screen readers may read out each emoji name in sequence, creating a poor audio experience. WCAG 2.1 and accessibility best practices recommend using aria-label to provide accessible text alternatives when emoji are used to convey meaning rather than decoration.
Why do some emoji have very different names across platforms?
Platform vendors can choose to use names other than CLDR annotations in their emoji pickers and keyboards, and historically many have done so. Apple's emoji picker has used proprietary names that sometimes differ from CLDR, as have older versions of Android and Samsung's One UI. However, the trend since approximately 2018 has been for major platforms to align their displayed emoji names with CLDR data, since CLDR is also used as the source for input method dictionaries and voice recognition. The official Unicode character name (all-caps, from the UnicodeData.txt file) is a separate, normative identifier that is never changed, even if CLDR short names are updated.
What languages have complete emoji annotation coverage in CLDR?
CLDR has 'modern' (fully complete) emoji annotation coverage for its core set of locales, which includes English, German, French, Spanish, Portuguese (Brazil), Japanese, Chinese (Simplified and Traditional), Korean, Arabic, Hindi, Russian, Indonesian, and several others. Coverage completeness is tracked by the CLDR project and reported as a percentage of required data items. Locales without complete modern coverage may be missing annotations for newer emoji added in recent Unicode versions, since volunteer contributor capacity varies by language. The CLDR Survey Tool allows the community to submit and vote on annotations, and contributions are encouraged for underrepresented languages.