• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Using XCode and en.lproj vs. English.lproj
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using XCode and en.lproj vs. English.lproj


  • Subject: Re: Using XCode and en.lproj vs. English.lproj
  • From: Brian Krent <email@hidden>
  • Date: Sat, 25 Jun 2005 16:24:39 -0400

I don't agree with either of these posts because they come from an English-centric perspective. I think developers should be using the ISO abbreviations (as Apple has been telling them to do for a long, long time now) and that the Finder should display localized, human- readable versions of them in the "Get Info" window.

I agree to that way of thinking, also. (Which I already stated, when I said, "At the very least, end users should never have to see it.")


However, the reality is that it is a English-centric operating system with great localization support.

How is it that the user experience for a Spanish user, for example, is better when the languages are shown as "English", "Spanish" etc instead of "Inglés", "Español" and so forth? You said that abbreviations are "unnatural", "disgusting" and not "humane" (fairly strong words, perhaps you need to calm down) but I suspect that you only think so because you speak English...

No... you misinterpreted me; my fault. I should have been more verbose. I do want the localized views to show it actually localized. I wasn't just thinking of "only English".


Everybody else in the world who doesn't speak English probably finds the use of unabbreviated English language names equally unfriendly and almost as unintelligible.

I think they're still unfriendly and unintelligible in Japanese. My point is that the user-view should see it localized.


My further point is that the Frameworks for developers are English- centric. Whether you'd like to admit it or not, English is the language for the development process in this operating environment.

I can live with going to the ISO codes, but I still don't personally like it.

It's 2005 and there's really no excuse for not being fully localized.

Exactly! _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: Using XCode and en.lproj vs. English.lproj
      • From: Brian Krent <email@hidden>
References: 
 >Using XCode and en.lproj vs. English.lproj (From: João Varela <email@hidden>)
 >Re: Using XCode and en.lproj vs. English.lproj (From: Scott Tooker <email@hidden>)
 >Re: Using XCode and en.lproj vs. English.lproj (From: "Alexey Proskuryakov" <email@hidden>)
 >Re: Using XCode and en.lproj vs. English.lproj (From: Brian Krent <email@hidden>)
 >Re: Using XCode and en.lproj vs. English.lproj (From: Greg Hurrell <email@hidden>)

  • Prev by Date: Re: Using XCode and en.lproj vs. English.lproj
  • Next by Date: Re: Using XCode and en.lproj vs. English.lproj
  • Previous by thread: Re: Using XCode and en.lproj vs. English.lproj
  • Next by thread: Re: Using XCode and en.lproj vs. English.lproj
  • Index(es):
    • Date
    • Thread