4 ms·

Since when?

louthy 3y ago
Since forever according to the OP
veave 3y ago
Misspellings, mistranslations, strings that don't fit in the label/button, harder to google errors in other languages, etc.
- Findecanor 3y ago
  What GUI toolkit are you using in 2023 where a widget doesn't adjust its size the size of its text label?
  - crazygringo 3y ago
    Literally any fixed-size dialog box ever. Which seems to still be mostly the norm for apps in any desktop OS for things like preferences/settings dialogs.
  - BasedAnon 3y ago
    Alot of UIs just can't deal with the size of a box being resized, so they instead adjust the size of the text, but for languages like Arabic and Japanese this can easily make text unreadable because characters often rely on finer details to be understood
  - stinos 3y ago
    There are so many other ways this can happen that it's really not surprising this happens. Like: started 20 years ago with the UI toolkit in English and a junior dev hence fixed size then suddenly got a growing customerbase in another language and slammed on a translation only to realize it would be a pretty large effort to track down and change each label to resize. Or even just: things adjusting size can simply be a big no depending on software (and you'd use truncation+toltip), because one doesn't want to waste space and/or keeps things aligned so it's easier to learn where everything is. Your browser tabs probably don't adjust size to text, just to name one thing.
  - deleted 3y ago
    [deleted]
- BasedAnon 3y ago
  Also text that's the wrong way or not ligaturized
- crickey 3y ago
  These are localization issues. If the GUI was done in another language then US from start it wouldnt be an issue. Of course sloppy work is bad, doesnt mean it’s inherently bad
shpx 3y ago
I was going to say since the invention of ASCII in 1963, but there were encodings before it and arguably you could say since the invention of Morse code in 1844.
andy81 3y ago
The worst localization bug I'm aware of is the default conversion of string to datetime in MS SQL Server. If the session language is non-US, the ISO formatted string '1991-02-03' becomes 2rd March rather than 3rd Feb. yyyyMMdd works as expected.

Since when?

Since forever according to the OP

Misspellings, mistranslations, strings that don't fit in the label/button, harder to google errors in other languages, etc.

Findecanor 3y ago
What GUI toolkit are you using in 2023 where a widget doesn't adjust its size the size of its text label?
- crazygringo 3y ago
  Literally any fixed-size dialog box ever. Which seems to still be mostly the norm for apps in any desktop OS for things like preferences/settings dialogs.
- BasedAnon 3y ago
  Alot of UIs just can't deal with the size of a box being resized, so they instead adjust the size of the text, but for languages like Arabic and Japanese this can easily make text unreadable because characters often rely on finer details to be understood
- stinos 3y ago
  There are so many other ways this can happen that it's really not surprising this happens. Like: started 20 years ago with the UI toolkit in English and a junior dev hence fixed size then suddenly got a growing customerbase in another language and slammed on a translation only to realize it would be a pretty large effort to track down and change each label to resize. Or even just: things adjusting size can simply be a big no depending on software (and you'd use truncation+toltip), because one doesn't want to waste space and/or keeps things aligned so it's easier to learn where everything is. Your browser tabs probably don't adjust size to text, just to name one thing.
- deleted 3y ago
  [deleted]
BasedAnon 3y ago
Also text that's the wrong way or not ligaturized
crickey 3y ago
These are localization issues. If the GUI was done in another language then US from start it wouldnt be an issue. Of course sloppy work is bad, doesnt mean it’s inherently bad

shpx 3y ago

I was going to say since the invention of ASCII in 1963, but there were encodings before it and arguably you could say since the invention of Morse code in 1844.

andy81 3y ago

The worst localization bug I'm aware of is the default conversion of string to datetime in MS SQL Server. If the session language is non-US, the ISO formatted string '1991-02-03' becomes 2rd March rather than 3rd Feb. yyyyMMdd works as expected.