Interesting - I would have thought this would work - but obviously not. I've get a small UTF8 test string in my example table ( http://datatables.net/release-datatables/extras/TableTools/index.html ) which seems to work okay with PDF export. Can you link us to your page which isn't working please, so I can try a few characters?
the demo is really working with utf-8.
my table is in closed section for registered users only so it will be alittle problem.
what i can give you is a couple of hebrew string
data = ????
table = ????
forum = ?????
encoding = ?????
try these words in the code and see if it will be in the exported utf-8
i modified the tabletool.js so it will use window.print() and then close the print preview back to the original
Could you possibly send me your data using this form: http://datatables.net/contact . It will almost certainly be something to do with the AlivePDF library that is used for generate the PDF files (for example a quick search gives this http://code.google.com/p/alivepdf/issues/detail?id=58 ).
Just looking a bit more and it looks like it is a limitation in the AlivePDF library that is being used for TableTools at the moment, but it is being worked on by the AlivePDF folks. They've released an RC of v1.5 which has support for font embedding, and the ability to support unicode fonts / characters. From the post announcing the RC ( http://alivepdf.bytearray.org/?p=440 ) it doesn't sound like it is quite ready unicode use just yet - but hopefully coming soon. When v1.5 is released I'll include it in TableTools. You could possibly send a note of support to the AlivePDF developers, saying there is interest in their project from this quarter as well :-)
TableTools is currently using the 0.1.5 RC from the AlivePDF project (which was released in Feb 2010 - so the project might be having a bit of a pause just now). There is a Unicode class, but I didn't have much success when using it before.
One option might be to use the newer PurePDF library which does handle Unicode (with the correct font of course) but it makes the swf size massive (700K+) which is bonkers for a little SWF like TableTools.
I suspect the real answer is to look into the AlivePDF code and figure out what is going on, but I thank that will take rather a lot of work.
Replies
Allan
my table is in closed section for registered users only so it will be alittle problem.
what i can give you is a couple of hebrew string
data = ????
table = ????
forum = ?????
encoding = ?????
try these words in the code and see if it will be in the exported utf-8
i modified the tabletool.js so it will use window.print() and then close the print preview back to the original
do you think it will be fixable without my data?
Allan
Allan
i have sent you a message trou the contact form... can you contact me by mail i have something to send you
Allan
Any progress on this issue?
How can i include the RC version of alive PDF for UTF support and test it in this project?
One option might be to use the newer PurePDF library which does handle Unicode (with the correct font of course) but it makes the swf size massive (700K+) which is bonkers for a little SWF like TableTools.
I suspect the real answer is to look into the AlivePDF code and figure out what is going on, but I thank that will take rather a lot of work.
Allan
what are the chances to introduce SWF using PurePDF for those of us who are willing to implement it.
Thanks,
-Nicky