Text Creation & Styles — Create and format single-line and multi-line text; manage text styles - AutoCAD

SECTION 1

Historical Context & Motivation

Before computer-aided design existed, every annotation on a technical drawing was painstakingly hand-lettered using templates, Leroy lettering sets, or skilled drafting penmanship. This manual process consumed a significant fraction of a drafter's time and introduced inconsistency—two drafters rarely produced identical letterforms. When AutoCAD debuted in 1982, it included rudimentary text capabilities that immediately addressed the legibility and consistency problems inherent in manual annotation. Over four decades of development, AutoCAD's text system evolved from simple vector-font line segments into a sophisticated typographic engine supporting TrueType and SHX fonts, paragraph formatting, columns, and annotative scaling.

For computer science students, AutoCAD's text architecture is an instructive case study in how a domain-specific application manages structured document content. The system mirrors concepts familiar from CSS stylesheets—text styles function like named CSS classes, defining reusable formatting properties that decouple visual presentation from content. Understanding this separation of concerns is essential to producing maintainable, standards-compliant engineering drawings.

1982 • AutoCAD 1.0 — DTEXT Introduced

The first release of AutoCAD included the DTEXT command (Dynamic Text), which rendered single-line annotations using simple SHX vector fonts. Each character was drawn as polyline segments, keeping file sizes small on hardware with limited RAM.

1993 • Release 13 — MTEXT Arrives

AutoCAD Release 13 introduced MTEXT (Multiline Text), a paragraph-aware text object supporting word wrap, inline formatting, and multiple fonts within a single bounding box—analogous to an HTML <div> with rich content.

2000 • TrueType Font Support Matures

Full TrueType (TTF) and later OpenType (OTF) integration allowed AutoCAD users to leverage the same font libraries used in word processors and graphic design, dramatically expanding typographic options while improving print fidelity.

2008 • Annotative Scaling

AutoCAD 2008 introduced annotative scaling, enabling a single text object to appear at the correct plotted height across multiple viewports at different scales—eliminating the need to duplicate annotations for each viewport scale.

2018–Present • Cloud & Collaboration Era

Modern AutoCAD (desktop and web) features enhanced MTEXT editors with spell-check, autocorrect, column support, and cloud-based collaboration. Text styles synchronize across shared drawings, ensuring typographic consistency in team environments.

The central question this lesson addresses is both practical and architectural: how does AutoCAD separate text content from text presentation, and how can you leverage that separation to annotate drawings efficiently, consistently, and in compliance with industry standards such as ASME Y14.2 and ISO 3098?

SECTION 2

Core Principles & Definitions

AutoCAD's text system rests on a small set of foundational concepts that, once internalized, make the entire annotation workflow intuitive. At the highest level, there are two distinct text object types—single-line text (DTEXT/TEXT) and multiline text (MTEXT)—and a shared formatting abstraction called a text style. The relationship between these elements is analogous to the MVC pattern: the text style acts as a view configuration, each text object stores content (model), and the rendering engine (controller) composites them for display and plotting.

Single-Line Text (TEXT / DTEXT)

Each invocation creates an independent text entity with a single baseline. Ideal for labels, callouts, and attribute values. Equivalent to an inline <span> element—lightweight and position-precise, but lacking paragraph semantics.

Multiline Text (MTEXT)

A rich-text container with a defined bounding width. Supports word wrapping, tabs, bullets, columns, inline formatting overrides, and embedded fields. Think of it as an HTML <div> with full CSS-like styling.

Text Style

A named, reusable collection of formatting properties—font family, height, width factor, oblique angle—stored in the drawing database. Applied to text objects by reference, enabling batch updates akin to changing a CSS class definition.

SHX vs. TrueType Fonts

SHX fonts are AutoCAD's native vector-stroke fonts—compact and fast to render but limited in glyph variety. TrueType/OpenType fonts provide full Unicode coverage and hinting but increase file size. The choice affects both aesthetics and interoperability.

Annotative Property

When enabled on a text style, text objects automatically scale relative to the viewport's annotation scale, guaranteeing a consistent plotted height regardless of the viewport's zoom factor—a form of responsive design for technical drawings.

✦

KEY TAKEAWAY

