show baselines

[bertsky]

Today I was surprised to learn that PageViewer does not visualise TextLine/Baseline.

Wouldn't be much more than checking for line.getBaseline() in DocumentImageView.drawTextlines(), and using a new DrawingHelper.drawMultiline to display it, right?

[chris1010010]

The world is full of surprises...
:-)

[bertsky]

The world is full of surprises...
:-)

Sure, but how do I ever get to see a PAGE baseline then? Is Aletheia the only tool that shows them? Or is AletheiaWeb, too?

Also, on my suggestions – assuming I would be able to get the build system for this package – is that the way to go, or am I missing something?

[chris1010010]

Just Aletheia at the moment

[bertsky]

Just Aletheia at the moment

I see. Do you happen to know if this works with wine? (It should, you know, since in vino veritas ...)

Also, on my suggestions – assuming I would be able to get the build system for this package – is that the way to go, or am I missing something?

Still thinking about a PR but waiting for your approval/comment.

[chris1010010]

Merged in the baseline code

[bertsky]

Merged in the baseline code

Thanks, but 5113c38 is not a merge, it's a copy, modify and paste. I'll have to rebase now. If you had just asked me to split my PR I would have done so (as I said)...

Also, I wonder why you always couple changes of source files with fully regenerated apidoc HTMLs in your commits. This makes it much harder to view them and browse history. If apidoc needs to be in the same repo, please at least commit the HTMLs separately.

[chris1010010]

Ok, yes, it was a manual merge.
Code and JavaDoc are generated. I use a separate code base in SVN. Should move at some point, no time though

[bertsky]

Oh, I see – that explains it. But perhaps you could do something like

git add "*.java" && git commit -m "changes"
git add -A && git commit -m "javadoc"

?