Table page break bug and PDFBOX character bug #19
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a reduced testcase which shows two bugs:
character. Instead a # character appears. There are even two # characters on places were no character is shown... If you view the html in a browser you see the right symbols. This works fine in flyingsaucer - after I manually register an other font (e.g. Noto Sans) which has this unicode symbol, as the fonts included in iText 2.1.7 don`t have that character.
Do you know how this "table repeated headers on page break" stuff works? I tried to figure it out / debug it, but I just don
t really understand where the repeated table headers are created. Somehow the top-margin is not calculated correctly after the page break. If you increase the margin-top in line 126 of the html file you can see that the header somehow gets more into the view. If you can give me some pointers were to look I can try to future investigate that problem. But at the moment I really don
t know were to look.I don`t think that examples is the right location for such a test case. But its not a unit case neither. Please tell me were I should place this files.
Thanks for reviving flyingsaucer under a new name! Beside some rare bugs like these its a very useful library to create reports (using html). And also to render html snippets to images (which I also use in my projects)