>Hi all,
>
>A short question concerning the STRCONV function and the UNICODE mentioned throughout the VFP9 help file UTF-16?
>
>Why am I looking for this? The new version of quickpdf nows requires feeding the beast with UTF-16 strings. I do not want to bump into a complex issue before considering an update.
>
>Thanks for any input:)


Depends on how you feed the beast

(1) If you can pass a 'normal' string - my understanding is that the string will be converted to UTF-16 for you, ie from codepage cpcurrent(1) to UTF-16

(2) If you have to explicitly pass UTF16

(a) if you stay within cpcurrent() - you can use strconv() I believe

(b) otherwise you can use StringToUTF16(@utf16Out, stringIn, codepageIn) where you can specify a codepage
You'll find the function in message#1523724