3 ms·
Words in interfaces are terrible unless a lot of thought goes into localization. For example, consider an American UI designer creating a 'Save' button. Now, t
by Tijdreiziger 4y ago
Words in interfaces are terrible unless a lot of thought goes into localization.
For example, consider an American UI designer creating a 'Save' button. Now, translate the button to Dutch ('Opslaan').
What you'll see very often is that the button is only wide enough for the English text ('Save'), so 'Opslaan' gets rendered as something like 'Ops...', which is obviously a terrible experience.
I just set my computer and phone interfaces to English to sidestep this problem, but not everyone wants to do this.
- KerrAvon 4y agoOn any Apple platform, that would be considered a serious bug. It shouldn’t ever be a problem in SwiftUI, and you can achieve the necessary dynamism without too much trouble by using layout constraints in both AppKit and UIKit.
- code_duck 4y agoApple's own products do this often. For instance, an instrument in one of my tracks in iOS GarageBand is listed as "Kind...ass". It's supposed to be "Kindergarten Bass". https://i.redd.it/0ncp6hgad7v91.jpg https://i.redd.it/0ncp6hgad7v91.jpg
- 0x445442 4y agoWhy does the word “save” need to be in a button? The claim that natural language is an inferior interface is up for debate.
- ziddoap 4y agoI'm pretty confident that "save" is only one of many examples where this issue can happen. >The claim that natural language is an inferior interface is up for debate. They only said that it requires much more thought, not that the debate is finished with their comment.
- afandian 4y agoIt's been a decade since I did any app development on MacOS. But I do recall having to create a separate dialog box XIB resource for each language, with different sized buttons.
- galad87 4y agoThat's not needed anymore when using auto-layout, introduced in 10.7 if I remember correctly.