search

barryvdh / laravel-dompdf

A DOMPDF Wrapper for Laravel
MIT License
6.74k stars 972 forks source link

useOTL, useKashida dont support in DomPDF #826

Closed junayedmahmud closed 2 years ago

junayedmahmud commented 3 years ago

I am behalf from A Software Company. We are running a big project in Bangladesh. Recently we needed to add bangla font in PDF. we tried with load_font.php and with

@font-face { font-family: 'font_family'; font-style: normal; font-weight: normal; src: url(fonts/Kalpurush.ttf) format('truetype'); } body { font-family: Arial, sans-serif, 'font_family'; }

I also tried with changing config/DomPDF.php file. UseOTL ,use Kashida dont work there. So generated word is looking like this:

image

image

These words are broken. That is generated with load_font.php

Have any way to fix ?

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any issues with PDF rendering itself that are not directly related to this package, should be reported on https://github.com/dompdf/dompdf instead. When having doubts, please try to reproduce the issue with just dompdf. If you believe this is an actual issue with the latest version of laravel-dompdf, please reply to this issue so we can investigate further. Thank you for your contribution! Apologies for any delayed response on our side.

bishwajitcadhikary commented 2 years ago

@junayedmahmud Did you find the solution? image

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any issues with PDF rendering itself that are not directly related to this package, should be reported on https://github.com/dompdf/dompdf instead. When having doubts, please try to reproduce the issue with just dompdf. If you believe this is an actual issue with the latest version of laravel-dompdf, please reply to this issue so we can investigate further. Thank you for your contribution! Apologies for any delayed response on our side.