Re: Using XCode and en.lproj vs. English.lproj
Re: Using XCode and en.lproj vs. English.lproj
- Subject: Re: Using XCode and en.lproj vs. English.lproj
- From: Scott Tooker <email@hidden>
- Date: Thu, 23 Jun 2005 18:30:42 -0700
On Jun 23, 2005, at 3:57 PM, João Varela wrote:
Hello people
I recently joined this list because I am moving all my projects
from CW to xcode. At first I was a little bit daunted by the task
at hand but in the last few days I managed to move two projects to
xcode which now compile and work properly. This is really great. I
have three more to go but the last results are certainly encouraging.
I must say that have tried many times to start using XCode /
Project Builder but before XCode 2.x I would always come back to CW
as I could not stand how slow gcc was. XCode has come a long way
and I can say I am really enjoying XCode 2.1. This would be
unthinkable a year ago. Still, XCode needs improvement especially
in compilation speed and the quality of dead code stripping. The CW
linker is still far superior in this regard. I do hope you guys can
make it better and surpass CW compilers and linkers.
Also another weird thing I noticed is that when I create a common
source folder for shared source files among several projects (and
so they sit outside the current project folder hierarchy) their
code size does not appear in the project window after compilation;
only the files that are present in the same directory as the
project file have their code sizes upon compilation. Is this a bug
or is this intentional? (If it is a bug I can file one).
This is a bug that may be fixed in internal builds. please file a bug
so we can track this.
I am going to file a request bug to improve the syntax coloring of
XCode, so that APIs, methods, classes, etc, get their own syntax
coloring as well like in CW. Actually, everything that is defined
earlier and you can "jump to definition" should have its syntax
color, like in CW. That would be just great.
Finally, I have a couple of questions. I was reading the
documentation about how a modern bundle should look like,
especially that in regard to localization resources. Also Deborah
Goldsmith has urged us to stop using English.lproj or French.lproj
as the directories to put our localized resources and use en.lproj
and fr.lproj instead. However, XCode project stationery still uses
the old locale names and creates an English.lproj directory instead
of creating directories with the proper ISO regional designators.
Thus, I have few questions:
1) Is this a known bug? If not I am happy to file one;
Yes, this is a bug. please file one.
Scott
2) If this is not a bug, how can I configure XCode to create the
localized resource directories with the proper ISO regional
designators? (if this is not possible I can also file a bug)
3) If I start using the new locale designators, will this break my
bundle in earlier versions of Mac OS X such as Jaguar and Panther?
TIA
Joao Varela
_______________________________________________
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
_______________________________________________
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