DP_AspectRatio
Incorrectly set to 1 for locales that don't use a decimal point as decimal separator.
More precisely, the picklist for aspect ratios always uses a decimal point, regardless of locale. Only if the user manually enters the aspect ratio according to his locale, DP_AspectRatio works.

DP_ProductionYearsDiffer
This does not indicate a changed Country of Origin and there is no other DP_*Differ variable that would do that.

DP_BoxsetContentsDiffer, DP_ScansDiffer
These are missing from the DP_*Differ variables.

DP_LockMediaType
This is missing from the DP_Lock* variables.

Quote chars not escaped
Quote chars are not escaped in the following fields:

DP_Studios

DP_Disc.location

DP_Disc.slot

Other missing data

Boxset Contents

Currency code and type for SRP and purchase price

Loan Due (there is only DP_LoanedTo

Strings used instead of booleans
For all boolean object fields except DP_*Entry.hasImage the strings "true" and "false" are used instead of boolean values.

DP_CastEntry.voice

DP_CastEntry.uncredited

DP_Disc.dualLayeredSideA

DP_Disc.dualLayeredSideB

This is nice, if I knew what you are talking about??? And I don't.

Quoting pauls42:

Quote:
Quoting goodguy:

Quote:
*Bump*

Judging by the meager view count of 38 for this topic, nobody seems to really care about this. But since a new beta is probably about to appear any time soon, I want to bring this to attention once more.

My new PCP plugin makes heavy use of the HEADER_VARS, and while I was able to work around most of the problems described in my first post, the unescaped quote chars cannot be magicked away. And they are a real world problem, too. At least one user of my plugin encountered a syntax error in the HEADER_VARS and I'm pretty sure the unescaped quote chars are the reason for it.

Have you bumped this into the feature request forum as well?

Wouldn't do any harm..

Probably not, but it's a bug, not a feature. 
Besides, as annoying the lack of response sometimes is, Ken usually silently does his job, so I just assume he will read it and fix it. If it is still not resolved with the next beta, I will open a support ticket.