UTF16-encoded PDF title displays as octal-escaped byte sequence in window and tab titles

VERIFIED WORKSFORME

Status

()

Firefox
PDF Viewer
VERIFIED WORKSFORME
6 years ago
5 years ago

People

(Reporter: jfkthame, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [pdfjs-c-rendering], URL)

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
Viewing the document http://www.quivira-font.com/files/QuiviraPUA.pdf in Nightly displays the window and tab titles as "\376\377\000Q\000u\000i\000v.....", which looks like it is UTF-16BE data being treated as individual bytes.

Updated

6 years ago
OS: Mac OS X → All
Hardware: x86 → All

Comment 1

6 years ago
partly fixed - works fine on Mac, still kinda broken on Windows (window title is OK, but content is a bit scrambled)

Updated

6 years ago
Whiteboard: [pdfjs-c-rendering]
Looks good on Windows now. Marking as fixed
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
looks broken on Mac to me.  None of the symbols are displayed correctly.  They look fine in Mac Preview.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Created attachment 703936 [details]
screenshot of UTF16 test page in PDF viewer
Works on Mac OSX 10.8; Tracy's is 10.6
(In reply to Yury Delendik (:yury) from comment #5)
> Works on Mac OSX 10.8; Tracy's is 10.6

So is this fixed everywhere except for Mac OSX 10.6? If so, I'd be in favour of marking this bug resolved fixed and filing a follow-up bug to address the Mac OSX 10.6 specific breakage.
(Reporter)

Comment 7

5 years ago
This bug was about the PDF document *title* being incorrectly decoded for display in the window titlebar and tab title.

Attachment 703936 [details] shows a problem with rendering of the *document contents* on the pdf.js canvas, almost certainly due to failure to load an embedded font (there's probably a message to that effect in the Web Console), but that's a different issue.

Tracy, do the window/tab *titles* appear correctly for you ("Quivira 3.8 Private Use Area")? If so, I think we can resolve this bug as fixed.

The *content* rendering that's broken on 10.6 should be filed as a separate bug; it's an issue with font conversion/loading, whereas this was a problem with metadata encoding.
Original problem address. Content looks good in Firefox Nightly for Windows. Closing as resolved
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago5 years ago
Resolution: --- → FIXED
Yes, it's ok now on Mac too.
Status: RESOLVED → VERIFIED
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.