LogoLogo
ClausesDatafieldsSpecial FunctionsStylingQ&AAPI
  • Welcome!
  • Getting started
    • What is Clause9?
    • Structuring your clause library
    • Structuring your clauses
    • Drafting modes in Clause9
    • Creating a questionnaire
    • Sample clauses
    • Videos
      • Concepts and datafields
      • Conditions
      • Q&As
      • Binders
      • Styling
      • Enumerations
      • Tables
      • Definitions
      • Snippets
      • Cross-references
      • Special functions
      • Examples of common clauses
      • Import clauses from MS Word
      • Grammatical conjugations
      • Action buttons
      • Alternative clauses
  • Assemble document
    • Document toolbar
    • Clause hierarchies
    • Focus Mode
    • Bulk generation of documents
    • Exporting documents
    • Assemble Document - FAQ
    • How to: Assemble Document
      • Insert images
  • Assemble Document Operations Panel
    • Operations panel
    • File pane
    • Edit pane
    • Document pane
    • Binder pane in the operations panel
    • Search pane
    • Browse pane
    • Terms pane
    • Data dashboard
    • Advanced pane
    • Styling pane
    • Miscellaneous pane
    • Visibility settings & actions menu
  • Binders
    • Binders: general
    • Styling cross-references to subdocuments
    • Global and local definition lists
    • Document and binder properties
    • Styling of a Binder versus subdocuments
    • (Un)locking documents in a binder
    • Binders - FAQ
    • How to: binders
      • Make a subdocument in a binder conditional
  • Clauses
    • Introduction to clauses
    • Clause structure
    • Grammar sheet
    • Writing conditions
    • Examples of conditions
    • Using codes instead of text fragments
    • Bold, italic and underline
    • Special codes
    • Enabled?
    • Links
    • Cross-references
    • Introduction to tables
    • Deviating table styling
    • Shrinking clauses
    • Action buttons
    • Enumerations
    • File position
    • Snippets
    • Parameters
    • Conjugations
    • Mixing data types
    • For-loops
    • Clause versioning
    • Abstract article references
    • Advanced multi-language features
    • Clauses - FAQ
    • How to: clauses
      • Create an ad-hoc clause
      • Create a library clause
      • Make a clause repeat
      • Make a paragraph within a clause conditional
      • Use a shortcut to refer to a concept
      • Insert a line break or page break
      • Creating a list with both predefined options and free input
      • Defining alternative clauses
      • Creating cross-references
      • Creating signature blocks
      • Creating advanced party introduction clauses
      • Automatically numbered annexes or schedules
      • Reuse any clause in a different context
      • Setting MS Word document properties
      • Add action buttons to clauses
      • Electronically signing documents
  • concepts
    • Introduction to concepts
    • Creating concepts
    • Concept labels
    • Links
    • Organising concepts
    • Concepts - FAQ
    • How to: concepts
      • Add predefines to a datafield
  • Datafields
    • Introduction to datafields
    • Types of datafields
    • Rules of thumb for using datafields
    • Data-expressions
    • Datafield aliases
    • Datafield labels
    • Datafield special tags
    • Datafield descriptions
    • Repeating list datafields
    • Datafield predefines
    • Datafields - FAQ
    • How to: datafields
      • Change datafield type
      • Change the datafield's name or alias
  • Definitions
    • Introduction to definitions
    • How to: definitions
      • How do definitions work?
      • Create a definition
  • Files
    • How files are organised
    • Browse files
    • File types
    • Custom styling
    • Legal comments
    • File description
    • Attributes
    • Reporting
    • File name
    • File category
    • Access rights
    • How to: files
      • Creating advanced folders
      • Naming your files
      • Shortcuts to folders or files
  • Q&A
    • About cards
    • Cards pane
    • About changes
    • Changes pane
    • Types of changes
    • Adding conditions
    • Question options
    • Copying & pasting answers
    • Comments, notes & documentation
    • Interactive Q&A inspection
    • Embedding questions into a document
    • “Changes” button
    • Batch create pane
    • Identifiers pane
    • Import pane
    • Edit clauses pane
    • Q&A options
    • Q&A - FAQ
    • How to: Q&A
      • Create predefined answers to a question
      • Add disclaimers
      • Create categories of questions
      • Modify the exported filename
      • Create a question to change the language of a document
      • Send a questionnaire to someone without a ClauseBase account
      • Create questions for repeating list datafields
      • Selecting legal entities & addresses
      • Create a questionnaire using "batch create"
      • Launch other Q&As
    • Leveraging ClauseBuddy Smart Templates in Clause9
  • Import
    • Introduction to importing clauses
    • Uploading clauses
    • Defined terms in Import mode
    • Datafields in Import mode
    • Cross-references in Import mode
    • Assigning folders
    • Conversion process
    • Exporting
    • Stashing intermediate results
    • Tips, tricks & limitations
  • Styling
    • Styling overview
    • Base styling
    • Numbering
    • Definitions styling
    • Enumerations styling
    • Locale styling
    • References styling
    • Page styling
    • Styling of a Binder versus subdocuments
    • Styling: tips and tricks
    • Advanced styling topics
    • Copying headers and footers from an MS Word file
    • How to: styling
      • Using custom fonts
      • Change bullet styling
  • Special functions
    • Introduction
    • Calculations
    • Concepts
    • Conditions
    • Conjugations
    • Content Control Elements
    • Datafields
    • Dates & durations
    • Languages
    • Lists
    • Numbers
    • References
    • Repeating (looping)
    • Special items
    • Text structure
    • Text modification
    • User
    • Q&A
  • Settings
    • Account
    • Preferences
    • Access bundles
    • Favourites
    • Saved searches
    • Saved datafields
    • Styles
    • Default styles
  • Admin
    • General
    • Users
    • User rights
    • Profiles
    • Groups
    • Styles
    • Default styles
    • Attribute models
    • Usage page
    • Custom homepage
    • Global placeholders
    • Access rights
    • How to: admin
      • Adding a new user
      • Disabling a user
      • Managing group memberships
  • Miscellaneous
    • Advanced tips & tricks
    • Typing special symbols on your keyboard
    • Shortcuts
    • Grammar style guide
    • Inserting MS Word files
    • Globo-panel
    • Creating high-quality documents
    • Excel calculations and lookups
  • Integrations
    • Overview
    • Spreadbases
    • E-signing documents
    • Drag & drop integrations
  • For developers
    • Clause9 API
    • Custom functions
    • Example custom functions
