4 ms·
Yeah, I do take your point, and I never denied that all of these are going to be valid consideration for some program for some customer somewhere, my main point
by cwstarblazer 3y ago
Yeah, I do take your point, and I never denied that all of these are going to be valid consideration for some program for some customer somewhere, my main point was that in most cases, it doesn't matter. Like you said, one could probably stop there in most cases. Obviously, the needs of a program doing OCR for ancient languages is different than something spitting out and reading in text from a console or even a Win32 text entry field.
- kjellsbells 3y agoYup. One thing that remains unclear to me (commercially) is: is it better to not internationalize at all if you cant do it perfectly? I honestly don't know the answer. A trivial example I came across the other day was a Spanish hotel website, which had multiple versions for EN/ES/PT etc, but when you came to book, presented some page elements in Spanish and some in English. Would have been better to stixk with one language than do it badly. Which brings me to the point: this is really about money. Internationalization done properly costs serious coin.