Thread: CFI Parser
View Single Post
Old 01-14-2019, 04:45 AM   #5
thiago.eec
Wizard
thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.thiago.eec ought to be getting tired of karma fortunes by now.
 
Posts: 1,217
Karma: 1419583
Join Date: Dec 2016
Location: Goiânia - Brazil
Device: iPad, Kindle Paperwhite, Kindle Oasis
Quote:
Originally Posted by kovidgoyal View Post
The best you can do in general is go to the line that contains the start of the tag referenced by the CFI.
Ok. That would be good enough. Can you give me some orientation on how to do that?

P.S.: I thought it would be possible to get line and column after reading this post of KevinH. He used you parser to achieve that.


Quote:
Originally Posted by kovidgoyal View Post
I dont know why the ACE tool chose CFI as a way to report error locations, it is not suited for that task, at all. Its a way to reference locations in an rendered HTML tree, not HTML source.
It surely would be easier if it gave a (lin,col), like EPUBCheck.
thiago.eec is offline   Reply With Quote