- Rating
- 3(+1)
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2(+1)
- Soundness
- 2
Read review
Paper summary
This paper proposes TeXForm, a LaTeX normalization method based on a command knowledge base and syntax-tree rewriting. It aims to preserve formula content while unifying equivalent representations, substantially reducing false rejects of render-equivalent formula pairs on selected benchmarks.
Critical strengths
- Thorough evaluation across multiple datasets and benchmarks, including ablations, cross-renderer validation, and sensitivity analyses.
- Strong normalization results, combining high rendering safety with substantial canonicalization and reducing false rejects on UniMER-Test and OmniDocBench.
Critical weaknesses
- TeXForm follows the established parse–rewrite–serialize pipeline. Its engineering contribution is substantial, but its methodological novelty is limited.
- Safety and canonicity are reported separately, so it is unclear how many successfully normalized pairs also retain their original rendering.
Questions for authors
- Could the authors report, among render-equivalent formula pairs normalized to the same LaTeX string, how often the shared output renders differently from the original formulas? This would help clarify how much of the merging preserves the original rendering.
3 comments
Response to Reviewer 99Jz (2/2): Direct Answer to the Question and Presentation Revisions
Question 1: Among render-equivalent pairs normalized to the same string, how often does the shared output render differently from the originals?
Rarely for TeXForm: only 0.91% of the pairs TeXForm (Faithful) folds (1.32% for Corpus), against 75.09% for MathNet and 20–22% for CDM. See Weakness 2 above for the full audit over all 29,528 equivalent pairs and the new safe pair canonicity column in Table 1.
Presentation (Score 1): Revisions to Improve Clarity
Taking your presentation feedback seriously, we used the extra discussion-period page to expand the main text and spell out parts that had been overly compressed (all changes marked in blue; full list in our general comment). We reworked the presentation of Tables 1 and 2 in Sections 6.2 and 6.4. In Section 5, we added a dedicated Normalization profiles paragraph and expanded the Parsing and Transforming descriptions, and in Section 6.1 we added an upfront Supports and rates paragraph.
We hope these new results and manuscript revisions address your concerns. If any passage still feels dense, please let us know so we can refine it further. We would also appreciate your reconsideration in light of these revisions.
Follow-up to Reviewer 99Jz
Dear Reviewer 99Jz,
Thank you again for your review. With about one day left in the discussion period, we would like to check whether our response and revision resolve your concerns. Below is a brief summary of our answer to each of your points, the first two of which directly shaped revisions to the main text.
Joint evaluation of safety and canonicity. Following your question, Table 1 now has a new column, safe pair canonicity, which counts a pair only when the shared output renders like both original formulas (defined in Section 6.1, discussed in Section 6.2). It tests both conditions of Proposition 1 on the same pairs. To answer your question directly, TeXForm (Faithful) changes the rendering of only 0.91% of the pairs it normalizes to the same string, against 75.09% for MathNet (new Appendix C.8).
Presentation. We used the extra page to rewrite the parts of the main text that were too compressed. Section 5 now describes the four profiles and walks through the three stages with the example in Figure 2, Section 6.1 introduces the evaluation data and each rate before the results, and Tables 1 and 2 have a simpler layout. All changes are marked in blue.
Methodological novelty. We agree that the parse–rewrite–serialize pipeline itself is standard. Our contributions are the definition of LaTeX normalization as a task with four measurable properties (Section 4), the audit of deployed normalizers, datasets, and benchmarks that this definition makes possible (Sections 3 and 6), and the command knowledge base that drives TeXForm (Section 5). The repaired normalizers we built for Reviewer WZKC also show that this command knowledge, rather than the pipeline, accounts for most of TeXForm's gain.
We would appreciate knowing whether these changes resolve your concerns, and whether the revised sections read more clearly. If so, we would be grateful if your final assessment could reflect this.
Best regards,
The Authors
Response to Reviewer 99Jz (1/2): Novelty and Joint Safety–Canonicity Audit
Thank you for your thorough review, for highlighting the gap between the separate safety and canonicity evaluations in Table 1, and for your candid feedback on presentation.
Following your suggestion to evaluate safety and canonicity jointly, we added a safe pair canonicity column to Table 1. It measures the share of equivalent pairs folded without changing the rendering. We placed it in the main table because it directly tests both conditions of Proposition 1 (Section 4).
Weakness 1: Novelty Beyond the Parse-Rewrite-Serialize Pipeline
We agree that the parse-rewrite-serialize pipeline itself is standard. Our contribution is to turn an ad-hoc preprocessing step into a formally specified, auditable component of the ML pipeline. In fact, existing normalizers (im2markup, MathNet, CDM) do not even rewrite a well-formed AST, instead pairing a lossy KaTeX pass with structure-blind regex or token substitutions (Section 3). We go beyond that pipeline in three ways:
The repaired baselines built for Reviewer WZKC isolate this third point. They keep the same parse-serialize skeleton and fix all nine documented defects in im2markup and MathNet without adding any command knowledge, and they reach at most 17.45% safe pair canonicity, against 37.15% for TeXForm (Faithful) (new Appendices C.7–C.8). Since both sides share the skeleton, the gap comes from the knowledge base and contracts.
Weakness 2: Joint Evaluation of Safety and Canonicity
For TeXForm (Faithful), only 0.91% of folded pairs render differently from the original formulas (1.32% for Corpus and 0.81% for Authoring). By contrast, MathNet changes the rendering of 75.09% of the pairs it folds, and CDM changes 20–22% of theirs.
Your concern points to a real gap in how we originally reported the two properties. Proposition 1 makes normalized matching a valid test of rendering equivalence only when safety and canonicity hold on the same inputs, yet Table 1 measured safety on raw labels and canonicity on model-prediction pairs. Measured apart, the two rates cannot separate folding that comes from knowing equivalent forms from folding that changes the rendering. For example, a normalizer that maps every formula to one fixed string folds every pair (100% pair canonicity) while preserving no rendering.
Following your suggestion, we ran a new audit across all 29,528 equivalent pairs (new Appendix C.8, Table 15). For each folded pair (x,y) with shared output z, we check z≡x and z≡y, which is exactly safety on both members, so safe pair canonicity counts the pairs on which both premises of Proposition 1 hold at once:
Once rendering-altering folds are excluded, no prior normalizer reaches 20% safe pair canonicity, which resolves the apparent trade-off with MathNet, since three quarters of its folds change the rendering. Table 1 now reports safe pair canonicity next to pair canonicity, and Appendix C.8 gives the full 12-row comparison.
Even in the ~1% of folded pairs with a pixel difference, TeXForm usually only shifts glyph positions while preserving MathML structure (e.g.,
(5^{\prime\prime})vs.( 5'' )).This joint criterion also shows the first point of Weakness 1 at work. Because the four properties are defined formally, the criterion follows directly from Proposition 1 instead of being chosen ad hoc, and it turns the apparent safety–canonicity trade-off among prior tools (Figure 3) into a measurable gap between pattern-based normalizers and TeXForm.