Re: Localizing absolute file name in Cocoa
Re: Localizing absolute file name in Cocoa
- Subject: Re: Localizing absolute file name in Cocoa
- From: Ken Thomases <email@hidden>
- Date: Fri, 22 May 2009 12:54:04 -0500
On May 22, 2009, at 12:48 PM, Michael Ash wrote:
On Fri, May 22, 2009 at 1:15 PM, Arun <email@hidden> wrote:
The displayName API will give me only the file name not the
absolute path of
the file.
Ex: If i have a path as /Users/user/temp.txt, only it will return
temp.txt.
Similarly componentsToDisplayForPath API will give me an array of
NSStrings
containing user, temp.txt
But my requirement is to get a localized string for Complete
absolute path
/Users/user/temp.txt
Did you *try* those APIs before you rejected them?
NSFileManager.defaultManager().componentsToDisplayForPath_("/
Users/mikeash/Movies")
(
Fear,
Utilisateurs,
mikeash,
"S\U00e9quences"
)
That's with the current language set to French. It's PyObjC, but it's
all Cocoa in the end....
I think his point is that the components don't have a one-to-one
correlation to the elements of the POSIX path.
However, I think what Arun is asking doesn't make sense. Localizing
only makes sense for display. The path on disk is certainly not
localized. For display, you should use componentsToDisplayForPath:
regardless of the fact that it produces a path which doesn't
correspond to the POSIX path. In fact, that's _why_ it produces a non-
POSIX-like path -- because it is inappropriate to display a POSIX-like
path to the user.
Regards,
Ken
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden