• 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: completePathIntoString doesn't work with unicode paths??
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: completePathIntoString doesn't work with unicode paths??


  • Subject: Re: completePathIntoString doesn't work with unicode paths??
  • From: Bob Ippolito <email@hidden>
  • Date: Thu, 2 Jun 2005 18:31:35 -0700


On Jun 2, 2005, at 6:28 PM, Jonathan del Strother wrote:

I'm struggling with NSString & some Unicode pathnames. My worst- case scenario test file is something called "Artist-SigurRós,Album- ()和紙.tiff"

I'm constructing the full path of that file without the extension, then using "completePathIntoString" to get all the files that start with "Artist-SigurRós,Album-()和紙". It tells me there are no matches - I know there are two.

However, if I strip down the filename even further, to "Artist- SigurR", then use completePathIntoString, it works fine.

Is this a bug, or am I missing some Unicode subtlety that I need to fix somewhere?

Sounds like a bug to me, but you should probably post some example code that reproduces this problem because you might be doing something else strangely.


[Incidentally, is there any way to have the debugger console display Unicode properly? NSLog(filename) displays the full path, but going to the console and typing 'po filename' strips out the non-ascii characters. ]

you could try: p (char *)[filename UTF8String]

-bob

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: completePathIntoString doesn't work with unicode paths??
      • From: Jonathan del Strother <email@hidden>
References: 
 >completePathIntoString doesn't work with unicode paths?? (From: Jonathan del Strother <email@hidden>)

  • Prev by Date: completePathIntoString doesn't work with unicode paths??
  • Next by Date: Re: completePathIntoString doesn't work with unicode paths??
  • Previous by thread: completePathIntoString doesn't work with unicode paths??
  • Next by thread: Re: completePathIntoString doesn't work with unicode paths??
  • Index(es):
    • Date
    • Thread