Excessive use of HTML in Output

#33
by abimaelmartell - opened

Hi! First off, really nice work on LightOnOCR 2, the extraction quality has been great in my testing and it beats a lot of models on speed.

I saw the reasoning for using HTML on tables here

That totally makes sense for things like nested tables.

But I’ve noticed the model often outputs a lot of layout/styling HTML, like div blocks with text-align, font-size, flex layouts, margins, etc.

Example:

<div style="text-align: center;">
  ![image](image_1.png)
  <br />
  <em>Power in Partnership</em>
</div>

For my use case (feeding the output into LLMs for RAG / analysis), this ends up wasting tokens and adding noise, since most of that styling doesn’t carry useful meaning.

Not a huge issue since it can be post-processed, but figured I’d share the feedback since the model is otherwise working really well.

Not a huge issue since it can be post-processed
Daisy chain this bad-boy to another model and get them real (non-html) outputs.

For real though, this OCR is more durable than the SOTAs on edge cases and I do this exact daisy chaining because of that

Sign up or log in to comment