Re: .string bug -- filed apple bug
Re: .string bug -- filed apple bug
- Subject: Re: .string bug -- filed apple bug
- From: Christopher Ryan <email@hidden>
- Date: Thu, 2 Jun 2005 06:41:18 -0700
Andy,
The behavior you are seeing is caused by Tiger's parser becoming more
strict on invalid .strings files.
In a .strings file every key-value pair needs to end in a semicolon.
In your package, the last line does not end in a semicolon, so on
Tiger, the strings are not found.
Chris
Mac OS X Installation & Setup
There seems to be a frustrating bug with Tiger's package installer
that I
filed in Apple's bug reporter a few days ago. Folks here that use
PackageMaker with custom InstallationCheck.strings and
VolumeCheck.string
will want to know of it... If anyone has any workarounds or further
knowledge of this, that'd be great. Here's a paste of it:
Problem ID: 4133872
Title: Package .string messages fail to show under Tiger
Summary:
Packages that properly display the messages contained in
VolumeCheck.strings
and InstallationCheck.strings under 10.3, do not display properly
under 10.4
(instead, the default "Could not find specified message for index
X" is
displayed).
Steps to Repro:
Run any package that uses VolumeCheck.strings and
InstallationCheck.strings,
built via PackageMaker 1.x or 2.x, built under 10.3 or 10.4, and
you'll
always get the "could not find specified message for index X"
message. I
stress: a package under 10.3 will show string messages properly
while the
*same* package will not find the string under 10.4. I've tried every
permutation of semi-colons, spaces, and new lines in those string
files that
I can think of, without any luck. Even if there was a format
problem I
didn't think of, you probably agree that Apple should propagate any
package
installer behavior of this nature from 10.3 to 10.4 (recall that I
mentioned
that the same package works on 10.3 but doesn't under 10.4).
Expected Results:
Same as under 10.3: the strings in *.strings properly display.
Actual Results:
Both the strings from VolumeCheck.strings and
InstallationCheck.strings are
never found.
Regression:
The fact the same package works under 10.3 and doesn't under 10.4
indicates
there's a bug in the 10.4 package installer.
Andy
_______________________________________________
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