Comment 41 for bug 623438

I am not entirely convinced about his arguments about UTF-8 and whitespace (sounds like just being lazy to adopt the parser to hOCR specs), but the loss of information about y-coordinates, which used to be present in the output of the previous versions sounds very much like a bug (if it's indeed the case).

I think that hOCR specification has to be studied in order to find out what are the actual requirements and if they can be interpreted liberally to a certain extent, maybe this could be put to advantage of hOCR developer.