v 2.0.0 EUR sign (€) is not working

[kle-dev]

hello everyone,
since v. 2.0.0 the EUR sign is not working anymore...

I did a sandbox: Please open the browser of the sandbox in a new window to see the PDF rendered.

and here the working version with 1.5.3:

Thanks

[HackbrettXXX]

Neither of the examples works on my end. Both show an empty PDF.

[kle-dev]

I dont know why, but it is working ... on chrome and safari, as well as firefox... as i said: Open it in a new Window -> Click for that the icon in the Sandbox on the Sandbox Browser for Open in a New Window

[HackbrettXXX]

Ah, yes. Didn't read carefully. Sorry about that. This seems to be a bug, indeed. The € sign is part of the "Latin" character set (see PDF specification, page 653 )and should therefore work without adding a custom font.

[amadese]

Dear @HackbrettXXX ,

I obtain exactly the same issue since I'm using dist/jspdf.umd.js with special characters as € or ≥ (issue #2832 )

[HackbrettXXX]

I just digged a little deeper... it seems like jsPDF@2.0.0 is correct and 1.5.3 did some kind of "compatibility" replacements. You are probably using the Unicode 8370 "€" character, which is not in the Latin character range. You should use the 128 "€" character instead or include a font that supports the 8370 character.

@amadese you are probably facing a similar issue.

[kakugiki]

@HackbrettXXX I had a similar issue months ago, can you tell me where the code of "compatibility" replacements is?

[HackbrettXXX]

I haven't found it, yet. That's just what I assume. But I'm pretty sure without some kind of replacement characters outside the Latin range can't work.

[nicolastoulemont]

Hi,

I am having some similar issue with the upgrade from 1.5.3 to v2.

The handling of copy paste content from word documents has had a significant regression (removal of all characters after the unhandled one).

Any clues how to handle it ? Using a custom font didn't resolve the issue.

[amadese]

Hi experts,

The issue with special characters is still present in the new release. Using a custom font didn't resolve the issue.
Nobody has found a solution about that ?

[HackbrettXXX]

@amadese AFAIK no. I would be very happy, though, if someone from the community could investigate this :)

[github-actions]

This issue is stale because it has been open 90 days with no activity. It will be closed soon. Please comment/reopen if this issue is still relevant.

[amadese]

Could you tell me please if somebody has found a solution about this issue ?
Thank you in advance

[HackbrettXXX]

@amadese did you try with the 2.3.0 release? We fixed something there that might have resolved this issue: #3062.

[github-actions]

This issue is stale because it has been open 90 days with no activity. It will be closed soon. Please comment/reopen if this issue is still relevant.