Paranthesis around literal strings are not checked

[asciim0]

Dev Effort

1D

Description

Per standard, String objects can be written in two different ways: either as literal strings enclosed in parentheses ( ) or as hexadecimal data enclosed in angle brackets. Strings can contain balanced parentheses. Missing parentheses around literal strings result in objects being not rendered correctly. Despite the fact that this is a standard violation, JHOVE considers the test case T02-05-01_009 with a missing opening parenthesis, test case T02-05-01_010 with a missing closing parenthesis and T02-05-01_011 with parentheses being replaced by brackets well-formed and valid. All test cases can be found in the ipres test corpus.

[carlwilson]

Hi @asciim0. I've had a look at addressing this for the 1.20 release but unfortunately it won't be possible. The problem is that this is a larger piece of work than it initially appears. The string literals in the test files all occur within a PDF content stream object and aren't validated by JHOVE at all unless I'm mistaken. Altering the PDF module so that it parses and validates content streams will require more effort to refactor and test than is available before the upcoming release.

[MartinSpeller]

Paranthesis around literal strings are not checked #214 - Assigned to TBA