Re: Are all strings passed to preflight/postflight scripts as ascii or unicode?
Re: Are all strings passed to preflight/postflight scripts as ascii or unicode?
- Subject: Re: Are all strings passed to preflight/postflight scripts as ascii or unicode?
- From: Iceberg-Dev <email@hidden>
- Date: Fri, 26 Feb 2010 12:00:56 +0100
On Feb 26, 2010, at 4:37 AM, Chris Kritzer wrote:
I have a bug where “special characters” in a user-selected folder
named !"§$%&/()=? are being passed to the postflight script
(written in perl). The installer log shows the text being passed
correctly (except for the forward slash, which it translates to a
colon), but the script has all sorts of issues parsing the string.
'/' is the only (AFAIK) forbidden character for a path component.
So it's really a ':'.
Does PackageMaker pass the string as escaped text or does it pass
it as Unicode?
The installation framework being a Cocoa thing, it's quite probable C
strings passed to scripts as arguments or env vars are built using
UTF8String or fileSystemRepresentation. Both are usually the same,
but apparently sometimes there can be a difference.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden