A "backdoor?" That may be how you guys at Adobe think about it, but to us users of the Acrobat SDK, it's just another "platformPathType" parameter value for ASFileSysAcquirePlatformPath, which should be documented along with POSIXPath and CString and all the other possible valid values. For that matter, why is there not a corresponding ASPlatformPathGetWinUnicodePathPtr function? Or for that matter, why is there not an ASPlatformPathGetUnicodePathPtr function that can return a Unicode (UCS-2) path on either Windows or Mac, as a string of 16-bit characters? The idea that getting the actual Unicode path that Windows uses natively should be a special "backdoor" case that's not documented seems like a deficiency in the API, or at the very least in the documentation. The fact that everyone has to keep asking the same question about it because it's not documented is the very definition of a documentation deficiency.
↧