Yes, we'd love to provide this functionality... but it is far from simple. With PPDs often containing proprietary commands and syntax, it would be next to impossible to match PPD commands specified in a PP-Design document across multiple PPDs.
For instance, the Duplex option, which one would think to be a fairly "standard" command, exists in a variety of forms in various PPDs. And I won't even get into the multiple language issues.
The only way we could ensure this would work would be by actually *preventing* end-users from using a specific PPD and instead force them to use our own, proprietary PPD (in which, of course, all known commadns would always be consistent and understood by our applications).
Then, we would have to provide end-users with a tool to map the equivalent commands from all their PPDs (granted, many of those could be *guessed* correctly by the tool, but still, it would involve a bit of work).
Oh... and this would make all previously created templates incompatible...
So... I'm afraid this one is not going to be implemented in the near future.
Sorry!
_________________________
Technical Product Manager
I don't want to achieve immortality through my work; I want to achieve immortality through not dying - Woody Allen