* specification; if they can't be interpreted
they are ignored.
2.
``size`` commands can occur anywhere and can be combined with a ``css`` command:
if they occur before the ``css`` command the contents of ``css`` will override ``size``,
and vice-versa if they occur afterwards: the CSS string for the
```` section is assembled in the order the commands occur.
3.
Because CSS doesn't use object-like inheritance, the ``size: [body]`` command resets
*all* of the properties of ``body``, leaving only ``width`` and ``height`` set in the style, e.g.
.. code::
body {
width:900px;
height:700px;
}
If you want to change the size but also retain other characteristics, use ``css``
to define the complete ``body`` style.
4.
The ``civ-editor`` command changes the size in the configuration of CKEditor rather than
any CSS, so this name cannot be used in ``css:`` (well, it can be used but it won't
do anything...). CKEditor does not allow the “%” option to be used as a “height”:
see http://docs.ckeditor.com/#!/guide/dev_size. The CKEditor defaults to the width
of the page (more or less) and a height of 200px.
5.
The ``civ-form`` and ``civ-text-display`` names correspond correspond to ````
in the content of the form; you can modify these directly by using a ``css:``command.
The ``size`` command resets the *-size* class, which only controls the size.
Insert HTML
-----------
[This command may or may not be included in the operational version of
the system, as it provides some opportunities for mischief. Stay tuned.
It is in the code but currently deactivated; if you are installing your
own version of the system, it can be activated by setting
``civet_settings.HTML_OK = True``.]
Adds arbitrary HTML code without escaping.
| **html:**
| one or more lines of HTML
.. rubric:: Footnotes
.. [#f1]
Writing in HTML5 and CSS, one can actually exercise a very fine
degree of control over the placement, but if you are comfortable with
that sort of code, you presumably aren’t using CIVET in the first
place. That said, you can see the HTML generated by CIVET by using
the *View source* option in your browser, then save it as a file
using *Save Page As...* and that could provide a starting point for
creating prettier code.
.. [#f9]
This feature is actually a bit more subtle: cancellation is invoked when
the first character in a line is “-” *and* there is a “:” in the line,
which will always occur with a command. This allows default texts such as “- - -”
to be used, though a default text such as “- - -: we really want to confuse CIVET”
will cause an error.
.. [#f2]
In the current implementation, named HTML entities such as ``©``
and ``€`` can be included and should produce the correct
character. At present numbered entities such as ``[``—the HTML
equivalent of ’]’—do not work since the # is interpreted as a comment
delimiter: depending on whether there is demand for this feature, the
system could provide a way around this.
.. [#f3]
This format can be changed in the function ``get_special_var(avar)`` in
*civet_form.py*: It is specified using the extensive Python/C date format
operators shown `here. `_
.. [#f4]
In fact, the ``comments:`` command is just a shorthand for
``textarea: entry-text [_comments_]``, and this will have the same
effect, with the contents added to the metadata.
.. [#f5]
Neither a bug nor a feature: just is what it is.
.. [#f6]
At present, only these two fields are available, but it is relatively
straightforward to add the others by just following the existing
code that you locate in a search for “textpublisher”
.. [#f7]
This is only done in the automatic annotation if
``civet_settings.USE_GEOG_MARKUP = True``: see the discussion in the
*Preferences* chapter.
.. [#f8]
In a future version of CIVET we hope to have a facility where citation
information can be transferred into a ``textsource`` field by clicking on
a lede but this has been implemented yet.
*Preferences* chapter.