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

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