Think of a text style as a CSS class for your drawing annotations. Just as a web developer defines .heading { font-family: sans-serif; font-size: 24px; } once and applies it to many elements, you define a text style once in AutoCAD and assign it to any number of text objects. Changing the style definition propagates to every text object that references it—single source of truth, zero manual search-and-replace.

SECTION 3

Visual Explanation — Text Object Architecture

Figure 1 illustrates how a Text Style (top, violet-to-cyan gradient) serves as a shared formatting definition referenced by both Single-Line Text objects (left, blue border) and Multiline Text objects (right, pink border). All entities persist in the DWG drawing database (bottom, dashed green), paralleling how a stylesheet and DOM nodes coexist in a web browser.

The diagram above captures the essential data-flow pattern. When you invoke the TEXT or MTEXT command, AutoCAD creates an entity that stores only the string content, insertion geometry, and a pointer (handle reference) to the current text style. The style record in the drawing's STYLE symbol table holds font, height, width factor, and oblique angle. This indirection means that modifying a text style's font from romans.shx to Arial instantly updates every text entity that references that style—exactly as changing a CSS rule propagates across an entire webpage without touching individual elements.

SECTION 4

How It Works — Commands & Formatting Parameters

Creating Single-Line Text

The TEXT command (alias DT for legacy DTEXT) prompts for three inputs: an insertion point, a text height (if the current style's height is set to 0), and a rotation angle. Each Enter keystroke begins a new, independent single-line text entity directly below the previous one. Pressing Enter on a blank line exits the command. Because each line is a separate entity with its own insertion point, you can move, rotate, or delete lines independently—offering granular positional control at the cost of paragraph-level coherence.

💡

Justify Options

Before specifying the insertion point, type J to access justification modes. AutoCAD offers 14 justification points including TL (Top-Left), MC (Middle-Center), BR (Bottom-Right), and A (Aligned—fitted between two points). Each justification mode changes which geometric point on the text bounding box is anchored to the specified coordinate.

Creating Multiline Text

The MTEXT command (alias MT or T) prompts you to define a rectangular text boundary by picking two diagonal corners. AutoCAD then opens the In-Place Text Editor—a WYSIWYG ribbon-based editor reminiscent of a lightweight word processor. Within this editor you can apply inline formatting overrides: bold, italic, underline, overline, stacking for fractions, color changes, font overrides, and paragraph settings such as line spacing and indentation. The underlying storage format is a variant of RTF (Rich Text Format) embedded in the DWG entity, and you can view the raw formatting codes via the editor's right-click context menu.

Text Height & Scale Relationships

PLOTTED TEXT HEIGHT

H_model = H_plotted × S

Where H_model is the text height in model space drawing units, H_plotted is the desired height on the printed sheet (typically 3/32″ or 2.5 mm for notes), and S is the drawing scale factor (e.g., 48 for a 1/4″ = 1′-0″ scale).

WIDTH FACTOR

W_actual = W_default × WidthFactor

The width factor (default 1.0) horizontally scales each glyph. A value of 0.8 compresses characters to 80% of their default width, useful for fitting annotations in tight spaces. Values above 1.0 stretch characters.

OBLIQUE ANGLE

Oblique = 0° (upright) | 15° (forward italic simulation)

The oblique angle shears character stems from vertical. An oblique angle of 15° applied to an SHX font simulates an italic effect, since SHX fonts lack native italic variants. Negative values slant characters backward.

SECTION 5

Text Style Management — Anatomy & Configuration

The STYLE command (or the Text Style Manager dialog) is where you define, modify, and organize text styles. Each style record contains a set of properties that collectively determine the visual appearance of any text entity that references it. Understanding these properties in detail is critical to producing drawings that comply with organizational and industry standards.

Figure 2 breaks down the Text Style record into three property groups: Font Settings (font name, big font for CJK support, and font style), Size & Shape (height, width factor, oblique angle), and Effects & Flags (annotative, mirroring, vertical orientation). The bottom panel shows common real-world style configurations.

A crucial design decision when configuring text styles is whether to set the Height property to a fixed value or to leave it at 0. When height is set to 0, AutoCAD prompts the user to specify a height each time a text entity is created with that style, providing flexibility at the cost of consistency. When a nonzero height is defined in the style, all text using that style adopts the stored height, and the height prompt is suppressed. In practice, most firms set height to 0 in non-annotative styles (so the user can vary it per label) and rely on annotative styles—where the plotted height is fixed—for notes and general annotations that must appear uniform.

Property	Default Value	Typical Override	Effect
`Font Name`	txt.shx	Arial / romans.shx	Determines glyph shapes; SHX is lighter, TTF is richer
`Height`	0.0000	3/32″ plotted (annotative)	0 = prompt user; nonzero = fixed height for all text
`Width Factor`	1.0	0.8 – 0.9	Compresses or stretches characters horizontally
`Oblique Angle`	0°	15°	Shears character stems; simulates italic for SHX
`Annotative`	No	Yes	Auto-scales text height relative to viewport annotation scale

Key Text Style properties and their defaults vs. typical production overrides

SECTION 6

Worked Example — Setting Up a Drawing with Text Styles

Consider a scenario in which you are creating an architectural floor plan at a scale of 1/4″ = 1′-0″ (scale factor = 48). You need three text styles: one for general notes, one for room labels, and one for drawing titles. Walk through the following steps to set up the styles, create text using each, and verify plotted heights.

Creating and Applying Text Styles for an Architectural Floor Plan

1
Step 1 — Open the Text Style Manager

Type STYLE at the command line and press Enter. The Text Style dialog opens, showing the default Standard style and any other styles already defined in the drawing template.
2
Step 2 — Create the "Notes" Style

Click New and name the style Notes. Set the font to Arial (TrueType), enable the Annotative checkbox, and set the Paper Text Height to 3/32″ (0.09375). Leave the width factor at 1.0 and oblique angle at 0°. Click Apply.

"Notes" style created: Arial, Annotative=Yes, Paper Height=3/32″.
3
Step 3 — Create the "RoomLabel" Style

Click New again and name it RoomLabel. Set the font to Arial Bold, enable Annotative, set Paper Text Height to 1/8″ (0.125). Set the width factor to 0.9 for slightly condensed characters that fit better in room-name labels.

"RoomLabel" style: Arial Bold, Annotative=Yes, Height=1/8″, Width=0.9.
4
Step 4 — Compute Model-Space Height (Verification)

Although annotative text handles scaling automatically, verify the math. For the "Notes" style at a 1:48 scale: H_model = H_plotted × S = 0.09375 × 48 = 4.5 drawing units. In model space, the text entity will display at a height of 4.5 units, but on the plotted sheet it will measure 3/32″.

H_model = 4.5 drawing units → 3/32″ on paper. ✓
5
Step 5 — Place Text Using Each Style

Set the current style to Notes via the Properties panel or the -STYLE command. Type MTEXT, define a bounding box, and type a general note such as "ALL DIMENSIONS ARE TO FACE OF STUD UNO." Close the editor. Switch the style to RoomLabel and use TEXT with Middle-Center justification to place room names like "KITCHEN" centered within each room outline.

Annotations placed: MTEXT general note placed using the "Notes" style (Arial, annotative, 3/32″ plotted height); single-line TEXT room labels placed using the "RoomLabel" style (Arial Bold, annotative, 1/8″ plotted height, width factor 0.9), each centered within its corresponding room outline using Middle-Center justification.
6
Step 6 — Verify in a Layout Viewport

Switch to a Layout tab, create a viewport at 1:48 scale, and confirm that the annotation scale matches. Both the general notes and room labels should display at their correct plotted heights—3/32″ and 1/8″ respectively—regardless of the viewport zoom level. If the annotations don't appear, check that the viewport's annotation scale is added to each text object's scale list via OBJECTSCALE.

All text displays at correct plotted height in the 1:48 viewport. Drawing is ready for plotting.

SECTION 7

Single-Line vs. Multiline Text — Strengths & Limitations

Choosing between single-line text and multiline text is not merely a matter of preference; each object type has distinct strengths that make it the correct tool for specific annotation tasks. The table below provides a systematic comparison across the dimensions that matter most in production drafting environments.

Criterion	Single-Line Text (TEXT)	Multiline Text (MTEXT)
Word Wrap	No — each entity is a single line	Yes — auto-wraps within bounding width
Inline Formatting	None — entire entity shares one style	Full — bold, italic, color, font overrides per character
Positional Control	Excellent — each line is independently movable	Moderate — entire paragraph moves as a unit
Best Use Cases	Dimension labels, attribute values, short callouts	General notes, keynotes, specifications, legal text
Columns	Not supported	Static or dynamic column flow
Field Embedding	Limited	Full field support (date, filename, sheet set data)
Performance (large drawings)	Lighter per entity; many entities add overhead	One complex entity; efficient for long blocks of text

Feature comparison between TEXT and MTEXT entity types

✦

KEY TAKEAWAY

Use single-line text (TEXT) when you need pixel-precise placement of short labels—it's the <span> of AutoCAD. Use multiline text (MTEXT) when you need paragraph semantics and rich formatting—it's the <div> with a full stylesheet. In a well-organized drawing, both coexist: MTEXT for note blocks, TEXT for point labels.

SECTION 8

Connection to Advanced Annotation — Fields, Attributes & Annotative Scaling

Text creation and styles form the base layer of AutoCAD's annotation stack. Above this layer sit more advanced features—fields, block attributes, leaders and multileaders, and tables—that all depend on text styles for their typographic behavior. Understanding this dependency tree is essential for designing drawing templates that scale across projects.

Concept	Foundation (This Lesson)	Advanced Extension
Static Text	TEXT and MTEXT with literal strings	Fields — dynamic values (date, filename, area) auto-update within MTEXT
Text Styles	Named styles with font, height, width	Dimension Styles (DIMSTYLE) reference text styles for dimension text formatting
Manual Scaling	H_model = H_plotted × S	Annotative Scaling — AutoCAD auto-computes model-space height per viewport scale
Standalone Text	Freestanding text entities	Block Attributes — text stored as metadata within block definitions, queryable via data extraction
Plain Annotations	Notes placed directly in the drawing	Multileaders (MLEADER) — text attached to leader lines with arrowheads for callout workflows

How foundational text concepts extend into advanced AutoCAD annotation features

For computer science students accustomed to thinking in layers of abstraction, the key insight is that AutoCAD's annotation system mirrors a class hierarchy. The TextStyle object is a shared base configuration. TEXT and MTEXT entities are concrete instances that reference the style. Advanced features like DIMSTYLE and MLEADERSTYLE compose (rather than inherit from) text styles, adding dimension-specific or leader-specific properties atop the typographic base. Mastering the base layer—text creation and style management—gives you leverage over the entire annotation stack.

SECTION 9

Practice Problems

Question 1: CONCEPTUAL

Explain the relationship between a text style and a text entity in AutoCAD. Why does AutoCAD use this indirection rather than embedding all formatting directly in each text object? Draw an analogy to a concept from software engineering.

Show answer

A text style is a named, reusable definition of formatting properties (font, height, width factor, oblique angle) stored in the drawing's symbol table. Text entities (TEXT or MTEXT) reference a style by name rather than storing their own copy of every formatting parameter. This is analogous to the separation of concerns in CSS—a stylesheet class defines appearance once, and many HTML elements reference it. The benefit is consistency and maintainability: changing the font in a text style automatically updates all text entities that reference it, eliminating the need to modify each entity individually. Without this indirection, a drawing with hundreds of annotations would require tedious, error-prone manual updates whenever the project's typographic standards changed.

Question 2: BASIC CALCULATION

A mechanical drawing is plotted at a scale of 1:20 (scale factor = 20). You want general notes to appear at 2.5 mm tall on the printed sheet. If you are NOT using annotative scaling, what text height should you specify in model space when placing the MTEXT entity?

Show answer

Using the formula H_model = H_plotted × S, substitute the known values: H_model = 2.5 mm × 20 = 50 mm. You should specify a text height of 50 mm in model space. When the drawing is plotted at 1:20, the text will be reduced by a factor of 20, yielding the desired 2.5 mm printed height. If annotative scaling were enabled, you would simply set the paper text height to 2.5 mm and AutoCAD would perform this multiplication automatically for each viewport scale.

Question 3: INTERMEDIATE

You have a drawing with 150 general note annotations using an MTEXT entity and a style called "Notes" set to romans.shx. The client now requires all notes to use the Arial TrueType font. Describe the most efficient method to update all 150 annotations. What potential side effect should you anticipate after the font change, and how would you address it?

Show answer

The most efficient method is to open the Text Style Manager (STYLE command), select the "Notes" style, change the font from romans.shx to Arial, and click Apply. Because all 150 MTEXT entities reference the "Notes" style by name, they will immediately update to display in Arial—no manual editing of individual entities is needed. The potential side effect is that SHX and TrueType fonts have different character metrics (glyph widths, descender depths, and line spacing). After switching to Arial, some MTEXT bounding boxes may overflow or show excessive whitespace. You should review the drawing for text overflow (indicated by a small triangle at the bottom of an MTEXT frame) and adjust bounding box widths or the style's width factor accordingly. Running the REGEN command ensures all text entities are re-rendered with the new font metrics.

Question 4: APPLIED

You are setting up a drawing template for a civil engineering firm. The template must support three viewport scales—1:100, 1:200, and 1:500—in a single layout. Design a text style configuration for general notes that ensures a consistent 2 mm plotted height across all three viewports. Specify the style name, font, height setting, annotative flag, and explain how AutoCAD handles the scaling in each viewport.

Show answer

Create a style named "CivilNotes" with font set to Arial, the Annotative property enabled, and the Paper Text Height set to 2 mm. Leave the model-space height at 0 (AutoCAD manages it via the annotative mechanism). When a text entity using this style is placed in model space, AutoCAD creates scale representations for each annotation scale assigned to the entity. In the 1:100 viewport, the text displays at 2 × 100 = 200 mm in model space; in the 1:200 viewport, at 2 × 200 = 400 mm; in the 1:500 viewport, at 2 × 500 = 1000 mm. Despite the different model-space sizes, each viewport's scaling ensures the text plots at exactly 2 mm. To activate this, set the ANNOAUTOSCALE system variable to the desired behavior (e.g., 4 to add scales automatically) and ensure each viewport's annotation scale matches its zoom scale. The result is a single text entity that appears correctly in all three viewports without duplication.

Question 5: CRITICAL THINKING

AutoCAD stores MTEXT formatting as embedded RTF-like control codes (e.g., \fArial|b1|i0; for Arial Bold). Discuss the trade-offs of this design choice compared to alternatives such as storing formatting in a separate sidecar data structure (like CSS in a separate file) or using a fully semantic markup language (like HTML). Consider interoperability, file size, editability, and round-trip fidelity.

Show answer

AutoCAD's embedded RTF-like control codes represent a self-contained approach: all formatting travels inline with the text content within the DWG entity, guaranteeing that any application reading the entity can reconstruct the visual appearance without needing to resolve external references. This maximizes round-trip fidelity and simplifies the file format—there is no risk of a missing stylesheet breaking annotation rendering. However, this design sacrifices separation of concerns: formatting and content are tightly coupled, making batch style changes more complex than a CSS-like model where changing one rule updates all referencing elements. AutoCAD partially mitigates this through text styles (which function as a base stylesheet), but inline overrides still embed formatting in the entity data. A fully semantic markup approach (like HTML with CSS) would offer cleaner separation but would require a rendering engine capable of parsing and compositing structured markup—adding complexity and potential parsing errors. In terms of file size, inline codes are compact but redundant across many entities; an external stylesheet would be more space-efficient for large drawings with consistent formatting. The trade-off AutoCAD chose—styles for shared defaults plus inline codes for overrides—mirrors real-world CSS usage (external classes + inline style attributes) and represents a pragmatic middle ground optimized for engineering workflows where file portability and deterministic rendering take precedence over stylistic flexibility.

SUMMARY

Summary

AutoCAD provides two fundamental text entity types: single-line text (TEXT/DTEXT) for lightweight, independently positionable labels, and multiline text (MTEXT) for rich, paragraph-aware annotation blocks with word wrap, inline formatting, and column support. Both entity types derive their base formatting from text styles—named records stored in the drawing's symbol table that define font family, height, width factor, oblique angle, and the annotative flag. This separation of content from presentation—analogous to CSS classes in web development—enables batch updates and ensures typographic consistency across large drawing sets.

The plotted text height formula (H_model = H_plotted × S) governs manual scaling, while annotative scaling automates this relationship, ensuring consistent text sizes across multiple viewports at different scales. Text styles serve as the foundation for AutoCAD's broader annotation system, feeding into dimension styles, multileader styles, and table styles. Mastering text creation and style management establishes the architectural foundation upon which all professional drawing annotation is built.