I am unable to find the answer in the documentation. Could you please explain the differences between wPDF300A.dll and wPDF300W.dll. Ansi vs. Unicode? When do we use it?
What is the purpose of wPDF300W.dll?
-
-
- Offizieller Beitrag
Hi,
The "W" DLL has been compiled with Delphi 2010 - unfortunately this makes it quite a bit bigger. Functionwise thats the only difference. It supports unicode file names for the property Filename. The other version which was compiled with Delphi 2006, will not use unicode file names.
If you use Delphi 2009/2010 and depend on unicode filenames, please assign "wPDF300W.DLL" to the property DLLName before the DLL is loaded.
Julian
-
Unfortunately, this is not the only difference. I guess the other problem might come from the other change - TWPDFFieldDef.Mode "add 256 for UTF-8". Application compiled with D2010 previously using wPDF300A.DLL now requires wPDF300W.DLL.
If I give to an existing build of the application a new wPDF300A.DLL the PDF will be created - but using the wrong filename (there are no Unicode chars in filename!) and all the PDF header properties are empty.
It looks like you have broken the backwards compatibility of wPDF300A.DLL for Delphi executables compiled with the D2010.
-
- Offizieller Beitrag
Hi,
You are right- The problem is - the new wPDF300A.DLL exports the method WPPDF_SetSPropW which it should not.
You can change the check for this method in WPPDFR1.pas to solve thjis problem.
Julian