ISO Designators versus Legacy Language Designators for resources in Xcode
ISO Designators versus Legacy Language Designators for resources in Xcode
- Subject: ISO Designators versus Legacy Language Designators for resources in Xcode
- From: Ulf Dunkel <email@hidden>
- Date: Fri, 04 Apr 2008 08:37:21 +0200
- Organization: invers Software
Honestly, the Apple Internationalization Programming Topics drive me nuts.
In
<http://developer.apple.com/documentation/MacOSX/Conceptual/BPInternational/Articles/LanguageDesignations.html>
Apple tells us (at the very end of this chapter):
---snip---
Legacy Language Designators
---------------------------
In addition to the ISO language designators, previous versions of Mac OS
X also supported a set of legacy designators. These designators let you
specify a language by name, instead of by a two or three character code.
Designators included names such as English, French, German, Japanese,
Chinese, Spanish, Italian, Swedish, and Portuguese among others.
Although these names are still recognized and processed by CFBundle and
NSBundle, their use is deprecated and support for them in future
versions of Mac OS X is not guaranteed. Use the codes described in
“Language Designations” and “Regional Designations” instead.
---snap---
We have adjusted all our Cocoa apps to only use the new ISO designators
- and run into several problems day by day.
Xcode does still create new projects using "English.lproj".
Xcode (2.5 as well as 3.0) don't open Interface Builder automatically
when I double-click on e.g. MainMenu.nib in my project, when it doesn't
contain a localized English .nib file. Instead I have to unfold the
MainMenu.nib entry and double-click on the en entry.
Xcode 2.5 doesn't recognize "en" as a localizable language when I "Add
localization" to a nib entry in my project.
Xcode 3.0 even crashes when I enter "en" ->
---snip---
File:
/SourceCach/DevToolsSupport/DevToolsSupport-893/FoundationAdditions.subproj/TSFileManager.m
Line: 308
Object: <TSFileManager:0x0207fe50>
Methode: createDirectoryAtPath:attributes:recurse:
path should be a non-empty string, but it is nil
---snap---
So I really wonder if Apple does indeed follow their own
Internationalization Programming Topics.
Is anyone of Apple willing and allowed to give me an official statement
on this?
PS: I really like the ISO encoding designators for their clear and even
more powerful usage. But today they cause much problems.
Best Regard, Ulf Dunkel
_______________________________________________
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