John Brinkman comments

Results 17 comments of


                                            John Brinkman

Existing pct-encoding in values for reserved {+} or fragment {#} expansion must NOT be re-encoded

Excellent. Thank you.

Lack of clarity on requirement of existence of `V` key on Text fields

duplicate of https://github.com/pdf-association/pdf-issues/issues/392

Is the `V` key required to be present on a Text Field?

Suggested wording: > If the field has a value other than null, it shall be held in a text string (or, beginning with PDF 1.5, a stream) in the V...

Is the `V` key required to be present on a Text Field?

> where abouts are you proposing this change in ISO 32000-2? Section 12.7.5.3 First sentence after table 231.

Forms.next requires that `V` & `DV` keys be allowed on push buttons

For background: HTML a button value is included in a submit operation for the button that was clicked to initiate the submit. For our purposes, we should allow push buttons...

Forms.next requires that `V` & `DV` keys be allowed on push buttons

@datalogics-pgallot > I'm curious as to what the processor requirements might be for a Pushbutton field with an associated value. The requirement is compatibility with HTML forms. HTML buttons may...

Make string to number coercion more strict

agreed

Make string to number coercion more strict

> Either we should throw an error that they are not comparable or compare them so that this particular invariant should hold if (a >=b) => true then (a <...

Example of how to add a custom function with signature using constants

You're right, we're missing an export. I will add it to the next release. Until then, you'll need to redefine them in your project: ``` const dataTypes = { TYPE_NUMBER:...

Example of how to add a custom function with signature using constants

@VentuzVictorPerez This should be fixed in the 1.1.2 release