On 4/4/19 1:20 PM, Hans Hagen wrote: > On 3/17/2019 4:41 PM, Pablo Rodriguez wrote: > >> - Although not reported, the /F value should conform these considerations: >> >> If present, the F key's Print flag bit shall be set to 1 and its >> Hidden, Invisible, ToggleNoView, and NoView flag bits shall be set >> to 0. >> https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-and-3-rules#rule-632-2 >> >> - Annotations need an appearance dictionary >> (https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Parts-2-and-3-rules#rule-633-1); >> unless the same exception for the /F value apply. > > puzzling ... i wonder what the rationale is behind first introducing > optional flags and then mandating them with bit disabling things ...
I guess that annotations in PDF/A are intended to be always printed and visible (at least, for versions 2 and 3). > if this is really as mentioned that we might need to default to some > safe values without bothering about user settings (which is now the > case) I think that default may contain the safe and sane values for all annotations. Just in case it helps, Pablo -- http://www.ousia.tk _______________________________________________ dev-context mailing list [email protected] https://mailman.ntg.nl/mailman/listinfo/dev-context
