Re: Localizing about files
Re: Localizing about files
- Subject: Re: Localizing about files
- From: email@hidden
- Date: Tue, 5 Mar 2002 13:04:29 -0800
What's the problem in just providing a folder "Read Me First", which
would
contain "English.rtf", "Czech.rtf", "Hebrew.rtf", "Bantu.rtf",
"Swahili.rtf",
"Esperanto.rtf", "Latin.rtf", and whatever else you like?
Both as a developer and as a user I would like that. You would not? Why?
One, it requires the user to find the proper file. Given that the
computer already knows the user's preferred language(s), it should do
this for the user.
Two, it scales very poorly. If the app is localized to a dozen
languages, it's a bit of an annoying search to find the right file. If
it's localized to 50, it's totally unacceptable.
Is there a drawback to providing the user with a solution to this
problem? It seems like a slam dunk to me. How would you feel about a
Cocoa app that presented a panel on launch saying "please choose the
language you'd like this app to run in:" with a scrolling list? That
would suck, right? So why does it suck any less when it's the readme
file that effectively has this UI?
Ben Haller
Stick Software
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.