Thanks for the parser contribution! Could you fork this from the dev branch? Also, I notice other parser files in this PR. Could you ensure the PR only includes the parser.py file and tests/fixtures?

Thanks!

Hey Kelly,
I just rebased that branch, sorry for the late reply. There are no other files in this PR, only universal which I only included because of the universal output of pdfinfo, I thought it would be logical to extend a parser.

Title:          Brochure
Producer:       Skia/PDF m111 Google Docs Renderer
Tagged:         no
Form:           none
Pages:          2
Encrypted:      no
Page size:      612 x 792 pts (letter) (rotated 0 degrees)
File size:      69988 bytes
Optimized:      no
JavaScript:     no
PDF version:    1.4

Thanks for maintaining a great library man, appreciate your work.

Hi @Luigi31415 - thanks for the updates. I wonder if there is a simpler way to do this since it looks like pdfinfo output is really just key/value pairs and we already have a key/value parser (--kv). Is there a need for this parser?

I can see if the keys should be renamed, then maybe we just alias to the existing --kv parser (which itself is an alias of --ini) and then just run the lib.normalize_key function within _process.

Here is the jc output using the existing key/value parser:

% echo 'Title:          Brochure
Producer:       Skia/PDF m111 Google Docs Renderer
Tagged:         no
Form:           none
Pages:          2
Encrypted:      no
Page size:      612 x 792 pts (letter) (rotated 0 degrees)
File size:      69988 bytes
Optimized:      no
JavaScript:     no
PDF version:    1.4' | jc --kv -p
{
  "Title": "Brochure",
  "Producer": "Skia/PDF m111 Google Docs Renderer",
  "Tagged": "no",
  "Form": "none",
  "Pages": "2",
  "Encrypted": "no",
  "Page size": "612 x 792 pts (letter) (rotated 0 degrees)",
  "File size": "69988 bytes",
  "Optimized": "no",
  "JavaScript": "no",
  "PDF version": "1.4"
}