User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It only takes a minute to sign up.
Sign up to join this community
Concerning Tags, like on stackexchange, or like in a webapp for creating content, would it be useful to store their name in a localized way: name:{en:'something', de:'someth...', ..} instead of name:'something'?. The language values could possibly be the same than en (default).
Should it rather be all english, or a multi-language name, searchable per language?
What are the risk, or advantage of i18n for tags?
Allowing tags in different languages isn't the same as having translations for each tag.
Translations for tags can be very inconsistent, as they are tags in the end, their purpose is to group unstructured/unpredictable content together.
Tags has certain meaning for a certain group of people, and is likely limited to their cultures and languages. Often we go to twitter and do not understand what a specific hashtag means, imagine how weird it becomes if twitter enabled hashtag translations, they are still tags in the end - debatable.
take a look at this http://ui-patterns.com/patterns/Tag
If the case was categories, translations make sense, where the structure is predefined, managed and most likely fixed from the beginning.
