Fix for two bugs related to Unicode translation support by Font objects

[unixnut]

Symptom was that some documents' contents was rendering as a bunch of control characters. These are the untranslated strings. This was happening because for two different reasons, these strings weren't being translated \Smalot\PdfParser\Font::decodeContent() in some circumstances.

First fix is to \Smalot\PdfParser\Font::loadTranslateTable():

• Fixed bug where bfchar sections weren't loaded due to mistake in regexp.
• It now uses * instead of + and thus supports translation tables with lines like <0000><0000>. (Required <0000> <0000> before.)

Second fix is for documents that attach their Font objects to the Pages object instead of each Page object:

• \Smalot\PdfParser\Page now has a setFonts() method
• \Smalot\PdfParser\Pages now declares its $fonts variable
• \Smalot\PdfParser\Pages::getPages() now applies the object's fonts to each child Page
• \Smalot\PdfParser\Pages::getFonts() copied from Page class

Type of pull request

• [x] Bug fix (involves code and configuration changes)
• [ ] New feature (involves code and configuration changes)
• [ ] Documentation update
• [ ] Something else

About

Checklist for code / configuration changes

In case you changed the code/configuration, please read each of the following checkboxes as they contain valuable information:

• [ ] Please add at least one test case (unit test, system test, ...) to demonstrate that the change is working. If existing code was changed, your tests cover these code parts as well. By the way, you don't have to provide a full fledged PDF file to demonstrate a fix. Instead a unit test may be sufficient sometimes, please have a look at FontTest for example code. Code changes without any tests are likely to be rejected. If you dont know how to write tests, no problem, tell us upfront and we may add them ourselves or discuss other ways.
• [ ] Please run PHP-CS-Fixer before committing, to confirm with our coding styles. See https://github.com/smalot/pdfparser/blob/master/.php-cs-fixer.php for more information about our coding styles.
• [ ] In case you fix an existing issue, please do one of the following:
  • [ ] Write in this text something like fixes #1234 to outline that you are providing a fix for the issue #1234.
  • [ ] After the pull request was created, you will find on the right side a section called Development. There issues can be selected which will be closed after the your pull request got merged.
• [ ] In case you changed internal behavior or functionality, please check our documentation to make sure these changes are documented properly: https://github.com/smalot/pdfparser/tree/master/doc
• [ ] In case you want to discuss new ideas/changes and you are not sure, just create a pull request and mark it as a draft (see here for more information). This will tell us, that it is not ready for merge, but you want to discuss certain issues.

[GreyWyvern]

I'm on vacation atm, but I can take a look at this on Monday. 👍

[GreyWyvern]

• Your code is about decryption and encryption, but in the title its about Unicode translation. Please elaborate on that a bit.

After a first pass of the code, this is what I'd like to know as well. I feel like for this many lines, the description as to what this PR does needs to be much much longer! :D What's the purpose of this encryption/decryption code? Does it supercede the previous PR #653?

I will keep studying it.

[k00ni]

Please merge in master branch, to get rid of these coding style issues.

[unixnut]

@k00ni @GreyWyvern my mistake, I forgot GitHub consumes all commits on a branch for a PR.

This PR is supposed to be for the first commit only

[k00ni]

@k00ni @GreyWyvern my mistake, I forgot GitHub consumes all commits on a branch for a PR.

This PR is supposed to be for the first commit only

Proceed as you see fit. I assume either close this one and create another PR with your changes or simply remove all additional changes in this PR and force push in order to update it.

[GreyWyvern]

I think I would probably cancel this PR and start a clean one, but that's just me. :)

[k00ni]

Please open new PRs with smaller sets of code changes. Thanks.