Merge algorithm is broken

Open
  • Is something wrong?
#150 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
backend

Research direction

Start by reading pdffont.js and tracing how .x and .width are produced and compared during text-stream recombination. Confirm which values use each coordinate system and identify the source of the width adjustments; done means bounding-box comparisons recombine the text stream correctly without inconsistent coordinates.

Written by the indexing model from the issue text.

Description

Re-Combining of the text stream does not work as

  • .x and .width are in different coordinate systems pdffont.js
  • width has some added magic number and additions
  • and the modified coordinates are assumed in the same coordinate system for bounding box comparison
Dominant language
Java
Stars
2.2k
Forks
396
Avg merge
9d 19h
Merged PRs (30d)
3

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from modesty/pdf2json

All issues in modesty/pdf2json

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.