Unicode characters from PDF import

Bug #956282 reported by Martijn
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Fix Released
Medium
Unassigned

Bug Description

When importing a PDF that has unicode characters in it (Japanese in my case) the non-ANSI characters are all omitted. Any ANSI-characters do show up, and any non-ANSI characters are replaced by nothing (not even a space or a "unknown characater" character). The import looks fine in Illustrator CS5. All options left at their default values.

Inkscape 0.48.2 r9819
Windows 7 Utimate x64 SP1
Language = US English
Locale = Dutch/Netherlands

Examples are attached.

Related branches

Revision history for this message
Martijn (m3rtijn) wrote :
Revision history for this message
Martijn (m3rtijn) wrote :
Revision history for this message
Martijn (m3rtijn) wrote :
Revision history for this message
Martijn (m3rtijn) wrote :
description: updated
Revision history for this message
jazzynico (jazzynico) wrote :

Confirmed on Windows XP, Inkscape trunk revision 11098 and 0.48.3.1.

Inkscape shows the following console messages (repeated several times):
Error (68994): No font in show
Error: Unknown font tag 'C0_8'
Error (42705): No font in show/space
Error: Unknown font tag 'C0_0'
...

With the trunk version, Inkscape also crashes when closing.

tags: added: importing pdf text
Changed in inkscape:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
su_v (suv-lp) wrote :

Testing on OS X 10.7.5:
- reproduced with the official stable package 0.48.2 (same console messages),
- not reproduced with local builds (stable 0.48.2 and later, trunk)
- not reproduced with new (experimental) application bundles based on the 'osxmenu' branch.

On OS X, the problem turned out to be missing poppler encoding data files [1]:
1) they are not included in the (dated) application bundle; and
2) if included, they need to be made known to the (relocatable) inkscape binary.

With Windows builds, possibly poppler-data is outdated, or not found by the inkscape binary (could be that full relocation support for poppler on Windows was added in a later version than the one included in the stable devlibs (poppler 0.12.1).

Fix used for a relocatable application bundle (WIP) on OS X in rev 12635-12638:
<http://bazaar.launchpad.net/~suv-lp/inkscape/osxmenu/changes/12638>

--
[1] see 'poppler-data' tarballs from <http://poppler.freedesktop.org/>

tags: added: packaging
Changed in inkscape:
status: Confirmed → Triaged
Revision history for this message
su_v (suv-lp) wrote :

Bitmap export rendered with Inkscape 0.48.4 attached.

Revision history for this message
su_v (suv-lp) wrote :

Bitmap export from PDF file attached in duplicate report #1264793, rendered with Inkscape 0.48.4 on OS X 10.7.5 (local build with up-to-date poppler-data files).

Revision history for this message
su_v (suv-lp) wrote :

Fix for OS X packaging committed in r13620.

Not closing - status with current Windows packages is unkown.

Revision history for this message
Nathan Lee (nathan.lee) wrote :

Closing because it's fixed in 0.92 and later in Windows and Linux (and already been confirmed fixed in OS X)

Confirmed fixed in 0.92.0 r15299, 0.92.1 r15371, 1.0.1 (3bc2e813f5, 2020-09-07) Windows 10, 1.1-dev (ad8effaa6e, 2020-11-17) Linux Mint 20

Confirmed 0.48.2-1, 0.48.5-1, 0.91-1 (Windows 10) has described bug, so calling this fixed

Closed by: https://gitlab.com/nathanal

Changed in inkscape:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.