• 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: "Alexey Proskuryakov" <email@hidden>
  • Date: Sun, 26 Jun 2005 00:10:45 +0400

On Sat, 25 Jun 2005 20:25:55 +0200 Greg Hurrell <email@hidden> wrote:

OTOH, the user experience with names like English.lproj is better.
<...>
I agree. The abbreviation/"letter-codes" are ugly to look at.

I don't agree with either of these posts because they come from an English-centric perspective.

What makes you think so, the .ru domain of my e-mail address? ;-)

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.

As soon as Finder does that (and not only in its latest version, but for a few years), perhaps. But this mailing list is about Xcode, and I think that Xcode templates shouldn't be fixed earlier than that.


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?

A Russian user may understand "Spanish", but not "es". And which language is Swedish, "su", "sv" or "sw"?


I don't know if Apple provides an API for moving back and forth between the ISO codes and localized human-readable representations of those codes (needless to say I think it should)

Hmm, good point... I don't see this functionality exposed as an API - other than going straight to ICU, which isn't recommended.


Currently, I have no use for it in my code, but if you do, please file an enchancement request. It is always better to provide potential use cases and explain the need (there are some subtle questions with such an API, which may explain why they haven't exposed it).

- WBR, Alexey Proskuryakov
_______________________________________________
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: Greg Hurrell <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: dlopen woes under XCode 2.1
  • 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