The indent trigger was using .abs() which fired on both increased indent (non-indented → indented) AND decreased indent (indented → non-indented). This caused drop-cap style paragraphs (indented first line, flush-left continuation) to incorrectly split into two blocks. Per plan Phase 4.4 heuristic #2, indent change should only trigger when the current line is MORE indented (to the right, larger x0) than the block average - i.e., a new paragraph starting after non-indented text. It should NOT trigger for decreased indent (first line indented, rest flush-left). Fix: Remove .abs() and only check if line_x0 - block_avg_x0 > threshold. Tests: - test_indented_first_line_new_block: PASS (non-indented → indented splits) - test_indented_first_line_of_paragraph_not_split: PASS (drop cap stays together) - All 179 line module tests: PASS
17 lines
665 B
Rust
17 lines
665 B
Rust
#[test]
|
|
fn debug_content_edit_pages() {
|
|
use pdftract_core::document::parse_pdf_file;
|
|
|
|
let v1_path = "tests/fingerprint/fixtures/content_edit_one_glyph/v1.pdf";
|
|
let v2_path = "tests/fingerprint/fixtures/content_edit_one_glyph/v2.pdf";
|
|
|
|
println!("Checking v1: {}", v1_path);
|
|
let (_fp1, _cat1, pages1, _resolver1) = parse_pdf_file(std::path::Path::new(v1_path)).unwrap();
|
|
println!("v1 pages: {}", pages1.len());
|
|
|
|
println!("Checking v2: {}", v2_path);
|
|
let (_fp2, _cat2, pages2, _resolver2) = parse_pdf_file(std::path::Path::new(v2_path)).unwrap();
|
|
println!("v2 pages: {}", pages2.len());
|
|
|
|
panic!("Debug info printed");
|
|
}
|