Support configurable inter-word spacing limits during justified line breaking
まだ誰も着手していません。
評価
調査の方向性
Start with BidiLine.processLine() and PdfDocument.writeLineToContent(), the two entry points named in the issue. Trace how candidate breakpoints and remaining width determine word spacing, then check the existing line breaking tests. Done means an opt-in policy selects legal breaks within the configured spacing limits while preserving default behavior and natural spacing on the last paragraph line.
索引モデルが issue の本文から書いたものです。
説明
Is your feature request related to a problem? Please describe.
When rendering justified, hyphenated paragraphs, OpenPDF chooses line breaks using text at its natural width. Once the line has been broken, the remaining width is distributed during justification.
This allows inter-word spacing to be increased, but the line-breaking algorithm does not consider placing an additional word on the line by reducing inter-word spacing.
For example, suppose two possible breaks produce:
- A hyphenated line requiring 130% inter-word spacing
- A line containing the complete next word requiring 90% inter-word spacing
The second result is typographically closer to the natural 100% spacing, but OpenPDF currently selects the first because the complete word does not fit at its natural width.
PDF supports negative word-spacing adjustments through the Tw operator, so the output format can represent the desired result. The limitation appears to be in line breaking, particularly BidiLine.processLine().
Describe the solution you'd like
Provide an optional justified line-breaking policy with configurable inter-word spacing limits, for example:
columnText.setMinimumWordSpacingRatio(0.70f);
columnText.setMaximumWordSpacingRatio(1.35f);
columnText.setPreferredWordSpacingRatio(1.00f);
For each line, the line breaker would evaluate legal breakpoints at:
- Word boundaries
- Available hyphenation points
For each candidate, it would calculate the inter-word spacing required to fill the line:
required spacing ratio = (available line width - glyph width) / natural space width
Candidates outside the configured minimum and maximum would be rejected. Among the remaining candidates, OpenPDF would select the one closest to the preferred ratio. A hyphenation penalty could optionally be applied so that otherwise similar candidates prefer an unhyphenated break. The last line of a paragraph would continue to use natural spacing, as it does currently. This should be opt-in, preserving the existing line-breaking behavior by default.
Describe alternatives you've considered
The alternatives appear to be:
- Forking OpenPDF and modifying BidiLine.
- Performing paragraph layout externally and drawing every line directly through PdfContentByte.
External layout would duplicate much of OpenPDF's handling of mixed fonts, inline formatting, bidirectional text, links, superscripts, hyphenation, and page/column transitions. A configurable implementation within OpenPDF's line breaker seems more reusable.
Your real name
Ioannis Rigopoulos
Additional context
The relevant behavior can be seen in:
- BidiLine.processLine(), which stops scanning when the next character exceeds the available natural width
- PdfDocument.writeLineToContent(), which calculates the final word and character spacing
The rendering stage already appears capable of emitting negative word spacing if a PdfLine has negative remaining width. The main change may therefore be to retain and score candidate breakpoints beyond the natural line width.
One possible initial implementation would compare:
- The existing word/hyphen break before overflow
- Hyphenation candidates
- The next complete-word boundary, if it fits within the configured minimum spacing
A paragraph-wide optimization could be considered later, but even a line-by-line candidate comparison would improve the current result considerably.
Example requirement:
- Minimum inter-word spacing: 70%
- Maximum inter-word spacing: 135%
- Preferred inter-word spacing: 100%
- Hyphenation enabled
- 主要言語
- Java
- スター
- 4.4k
- フォーク
- 714
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
LibrePDF/OpenPDF のほかの issue
-
bug
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
-
IndexOutOfBoundsException in PdfReader対応中かも @andreasrosdalw が 95 日前に担当しました。 オープンbug
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
-
`PdfSmartCopy` can take effectively unbounded time on nested shared Form XObjects対応中かも このイシューにリンクされたプルリクエストがオープン中、またはマージ済みです。 オープンbug
難易度 4/5 3〜5日 初心者へのやさしさ 48/100
-
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
-
難易度 4/5 1〜2日 初心者へのやさしさ 45/100
LibrePDF/OpenPDF の issue をすべて見る
似ている issue
-
[BUG] micronaut-serde-oracle-jdbc-json brings a second OJDBC driver onto the runtime classpath対応中かも @ZARAYACH が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
micronaut-projects/micronaut-serialization#1494 · コメント 4 件 ·
メンテナーはふだん 2 日以内に返信
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 73/100
メンテナーはふだん 2 日以内に返信
-
code-health feature/sync OS/Android QA/Test-Plan-Specified QA/Yes
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
brave/brave-browser#60327 ·
メンテナーはふだん 1 日以内に返信
-
Type: Bug
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
it-at-m/raumreservierung#383 ·
メンテナーはふだん 3 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
aws/context-ontology-accelerator#325 ·
メンテナーはふだん 1 日以内に返信