Difference between revisions of "Command/fillinfield"
< Command
Jump to navigation
Jump to search
m (Text replace - "[[Category:Commands|" to "== ConTeXt-Forum == {{Forum|{{SUBPAGENAME}}}} [[Category:Commands|") |
m (Text replace - "ConTeXt-Forum " to "Help from ConTeXt-Forum ") |
||
Line 44: | Line 44: | ||
<!-- something like [[cmd:goto|\goto]] --> | <!-- something like [[cmd:goto|\goto]] --> | ||
− | == ConTeXt-Forum == | + | == Help from ConTeXt-Forum == |
{{Forum|{{SUBPAGENAME}}}} | {{Forum|{{SUBPAGENAME}}}} | ||
[[Category:Commands|fillinfield]] | [[Category:Commands|fillinfield]] |
Revision as of 00:50, 15 March 2012
\fillinfield
Syntax
\fillinfield[...]{...} | |
[...] | text |
{...} | text |
Example
\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