Manuel Collado wrote: > By the way, a minor inconsistency is that the given diagnostic messages > seem to count lines starting from 1, but columns starting from 0. Most > text editors don't do so, but count columns also from 1.
This is not a bug (i.e. this is documented in our API). We are reluctant to change this because, in such case, we need to update the documentation and all our non-regression tests. > I'm using a customizable text editor to edit DTD/CSS files. When editing > a DTD, the editor allows me to call an external command-line validator, > capture the output, parse it, and set the cursor on the offending > element by simply clicking on the diagnostic message. > > It's frustrating not to been able to do so for CSSs. Please consider > making available this facility. OK, you'll have this command line utility in next release.
