Error location should be easy to find / counting CFI

Is there an easy way to find a location that is given with the CFI?
Currently I am desperatly looking for the cause of the error/warning below. But the message does not help much.
I know in which file the error is in. But after that it is counting elements and trying to find the right location.

So my general question is:
Can the error messages include a line or a text snippet that is actually helping to find the error without interpreting the CFI?

```
"Teil B"

text/008_400699_003.xhtml#epubcfi(/4/2/6/10)

Snippet (I added some line breaks to make the non-helpful information easier to see):

```

The issue names no source files, tests, or entry points. Start by locating where CFI-based errors and warnings are generated, then determine how a line or useful text snippet can be reported; done means the messages let users find the problem without interpreting the CFI.

Written by the indexing model from the issue text.