• 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: Using non-ASCII chars to access servers
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using non-ASCII chars to access servers


  • Subject: Re: Using non-ASCII chars to access servers
  • From: Magnus Strand <email@hidden>
  • Date: Mon, 18 Apr 2005 15:50:30 +0200

Hi Quinn and Horst,

My customer is using Mac OS 10.3.8 and will connect to a PC or Mac fileserver.
I am testing with Mac OS 10.3.8 against Windows XP (SMB-share).


A folder in the path contains an a-umlaut.
I tried with both char code 0x8a (MacRoman) and 0xe4 (Win-1252),
but neither did work!
The code works if the path contains ASCII-chars only.

I am using this API:
OSStatus FSPathMakeRef (
  const UInt8 * path,
  FSRef <http://developer.apple.com/documentation/Carbon/Reference/File_Manager/file_manager/chapter_1.5_section_38.html#//apple_ref/doc/c_ref/FSRef> * ref,
  Boolean * isDirectory
);

Does FSPathMakeRef perhaps take UTF-8?

Regards,
Magnus



Horst Hoesel wrote:


Am 18.04.2005 um 14:14 schrieb Quinn:

At 13:49 +0200 18/4/05, Magnus Strand wrote:

I would like to use non-ASCII chars (e.g. MacRoman) in a a constant string path to access file servers
But this didn't work against my PC (SMB-share).


You're going to have to provide a lot more detail for us to be able to help out. Where do these characters emanate? What sort of APIs are you using to access the server? What does the overall data flow look like? What constraints do you have about your product (Mac OS X-only?, and what version?)?

S+E
--
Quinn "The Eskimo!"                    <http://www.apple.com/developer/>
Apple Developer Technical Support * Networking, Communications, Hardware

Hi Magnus,

a shoot in the dark, despite Quinn's very valid points.

Could it be as simple as different character encodings? The glyph for, say a-umlaut, uses a different code on Mac OS (in Mac Roman that would be 0xae IIRC) and Windows (assuming Windows CP1252 this would be 0xc4).

HTH,
Horst



--
*Magnus Strand *
Systemutvecklare | System Developer, MSc

*Teknik i Media* | Södra Förstadsgatan 2 | 211 43 Malmö | Tel +46 40 601 57 00 | Fax +46 40 601 57 99
Direkt +46 40 601 57 16 | Mobil +46 704 20 57 16 | email@hidden | www.tim.se


/This message contains information that may be privileged or confidential and is the property of Teknik i Media. / /It is intended only for the person to whom it is addressed. If you receive this message in error, please notify the sender immediately and delete all copies of this message. /

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


References: 
 >Using non-ASCII chars to access servers (From: Magnus Strand <email@hidden>)
 >Re: Using non-ASCII chars to access servers (From: Quinn <email@hidden>)
 >Re: Using non-ASCII chars to access servers (From: Horst Hoesel <email@hidden>)

  • Prev by Date: Re: Using non-ASCII chars to access servers
  • Next by Date: Re: ioctl always returns 0
  • Previous by thread: Re: Using non-ASCII chars to access servers
  • Next by thread: Solved: Using non-ASCII chars to access servers
  • Index(es):
    • Date
    • Thread