Are all strings passed to preflight/postflight scripts as ascii or unicode?
Are all strings passed to preflight/postflight scripts as ascii or unicode?
- Subject: Are all strings passed to preflight/postflight scripts as ascii or unicode?
- From: "Chris Kritzer" <email@hidden>
- Date: Thu, 25 Feb 2010 19:37:36 -0800
- Thread-topic: Are all strings passed to preflight/postflight scripts as ascii or unicode?
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.
Does PackageMaker
pass the string as escaped text or does it pass it as Unicode? If the former,
is there a setting to tell PackageMaker to pass it as Unicode instead? If the
latter, any suggestions on how to decode it in perl?
Thanks in advance,
Kritzer
|
_______________________________________________
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