Changes

356 bytes added , 14:37, 15 October 2019

no edit summary

}}

== [[Help:Reference|Syntax]] (autogenerated) ==

<syntax>fillinfield</syntax>

== [[Help:Reference|Syntax]] ==

</table>

== Example ==

~~== Description ==~~

<texcode>\usemodule[fields, abr-pseudocaps]

\setupinteraction[state=start]

\starttext

A few years back, \TEX\ could only produce \fillinfield [dvi]{\DVI}

output, but nowadays, thanks to \fillinfield {Han The Thanh},

we can also directly produce \fillinfield [pdf] {\PDF}! Nice eh?

Actually, while the first field module was prototyped in \ACROBAT,

the current implementation was debugged in \fillinfield [pdfTeX] {\PDFTEX}.

Field support in \fillinfield [ConTeXt] {\CONTEXT} is rather advanced

and complete and all kind of fields are supported. One can hook

in appearances, and validation \fillinfield [JavaScripts] {\JAVASCRIPT}'s.

Fields can be cloned and copied, where the latter saves some space.

By using \fillinfield {objects} when suited, this module saves space anyway.

\stoptext

</texcode>

~~A few years back~~'''Beware''', ~~\TEX\ could only produce~~{{cmd|fillinfield}} has a broken validation script that empties the field after input and thus doesn’t make sense, see {{src|m-fields.mkiv}} (as of 2017-03-14; probably since 2010).

~~\fillinfield [dvi]{\DVI} output,~~== See also == ~~but nowadays, thanks to \fillinfield~~

~~kind of fields are supported. One can hook in appearances, and~~ ~~validation \fillinfield [JavaScripts] {\JAVASCRIPT}’s. Fields~~ ~~can be cloned and copied, where the latter saves some space. By~~ ~~using \fillinfield {objects} when suited, this module saves~~ ~~space anyway.~~ ~~\stoptext~~ == ~~See also~~ Help from ConTeXt-Mailinglist/Forum ==~~~~{{SUBPAGENAME}}}}

[[Category:~~Reference~~Command/enFields|fillinfield]]

Usonianhorizon

973

edits

Changes

Command/fillinfield (view source)

Revision as of 14:37, 15 October 2019