I'm making a piece of software that is intended to be localized in the future. I'm wondering how ellipsis (the ... indication an action opens a new window/dialog) are typically localized.
Do all languages use ellipsis this way? Can I safely add the ellipsis in my own code and reuse a string, e.g. Save As, both for the menu entry (Save As...) and the dialog title (Save As) or should the strings with and without ellipsis be specified in the translation table separately?
I often find myself asking this too. Should meaningful punctuation be part of the translatable text, or can it be safely suffixed outside?
You've not said what platforms you're developing for, so I can only come at this from my experience (web apps).
A good source of translation examples can be found in the WordPress community. These are used on millions of websites and you will find several cases of an ellipsis used in this context. e.g. the text "Saving..." to indicate progress, or "Read more..." to indicate that something follows on.
In these cases the punctuation is part of the translatable text, so I downloaded a few translations in non-latin scripts to see what they did with it:
Japanese, which uses different full-stops to western languages keeps the style of the source text:
続きを読む...
Arabic and Hebrew (which read right-to-left) both use the same punctuation, but simply render in reverse. Your platform (e.g. browser) should handle the text direction:
قراءة المزيد...
להמשך קריאה...
Also Thai, Indonesian, Sinhalese ... I could go on:
อ่านเพิ่มเติม...
Baca selanjutnya...
තවදුරටත් කියවන්න...
So it seems it's a common convention, but that doesn't necessarily mean you should hard-code it.
Worth noting that WordPress includes many hard-coded uses of an ellipsis for use when long text is truncated. Not quite the same use case as "Save As...", but interesting that such an international project would confidently use it in this way.
Personally I've often made the decision to suffix the punctuation in case I want to change it later without invalidating translations. I'm yet to find this is a problem, but there's always tomorrow.
Having separate strings in your translation table is obviously the safest thing to do. It also offers translators some discretion over the slightly different contexts (i.e. between button and title).
Side note: The triple dot used above isn't a true ellipsis. That's an academic point here I think.
Here's one case study of Japanese-to-English localization of ellipsis in games: https://legendsoflocalization.com/qa-japanese-ellipsis-usage-and-english-translation/ (and here's an archived version, in case the above goes down for whatever reason: http://archive.is/tdj59).
The author provides one example game in which five-dot, three-dot, two-dot, and even one-dot ellipsis are used in the Japanese version, but three-dot ellipsis are used consistently in the English version.
So the takeaway from this case study seems to be that ellipsis can be localized (in Japanese at least), although the mappings aren't quite clear (English always uses 3-dot ellipsis whereas Japanese seems to vary depending on the context).
There is a glyph that is specifically the ellipse which can then be localized … vs ... (drag/select them with your cursor to see how they compare, 1 character vs 3) See: https://en.wikipedia.org/wiki/Ellipsis
If designing for the web, you can use CSS to truncate your text with an ellipse, the browser will then handle how this is displayed automatically.
© 2022 - 2024 — McMap. All rights reserved.
