Skip to content

fix(cmap): accept metadata keys without leading slash in ToUnicode CMaps#475

Closed
abimaelmartell wants to merge 1 commit intoJ-F-Liu:mainfrom
abimaelmartell:firecrawl/fix-cmap-optional-slash
Closed

fix(cmap): accept metadata keys without leading slash in ToUnicode CMaps#475
abimaelmartell wants to merge 1 commit intoJ-F-Liu:mainfrom
abimaelmartell:firecrawl/fix-cmap-optional-slash

Conversation

@abimaelmartell
Copy link
Copy Markdown
Contributor

Summary

Some PDFs (e.g. EPEVER datasheets) emit CIDSystemInfo, CMapName, and CMapType without the leading / in their ToUnicode CMap streams. The parser previously required the slash, causing these CMaps to fail parsing entirely and producing garbled text for Identity-H CID fonts.

Updated CMap parser to accept CIDSystemInfo, CMapName, and CMapType with or without the leading / slash in ToUnicode CMap streams.

Thanks!

@abimaelmartell
Copy link
Copy Markdown
Contributor Author

This was not a right approach, sorry.

@abimaelmartell abimaelmartell deleted the firecrawl/fix-cmap-optional-slash branch March 7, 2026 08:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant