You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/meta/taking-ownership.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ that if I become unavailable, e.g. due to severe health issues.
6
6
7
7
This currently is just an abstract scenario. I'm fine and I will likely do this
8
8
for several more years, but I have seen how projects stand still for many years
9
-
because of the maintainer becomming inactive.
9
+
because of the maintainer becoming inactive.
10
10
11
11
I've also followed the [GitHub Deceased User Policy](https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy)
12
12
and added a [pre-designated successor](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories).
Copy file name to clipboardexpand all lines: docs/user/forms.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -64,10 +64,10 @@ To flesh out this overview:
64
64
-`/V`: Field Value
65
65
-`/DV` : Default Field Value (used when resetting a form for example)
66
66
* In order to streamline readability, _Field_ Objects and _Widget_ Objects can be fused housing all properties.
67
-
* Fields can be organised hierarchically, id est one field can be placed under another. In such instances, the `/Parent` will have an IndirectObject providing Bottom-Up links and `/Childs` is an array carrying IndirectObjects for Top-Down navigation; _Widget_ Objects are still required for visual rendering. To call upon them, use the *fully qualified field name* (where all the individual names of the parent objects are seperated by `.`)
67
+
* Fields can be organised hierarchically, id est one field can be placed under another. In such instances, the `/Parent` will have an IndirectObject providing Bottom-Up links and `/Kids` is an array carrying IndirectObjects for Top-Down navigation; _Widget_ Objects are still required for visual rendering. To call upon them, use the *fully qualified field name* (where all the individual names of the parent objects are separated by `.`)
68
68
69
69
For instance take two (visual) fields both called _city_, but attached below _sender_ and _receiver_; the corresponding full names will be _sender.city_ and _receiver.city_.
70
-
* When a field is repeated on multiple pages, the Field Object will have many _Widget_ Objects in `/Childs`. These objects are pure _widgets_, containing no _field_ specific data.
70
+
* When a field is repeated on multiple pages, the Field Object will have many _Widget_ Objects in `/Kids`. These objects are pure _widgets_, containing no _field_ specific data.
71
71
* If Fields stores only hidden values, no _Widgets_ are required.
72
72
73
73
In _pypdf_ fields are extracted from the `/Fields` array:
0 commit comments