93
edits
Changes
Jump to navigation
Jump to search
Added a hidden anchor because you can't link to a heading that has command names in it.
This is a [[Right_and_left|FAQ item]].
<span id="setupnotation v setupnote"></span>
== Footnotes: The Difference between {{cmd|setupnotation}} and {{cmd|setupnote}} ==
(For more definite answers concerning the ''notes'' mechanism, use the
source, Luke: {{src|strc-not.mkvi}}.)
== Float Insertion Issues ==
(If you desparately need separate captions please send a feature
request to one of the
[[ConTeXt_Mailing_Lists#Mailing ListsMailing_Lists]]).
<context source="yes" mode="mkii">
= Syntax =
== Assignments ==
Spaces before commas or before the closing <code>]</code> are '''''not''''' ignored in ConTeXt. That is a common pitfall and leads to errors that can be confusing for beginner, especially those coming from LaTeX, where this is the default behaviour. Formatting your keys like this might look nice but leads to spurious spaces:
<context source="yes" mode="mkiv">
\getparameters[test]
[ foo=bar
, hello=world
]
“\testfoo” “\testhello”
</context>
Instead it is recommended to adhere to the style that is used in the ConTeXt source to avoid problems with trailing spaces:
<context source="yes" mode="mkiv">
\getparameters[test]
[foo=bar,
hello=world]
“\testfoo” “\testhello”
</context>
In the most common form of key-value type arguments, ConTeXt will
pass being omitted.
In [[MetafunMetaFun - MetaPost in ConTeXt]], the default Metapost format in Context, the booleans
<code>mfun_first_run</code> and <code>mfun_trial_run</code> allow
detecting the individual stages:
\stoptext
</texcode>
[[Category:Basics]]
[[Category:Tools]]
