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
  • Why you may not want to use custom fonts
  • How to use custom fonts in ClauseBase
  • Step 1: Create a .DOCX file with one or more embedded fonts
  • Step2: Upload the .DOCX file
  • Step 3: Reference the .DOCX file
  • Step 4: Specify the font to use
Export as PDF
  1. Styling
  2. How to: styling

Using custom fonts

PreviousHow to: stylingNextChange bullet styling

Last updated 1 year ago

ClauseBase offers a variety of standard fonts — such as Arial, Times New Roman and Verdana — from which you can choose in various places relating to styling. However, sometimes this is not enough, and you insist on using custom fonts.

Why you may not want to use custom fonts

Fonts seem like an easy topic for most users, but actually have many delicate issues attached to them:

A font file must be available on the document’s recipient computer, otherwise the document will look and print differently on the recipient’s computer — which may vary from usually negligble (slightly different spacing of letters and paragraphs) to downright problematic (certain letters are replaced by empty rectangles or weird characters). The font availability can be achieved in two different ways:

  • Either the font file is installed on the device. This will be almost guaranteed to be the case for the truly standard fonts (Times New Roman and Arial). It will usually also true for secondary fonts (such as Verdana and Courier), but you should not expect it to be true for other fonts. Be aware that, while installing a font is not a difficult operation, font installation is actively disabled on many corporate Windows desktops and laptops — i.e., the IT department must intervene. In any case, asking a user to install a certain font is not exactly polite. However, if a . DOCX/.PDF file will only be used internally, and a special font is part of the company/firm’s branding, then it can be safe to assume that that special font was indeed pre-installed on all the recipients’ computers.

  • Or the the font file is embedded into the .DOCX / .PDF file. The advantage is that no installation is necessary at all, but the disadvantage is that the size of the file will increase enormously — a simple 50 KB .DOCX or .PDF file can easily blow up to more than 1 MB if the regular, bold and italic versions of a single font are being embedded.

It is therefore advisable to stick to the standard fonts, only use custom fonts for strictly internal documents (i.e., when you can assume that the font-file was pre-installed), and very exceptionally use custom fonts if there really is no other way.

How to use custom fonts in ClauseBase

Step 1: Create a .DOCX file with one or more embedded fonts

In order to use a custom font in your documents, you should first create a .DOCX file that contains an embedded version of that font.

To do so in Microsoft Word, please check .

Step2: Upload the .DOCX file

Next, you should upload the created .DOCX file to some location in the ClauseBase file system. If other users (in particular anonymous users) will need to access the same file, then make sure the file is in a shared location, e.g. your organisation’s or department’s library.

Step 3: Reference the .DOCX file

Each time you want to actually use the font, you need to reference the .DOCX file in the “Custom fonts” section of the Page stying:

Step 4: Specify the font to use

At the location where you want to use the custom font, you should reference it explicitly by choosing “(Custom font…)” in the fonts dropdown list. For example, in the screenshot below, we are selecting custom font “Bainsley”:

Be aware that when this font is not installed on your end-user’s device, the user will not see the actual custom font on his/her screen, but Arial instead. When creating a .PDF or .DOCX file, however, the custom font will be embedded and therefore show up in his/her MS Word or PDF reading application.

Microsoft’s instructions