summaryrefslogtreecommitdiff
path: root/macros/latex/contrib/ocgx2/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'macros/latex/contrib/ocgx2/README.md')
-rw-r--r--macros/latex/contrib/ocgx2/README.md29
1 files changed, 19 insertions, 10 deletions
diff --git a/macros/latex/contrib/ocgx2/README.md b/macros/latex/contrib/ocgx2/README.md
index 1f33d755ed..b74fe96291 100644
--- a/macros/latex/contrib/ocgx2/README.md
+++ b/macros/latex/contrib/ocgx2/README.md
@@ -127,15 +127,15 @@ document.
A `<visibility policy>` can be *one* of
````latex
-\AllOn{<OCG id 1>, <OCG id 2>, ...}
-\AnyOn{<OCG id 1>, <OCG id 2>, ...}
-\AnyOff{<OCG id 1>, <OCG id 2>, ...}
-\AllOff{<OCG id 1>, <OCG id 2>, ...}
+\AllOn{<OCG id 1> [, <OCG id 2>, ...]}
+\AnyOn{<OCG id 1> [, <OCG id 2>, ...]}
+\AnyOff{<OCG id 1> [, <OCG id 2>, ...]}
+\AllOff{<OCG id 1> [, <OCG id 2>, ...]}
````
All four directives take a list of OCG ids from wich the OCMD visibility is
calculated. If the condition represented by the policy is met, the content
associated with the OCMD is shown. The listed OCGs can be defined anywhere in
-the document. These directives can neither be combined nor nested in order to
+the document. These directives *can neither be combined nor nested* in order to
define the policy. Thus, a visibility policy has limited capabilities.
A `<visibility expression>` is much more flexible than a policy. Arbitrarily
@@ -149,12 +149,21 @@ functions
````
In the argument list, items represent OCG/OCMD ids and nested Boolean
functions. As nesting of the three functions is possible, any thinkable
-visibility relationship can be defined. Note that `\Not{...}` accepts only
-one item, either an OCG/OCMD id or a nested function. Also note that Boolean
-functions and policy directives cannot be intermixed.
+visibility relationship can be defined.
-As a trivial example, the visibility expression equivalent of the policy
-directive `\AllOff{...}` is written as `\Not{ \Or{ ... } }`.
+Note that `\Not{...}` accepts only one item, either an OCG/OCMD id or a nested
+function. Besides that, a single, isolated OCG/OCMD item is not allowed as an
+expression, it must always be embedded in one of the Boolean functions listed
+above. In the simple case of an OCMD depending on a single OCG in a positive
+way, it is better to use a policy, such as `\AllOn{<OCG id>}`, or to put it as
+`\And{<OCG id>}`.
+
+Thus, simple OCMD visibilities can be expressed in an equivalent way by a
+policy or an expression. For example, the visibility expression equivalent of
+the policy directive `\AllOff{...}` is written by means of Boolean functions as
+`\Not{ \Or{ ... } }`.
+
+Note that Boolean functions and policy directives cannot be intermixed.
----