Hot answers tagged globalization
The international standard ISO 8601 specifies a notation that uses the slash “/” between dates expressed in the year-month-day notation, e.g. 2014-07-15/2015-08-01 This is the only reasonable globalized notation. But it should normally be used only a) internally in data representation when a date range needs to be represented as one string and b) as the ...
I think it's better to put n-dash symbol (U+2013) without spaces on sides. This is typographically right. There is no strict rules about it so you are free to use western tradition. What is the difference between dash and n-dash, you can read here: http://en.wikipedia.org/wiki/Dash
I saw this blog post a little while ago. The main article focuses on American placeholder names, but there are some fascinating international examples in the comments section. EDIT: Just found that she did a post about the international ones too.
I would say, if you can code it in and it doesn't make button too wide, to be more specific in button wording. This way, I haven't seen your layout so I'm making an educated guess, the user isn't confused as to what entity the button is for. Activate Region or Activate Program. Approve Request or Deny Request.
I would recommend going with the Google calender approach as it gives the user the flexibility to add additional calenders as needed. However the design change I would make is to ensure that you explicitly call out the holiday or religious occasion of which country it is or which religion so that you dont require users to go and compare the calender overlay ...
The answer depends much on brand marketing policy and organisational structure. Suppose your brand has reginal branches which are relatively independent. Their behavior may vary and thus requirements to contents and even design may vary. If your brand corporate website has centralized maintenance most probably it has no possibility to take into account all ...
A few quick ideas: Have a list of the languages on the right in their own section and designate each language with text and an image (maybe a small flag?). Then when they select a language on the left, the detail information will be on the right. Each language can have it's own detailed information this way. Have a "drop down" (you can see how Skype has a ...
Depends on who is doing/using the translations and the problems they're facing. A few things I've seen/done - often systems have multiple instance of these for different user groups / purposes. Systems pretty much like the one you're outlining - but with popups / other navigation structures to flip between languages. More grid-based systems where you have ...
Only top voted, non community-wiki answers of a minimum length are eligible