Powered by GitBook
On this page
  • Regular bullets
  • Internal bullets
  • Items in the same block of text (aka “Inline lists”)
  • Items on separate lines
Export as PDF
  1. Styling

Enumerations styling

The enumeration styling settings distinguishes between three different types of enumerations:

  • regular bullets, i.e. bullets that are inserted by typing in one or more asterisks (*) in the body of a clause

  • internal bullets, i.e. bullets that are inserted through one of the special codes for enumerations — such as { AND | ... } or { LIST | ... }. Those internal bullets can finally result in:

    • items in the same block of text — also called “inline lists” in the documentation, for example (i) alpha, (ii) beta, (iii) gamma

    • items on separate lines — i.e. real bulleted lists

Regular bullets

This section of the settings targets bullets that are inserted by typing in one or more asterisks (*) in the body of a clause, and inserting the right enumeration-type as the very first item.

For example, typing:

* alpha
* beta
* gamma

will result in three items, on separate lines, without any suffixes (such as semicolons / comma’s / etc.). If you want to insert such suffixes, you have to type:

* AND
* alpha
* beta
* gamma  

Typing* AND, * OR, *AND/OR or *LIST will ensure that all items that follow, will be formatted with a suffix. What this suffix looks like, is determined by the enumeration styling discussed below.

The settings are fairly straightforward:

  • The first setting allows you to specify the character that will be inserted at the end of each item (except for the very last item): a period, comma, semicolon or nothing.

  • The second setting allows you to specify whether or not to repeat the “and”, “and/or” or “or” at the end of everyitem, or whether instead such suffix should only be inserted at the end of the penultimate item.

This second setting has no effect on enumerations created using the {LIST | ... } code or the @enumerate special function, because those will result in enumerations that do not show any such suffix.

  • The third setting specifies the character (if any) that should be shown after the last item in the list. If you do not want any character at all, leave this blank.

Even when this setting is active, you can avoid that this character would be inserted in a specific enumeration, by using AND-SKIPFINAL, OR-SKIPFINAL, AND/OR-SKIPFINAL or LIST-SKIPFINAL (when explicitly typing in bullet-lists) or by using one of the special functions that have -skipfinal in their name (e.g., @enumerate-skipfinal).

Internal bullets

With this setting, you can configure when internal bullets — i.e. those inserted through one of the special codes for enumerations, such as { AND | ... } or { LIST | ... }— should be printed as text concatenations, and when they should be printed as real bulleted lists.

  • always put each item on a separate line forces the internal bullets to always be shown as real bulleted lists

  • concatenate items if possible will try to concatenate items, typically using romanettes — e.g. (i) … (ii) … (iii) …

As suggested by this option, there exist situations where concatenation is not possible. This will be the case when at least one of the items happens to consist of multiple paragraphs. In such case, it is obviously impossible to concatenate all items into one single paragraph. Clause9 will therefore use real bulleted lists instead.

  • concatenate items up to … words will use concatenated lists up to a maximum number of words. If the number of total words is higher, then real bulleted lists will be used instead.

Items in the same block of text (aka “Inline lists”)

These settings configure how concatenated lists of items should be shown:

  • Put a comma/semicolon/space after each item.This setting specifies which character to insert after each item:

    • a comma — alpha, beta, gamma

    • a semicolon — alpha; beta; gamma

    • a space — alpha beta gamma

  • Repeat/don’t repeat and-or-and/or for every item.This setting specifies whether the “and”, “or” or “and/or” should be inserted:

    • after each item — alpha, and beta, and gamma

    • only after the penultimate item — alpha, beta and gamma

This setting has no effect on enumerations created using the {LIST | ... } code or the @enumerate special function, because those will result in enumerations that do not show any such suffix.

  • Show/don’t show the comma when and-or-and/or is shown.This setting specifies whether the comma/semicolon/space should be shown when an “and”, “or” or “and/or” is shown:

    • do show — alpha, beta, and gamma

    • don’t show — alpha, beta and gamma

  • Only number items when suggested by the clause author. This setting allows you to force an enumeration to always show numbers as prefixed for each item. In principle, such numbers are only shown when you explicitly type in numbers when coding enumerations — e.g. by using { AND | 1. alpha | 2. beta} instead of { AND | alpha | beta}, or by using @enumerate-numbered(...) instead of @enumerate(...). When this setting is enabled, inline enumerations will always show their number.

  • Level customizations. This setting allows you to specify how the number of each level should be formatted. Instead of using the default romanette surrounded by round parentheses (i), you can for example choose square brackets around arabic numbers [1].

Items on separate lines

The settings you see here, are identical to those of the Regular Bullets section described above. However, these settings only apply to internal bullets and happen to get formatted as real bulleted lists.

PreviousDefinitions stylingNextLocale styling

Last updated 1 year ago