Actually, another app is feeding the path to my program, so the path will
be in Mac OS X format. So, it might have : in the path. The data is given
to my app in an app-specific format which is easily changed to a char*.
After that I have had a difficult time getting very far ;-)
Thanks!
James Berry
<[EMAIL PROTECTED]> To: Xerces C Dev <[EMAIL
PROTECTED]>, <[EMAIL PROTECTED]>
cc:
07/31/2003 07:19 Subject: Re: Mac OS X paths
PM
Please respond to
xerces-c-dev
On 7/31/03 2:47 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>
> First of all, I will admit that I am a total newbie to the Mac. That
being
> said, does anybody have any examples of loading files with Xerces on Mac
OS
> X. I know about XMLCreateFullPathFromFSRef and XMLParsePathToFSRef, but
I
> am having trouble getting what I want out of them. I am not terribly
> familiar with FSRef's (which is my problem). For instance, in the
DOMPrint
> example we get the char* path from the command line argument, but I can't
> seem to convert it to a Unix style path to load it.
>
> Any samples or advice would be much appreciated!
>
> Thanks!
Hi Elliot,
If you're already starting out with a unix pathname (such as you specify on
the Mac OS X command line) then you can just feed that on into Xerces, just
as DOMPrint does. You should in fact be able to run the DOMPrint
application
and specify a file path from the command line. Does that work for you?
The utilities you mention above are used internally by Xerces to convert
back and forth from paths to FSSpecs and FSRefs. They may also be useful
within programs that use Xerces, in order to convert between those forms.
James
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
