1. No editing

1.1 File Extensions
.DAE, .3DM, .FBX, .SKP
Note: all file extensions should be fully capitalized

1.2 Common UI buttons
Tab, Arrow Up, Ctrl, Right-click
Note: all button names must be capitalized

1.3 External Locations:
Desktop, Control Panel

1.4 3D App names (Lumion and CAD Software)
Lumion, SketchUp, Revit, Rhino, etc.

5.2 Other Types of Apps
Windows Remote Desktop Access, Splashtop, VMWare Fusion, VMWare VDI, Citrix, XenApp, Teamviewer. Parsec, Crazy Bump, Photoshop

2. Quotations

2.1 Single quotation marks
When emphasis needs to be made on a certain word relating to a Lumion setting but is not itself a Lumion word (1) AND when quoting in-software nomenclature (2). This is rarely used, but may come handy for longer, more complex replies.

E.g: (1) Is the surface ‘marked’ as terrain?

Whereas Mark as Terrain is a Lumion phrase for a setting (pre V9).

The alternative is to use bolding (see below).

(2) Revit says Ignore interior details and I don't know what it means.

2.2 In-Software Settings - Single quotation marks
'Export edges', 'Start LiveSync', 'Triangulate all faces', 'Include texture maps'

2.3 Double quotation marks
When quoting a person.

E.g: As per your previous email, ""the power supply is 500W"". This means ...

2.4 Quote block

When using a full quote from a previous message.

E.g:

Quote from something (prev. email)

3. Articles:

3.1 Knowledge Base articles
General Format: bullet point + “Knowledge Base:” in Bold + link to KB article. E.g:

• Knowledge Base: Model import guidelines for SketchUp

3.2 Links under another name: Lumion Website / Lumion Downloads/ External Link / etc
General Format: bullet point + type of link in Bold + link to page. E.g:

• External Link: Nvidia Drivers

Links are always in the default style sheet for the template as underlined and blue.

4. Bold:

4.1 Subtitles

Optional for needed emphasis if consider based on issue, customer, and detail needed in the reply.

E.g:

Thank you for your reply. In order to fix your issue, you can try the following:

Method 1: Download the patch
Tell the customer how to do that.

Method 2: Copy and paste this file to that location
Tell the customer how to do that.

4.2 Numbering

1. This is point 1
2. This is point 2

5. Italics:

5.1 General Lumion and identifiers of objects/license types/functions except for 'Lumion'
Lumion Student Pro, Scene, Project, Lumion Support Center, License Key, Getting started with Lumion, Effects

Italics is used as the key formatting style for Ticket replies as that is the only option available (other than Bold which needs to be reserved for important or emphasis words).

Italics are reserved for Lumion-based words/phrases.

In the external Knowledge Base articles, we apply further focus formatting with bolding and font color change from black, so the bolding is less about emphasis. Those can all be controlled via CSS if we need to change the look.

Again, please note (see also 1.4) that the word 'Lumion' itself is the product or software/service and although it might seem like it should be in special Lumion-use formatting, its a name that does not need to be formatted, unless you need to add some special emphasis such as bolding (not usually needed).

There are some product objects such as Lumion Account that are by themselves the name of the account and so should be formatted in italics (for Zendesk replies and italics with bolding for external articles).

5.2 Folder Locations of Lumion
C:\Documents\Lumion 8.0

In italics because these are Lumion implicit working environment locations so in 'Lumionized' format.

5.3 Error logs and other requested files
DxDiag.txt, error.log

In italics because these are Lumion implicit working environment locations so in 'Lumionized' format.

6. Bold-Italics:

6.1 Lumion-related elements:
Photo Mode, Movie Mode, Build Mode, Change Style, Store Camera, Settings

(when referring to in-Lumion features or areas of operation/functionality)

NOTE: Only when the extra emphasis is needed otherwise they are in plain Italics

6.2 Lumion Materials or Objects
Invisible Material, 3D Grass, Billboard Material, Spotlights, Reflection Control, Nature

NOTE: Only when the extra emphasis is needed, otherwise they are in Italics

7. Text Arrows:

7.1 Used for directories or emphasizing steps: ->
Go to Settings -> Recovery -> ON

8. Text editing shortcuts in Zendesk:

 

==========================================

ARTICLE SUPPORT (from transfer to HubSpot):

1. Tables:

Tables were not able to be imported via HubSpot Importer. Any Tables in this article are now based on a DIV Conversion. Same is also the case for the transfer of articles with tables in the EKB.

You can add new (basic) Tables in the HubSpot Editor directly.

If the layout does not work, then you can copy/paste or recreate the old Table from ZD. Where possible the Table has also been copy/pasted from the source page (see link below in 3.). Instructions, see this article: Copying an old Zendesk Table over to HubSpot

2. Finding the reference to the old Zendesk Ticket in HubSpot:

Use this Support article:  Finding the reference to the old Zendesk Ticket in HubSpot

and for ZD ticket Search in HubSpot following step 1 in above article:

3. Source Zendesk article:

A source and backup copy was made of all articles 9 June 2025.

The saved HTML files and images are in subfolders of: HTML files and images subfolders.

See also Support article in 2 above.

Backup/copy article: [TR] 1.7 Support Reque... (360015784419).html

4: Quick Link to Zendesk IKB article:

(not available when Zendesk closed)

[TR] 1.7 Support Request Editing Guidelines - Zendesk Support