I see what you are saying about utf-8. I put in a
cfprocessingdirective tag in order to use utf-8 encoding, but it
makes no apparent difference. I also tried using other canonical
values (MS936, x-mswin-936, etc.) for Simplified Chinese that I
found in a Java spec on the Sun website – still not
difference. Well that’s not strictly true: when I used Cp935,
it turned everything to Chinese characters.
After working with the utr-8 and doing some other analysis we
discovered the questions marks in the code were not being cause by
unprintable characters, but they we actually in the data. OOOOPs.
This is a whole new ballgame. At first we though that the
servers running CF8 must be missing some font that was needed on
the server side. We brought over all of the fonts that seemed to be
associated with Simplified Chinese, but that didn’t make any
difference. I one final act of desperation, we changed the format
on the cfdocument from PDF to SWF. All of the Chinese characters
appeared in the SWF output file. All of the Chinese characters also
appear in the HTML output that is generated at the same time that
the PDF/SWF files are created. I call the code that creates the
actual report twice from within a shell: once inside the cfdoument
with a file name to create a separate file, and once that is not
within it to create a HTML presentaion.
The same code, when run on a CF7 server, produces a PDF
output with all of the Chinese characters. One last thing, we are
using CF8 on two different servers: one running W2KS and the other
with W2003S.
The only thing I can conclude from all of this is that there
is either something wrong with the CF8 setup on both servers, or
there is something wrong with CF8 itself.
I'm also in the middle of a severe Verity problem that I'm
working on with Adobe. The K2Server.exe process will crash (process
grows from about 15k to over 700,000k) after doing some number of
Verity collection creations or in the indexing. I've sent them code
that will create this problem time after time. They are still
scratching their collective heads over this one. I see it as a
classic case of memory leakage. They haven't agreed with me yet.
Having said all that, it seems entirely possible that there is some
undiscovered problem with cfdocument and PDF file creation using
CF8 as well.
:-}
Len