Most compatible / lax parsing options
- Dominant language
- C++
- Stars
- 262
- Forks
- 110
- PR merge metrics
- No merged PRs in 30d
Description
When parsing different XMP Metadata (contained in PDFs) we sometimes get errors. Now I realized that it is possible to specify several parsing options. So my question is what the most lax / compatible setting for reading XMP data would be. The following options are available and I would set the options to the following values:
```
ParseOptions po = ...;
po.setAcceptLatin1(true);
po.setDisallowDoctype(false);
po.setFixControlChars(true);
po.setOmitNormalization(true);
po.setRequireXMPMeta(false);
po.setStrictAliasing(false);
```
Are these the most lax parsing options (in terms of reading compatibility)?
Contributor guide
Research direction
Start with the ParseOptions API and the listed parsing flags, then compare their documented behavior against the XMP parsing errors described here. Done means establishing and documenting whether these values are the most compatible combination, or identifying which options should differ.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100