I agree with the overall direction here, although I think the issue goes a bit deeper than just EV battery reports. Acrobat has always been strong for final documents, but when it comes to living documents—things that evolve over time with updated data—it starts to show limitations. I’ve personally worked with exported reports from different systems, including vehicle diagnostics, and even small edits can feel unpredictable. It breaks the workflow, especially when you’re trying to maintain consistency across versions.
What stands out to me is the lack of structure awareness. These PDFs aren’t just text—they’re data. Tables, metrics, logs, all interconnected. When you edit one value, everything else should stay intact, but that’s not always the case. I recently came across a breakdown explaining how EV battery reports are structured and why even minor changes can affect readability and accuracy, which really highlights the gap in current editing tools. This website https://evbattery.us/ gives a good example of how these reports are actually used in practice.
So yes, I support this idea, but I’d frame it as Acrobat needing to evolve from a document editor into something that better understands structured, data-heavy content. Whether it’s EV reports or any other technical documentation, users shouldn’t have to fight the layout just to make simple updates.
Morgan Wilson supported this idea ·
I agree with the overall direction here, although I think the issue goes a bit deeper than just EV battery reports. Acrobat has always been strong for final documents, but when it comes to living documents—things that evolve over time with updated data—it starts to show limitations. I’ve personally worked with exported reports from different systems, including vehicle diagnostics, and even small edits can feel unpredictable. It breaks the workflow, especially when you’re trying to maintain consistency across versions.
What stands out to me is the lack of structure awareness. These PDFs aren’t just text—they’re data. Tables, metrics, logs, all interconnected. When you edit one value, everything else should stay intact, but that’s not always the case. I recently came across a breakdown explaining how EV battery reports are structured and why even minor changes can affect readability and accuracy, which really highlights the gap in current editing tools. This website https://evbattery.us/ gives a good example of how these reports are actually used in practice.
So yes, I support this idea, but I’d frame it as Acrobat needing to evolve from a document editor into something that better understands structured, data-heavy content. Whether it’s EV reports or any other technical documentation, users shouldn’t have to fight the layout just to make simple updates.