trouble in converting unicode template to pdf using xhtml2pdf trouble in converting unicode template to pdf using xhtml2pdf flask flask

trouble in converting unicode template to pdf using xhtml2pdf


Its partially solved. Providing the absolute path to the font i.e.

    <style>        @font-face {        font-family: Preeti;        src: url("c:/static/fonts/preeti.ttf");        }        body {        font-family: Preeti;        }    </style>  

Now another problem has raised. I have mixed texts, partially in unicode and partially in normal Font(I think I should say it normal fonts :D), since fonts have been overridden, now the normal Fonts are coming in rectangular boxes. In this case a empty box.


A little late answer but I think that it is important to know why relative paths do not work in fontface for xhtml2pdf:

The CreatePDF function (which is the same with the pisaDocument method as can be seen in https://github.com/chrisglass/xhtml2pdf/blob/master/xhtml2pdf/pisa.py) has a path named parameter. Now, if you don't set this parameter and use a relative path then it will try to find your fonts under a folder named __dummy__ as can be seen on the file https://github.com/chrisglass/xhtml2pdf/blob/master/xhtml2pdf/context.py (search for dummy).

So, that's why your .ttf files only work when you use absolute paths.

To resolve this, you can either:

  • create a __dummy__ folder and put your .ttf files there, or
  • pass a value to the path named parameter of CreatePDF

For example, in my case, I am creating PDFs through django, so I passed path='.' and put my .ttf in the same folder as my manage.py -- everything is working fine. Of a better solution would be to define SETTINGS.PROJECT_PATH and use that.


From the documentation, it looks like you're supposed to give CreatePDF an encoding, otherwise "this is guessed by the HTML5 parser".

So, say the HTML file's headers specify whatever legacy charset was used for Devanagari. You decode that properly to Unicode somewhere before the code you've shown us, then re-encode it as UTF-8, but the headers are specifying a different charset. In that case, html5lib will guess the wrong charset, and interpret the characters incorrectly and give you mojibake.

Of course I can't be sure that's exactly the problem you're facing without a complete example, but it's likely something like that. And the most likely solution is the same for any of them: If you encode to UTF-8, tell the converter to use UTF-8 instead of guessing:

pisaStatus = pisa.CreatePDF(    StringIO(sourceHtml.encode('utf-8')),                     dest=resultFile,    encoding='utf-8')