how to export to pdf with utf-8 for hebrew table

how to export to pdf with utf-8 for hebrew table

yonihbcyonihbc Posts: 5Questions: 0Answers: 0
edited January 2011 in TableTools
hi... my table have hebrew in it
but exporting to pdf will cause question marks - what is the solution?

i have empty or [code] [/code] in a cell, export will have undefined instead: what can be done?

Replies

  • allanallan Posts: 63,489Questions: 1Answers: 10,470 Site admin
    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?

    Allan
  • yonihbcyonihbc Posts: 5Questions: 0Answers: 0
    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
  • yonihbcyonihbc Posts: 5Questions: 0Answers: 0
    damn... this forum is not in utf-8 - i will try working on a table for you

    do you think it will be fixable without my data?
  • allanallan Posts: 63,489Questions: 1Answers: 10,470 Site admin
    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 ).

    Allan
  • allanallan Posts: 63,489Questions: 1Answers: 10,470 Site admin
    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 :-)

    Allan
  • yonihbcyonihbc Posts: 5Questions: 0Answers: 0
    ok... so i guess i will be waiting :-)

    i have sent you a message trou the contact form... can you contact me by mail i have something to send you
  • allanallan Posts: 63,489Questions: 1Answers: 10,470 Site admin
    Just done :-)

    Allan
  • canavarcanavar Posts: 1Questions: 0Answers: 0
    Hi,

    Any progress on this issue?
  • hadibuntuhadibuntu Posts: 4Questions: 0Answers: 0
    Hi
    How can i include the RC version of alive PDF for UTF support and test it in this project?
  • allanallan Posts: 63,489Questions: 1Answers: 10,470 Site admin
    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.

    Allan
  • ickataickata Posts: 1Questions: 0Answers: 0
    Hi Allan,
    what are the chances to introduce SWF using PurePDF for those of us who are willing to implement it.

    Thanks,
    -Nicky
  • hadibuntuhadibuntu Posts: 4Questions: 0Answers: 0
    Can you use purepdf (http://code.google.com/p/purepdf) instead of alivePdf
This discussion has been closed.