>Hi Gregory,
>
>I'm just looking for a confirmation that what is called UNICODE is the now old VFP9 documentation is exactly what is meant as UTF-16 within the new quickpdf library since the new version 8.x is now fully based on UTF-16 parameter passing.
>
>I understand that you confirm that:)
>
>Do you mean as well that, since I'm using the COM version of the library, not the dll or delphi lib I should see the com dialog takes care of the translation. The change in parameter structure (the whole lib is changing) should have no consequence for a use via COM.
>
>Am I correct?
>
>François

François,

I do not understand what I confirm
Let me repeat

(1)
In general - I'm careful here - COM objects that work internally in UTF-16 convert the strings
- vfp to COM : cpcurrent(1) to UTF-16
- COM to vfp: UTF-16 to cpcurrent(1)

Excel is an example of that

If you have to convert your strings to UTF-16 before passing them

(a) CPCONVERT is useful as long as your strings are in codepage cpcurrent

	local x
	
	x = 'œ'
	
	y = strconv(strconv(x, 1), 5)   && first to double byte, then to wide chars (wide = UTF-16)
	
	&& y = 0x0153   or chr(0x53) + chr(0x01)

(b) if the code page is different, use the function of my previous message


i do not know how to need to pass the strings to quickpdf - I can only describe the different possibilities. You'll have to to some testing