TPS Format Specification (TelePrompterScript)

What is TPS?

TPS (TelePrompterScript) is a markdown-based file format for teleprompter scripts. It supports hierarchical content organization with precise timing, emotional cues, delivery instructions, and presentation control.

Motivation

Teleprompter scripts need more than plain text. A speaker needs pace guidance, emotional cues, visual emphasis, and natural pauses — all embedded directly in the script. Existing formats (plain text, SubRip .srt, WebVTT) either lack structure entirely or focus on subtitle timing rather than live presentation flow.

TPS bridges this gap: it is human-readable markdown that any text editor can open, yet it carries rich metadata that teleprompter software can interpret for real-time rendering.

Target Audience

• Script authors — writers who create teleprompter scripts and want inline pace/emotion control without leaving a text editor.
• Teleprompter app developers — engineers who parse and render TPS files in real-time reading applications.
• Content producers — video/podcast teams who need structured, reviewable scripts with edit points and timing hints.

Design Goals

1. Markdown-compatible — a .tps file renders reasonably in any markdown viewer.
2. Human-authorable — no tooling required to write a valid script.
3. Hierarchical — documents decompose into Segments → Blocks → Phrases → Words, each level inheriting and overriding properties.
4. Minimal yet extensible — the core tag set is small; parsers ignore unknown tags gracefully.

Glossary

Term	Definition
Script	The entire TPS document, including front matter and all content.
Front Matter	YAML metadata block delimited by --- at the top of the file.
Segment	A major section (## header) — e.g., Intro, Problem, Solution.
Block	A topic group (### header) within a segment.
Phrase	A sentence or thought within a block, delimited by sentence-ending punctuation or pause markers.
Word	An individual token with optional per-word properties (emphasis, volume, pause).
WPM	Words Per Minute — the reading speed.
Edit Point	A marker indicating a natural place to stop or start an editing session.
Emotion	A predefined delivery style that controls tone, energy, and visual presentation.

File Structure

Script
├── Front Matter (YAML metadata)
├── Title (# header — optional, informational only)
└── Segments (## headers — major sections)
    └── Blocks (### headers — topic groups within segments)
        └── Phrases (sentences/thoughts with inline markers)
            └── Words (with individual properties)

Title (# Level)

An optional # header immediately after the front matter. It serves as the document title for display purposes. Parsers should treat it as metadata — it does not create a segment or affect WPM/emotion inheritance. If omitted, the title field from the front matter is used instead. If both are present, the # header takes precedence for display.

Format Specification

Front Matter (YAML)

The front matter is a YAML block delimited by --- lines at the very start of the file. All fields are optional.

---
title: "Script Title"
profile: Actor              # Actor (default)
duration: "10:00"           # Target duration MM:SS
base_wpm: 140               # Default words per minute
speed_offsets:              # Percentage offsets for speed tags relative to base_wpm
  xslow: -40                # [xslow] = base_wpm × 0.6 (40% slower)
  slow: -20                 # [slow] = base_wpm × 0.8 (20% slower)
  fast: 25                  # [fast] = base_wpm × 1.25 (25% faster)
  xfast: 50                 # [xfast] = base_wpm × 1.5 (50% faster)
author: "Author Name"
created: "2024-01-01"
version: "1.0"
---

Field	Type	Default	Description
title	string	—	Human-readable script title.
profile	string	Actor	Actor for natural spoken reading from a teleprompter.
duration	string	—	Target duration in MM:SS format.
base_wpm	integer	140	Default reading speed (words per minute) for the entire document.
speed_offsets.xslow	integer	-40	Percentage offset for [xslow]...[/xslow] tags. Default -40 means 60% of base speed.
speed_offsets.slow	integer	-20	Percentage offset for [slow]...[/slow] tags. Default -20 means 80% of base speed.
speed_offsets.fast	integer	25	Percentage offset for [fast]...[/fast] tags. Default 25 means 125% of base speed.
speed_offsets.xfast	integer	50	Percentage offset for [xfast]...[/xfast] tags. Default 50 means 150% of base speed.
author	string	—	Script author name.
created	string	—	Creation date (ISO 8601).
version	string	—	Document version.

Segments (## Level)

Segments are major sections of the script.

## [SegmentName|120WPM|Emotion|Timing]

All parameters after the name are optional, separated by |. Parameters are identified by format, not by position:

• An integer (or integer + WPM suffix) → WPM
• A known emotion keyword → Emotion
• A time pattern (MM:SS or MM:SS-MM:SS) → Timing
• Speaker:Name → Speaker (for multi-talent scripts)

This means parameters can appear in any order and unneeded ones can simply be omitted — no empty || slots required.

Examples:

• ## [Intro|Warm] — inherits base WPM, sets emotion
• ## [Urgent Update|145WPM|Urgent|0:30-1:10] — overrides WPM, sets emotion and timing
• ## [Overview|Neutral] — inherits WPM, sets emotion
• ## [Simple Segment] — name only, inherits everything

Segment Parameters:

Parameter	Format	Description
Name	free text	Human-readable label shown in editors. Required (first value before the first |).
WPM	NNN or NNNWPM	Integer speed override. Omit to inherit.
Emotion	preset name	Emotion preset (see table below). Omit to inherit (defaults to Neutral at document level).
Timing	MM:SS or MM:SS-MM:SS	Duration hint. Stored for tooling; playback computes timing from word counts.
Speaker	Speaker:Name	Talent assignment for multi-speaker scripts. Omit for single-speaker.

Leading text: Content between a segment header and its first block is preserved as introductory text that inherits the segment's speed and emotion.

Blocks (### Level)

Blocks are topic groups within a segment.

### [BlockName|120WPM|Emotion]

Examples:

• ### [Opening Block] — inherits segment WPM and emotion
• ### [Speed Variations|Focused] — inherits WPM, overrides emotion
• ### [Key Stats|130WPM] — overrides WPM, inherits emotion
• ### [Climax|150WPM|Urgent] — overrides both

Block Parameters:

Parameter	Format	Description
Name	free text	Descriptive label. Required (first value before the first |).
WPM	NNN or NNNWPM	Integer speed override. Inherits segment WPM if omitted.
Emotion	preset name	Emotion override. Inherits segment emotion if omitted.
Speaker	Speaker:Name	Talent assignment. Inherits segment speaker if omitted.

Inline Markers

Inline markers are embedded within phrase text to control presentation.

Pauses

[pause:2s]          # 2-second pause
[pause:1000ms]      # 1000-millisecond pause
/                   # Short pause (300ms)
//                  # Medium pause (600ms)

Emphasis

[emphasis]word[/emphasis]    # Standard emphasis (level 1)
*word*                       # Markdown italic → emphasis level 1
**word**                     # Markdown bold → emphasis level 2

Speed Changes

[150WPM]text here[/150WPM]    # Temporary absolute speed change
[xslow]very careful[/xslow]   # Relative: base_wpm × 0.6 (40% slower than base)
[slow]important point[/slow]   # Relative: base_wpm × 0.8 (20% slower than base)
[fast]quick mention[/fast]     # Relative: base_wpm × 1.25 (25% faster than base)
[xfast]rapid section[/xfast]   # Relative: base_wpm × 1.5 (50% faster than base)
[normal]reset speed[/normal]   # Reset to base_wpm (multiplier = 1.0)

Speed tag summary (at base_wpm = 140):

Tag	Multiplier	Effective WPM
[xslow]	0.6×	84
[slow]	0.8×	112
[normal]	1.0×	140
[fast]	1.25×	175
[xfast]	1.5×	210

Note: All relative speed tags are relative to the base speed, not absolute values. The multiplier is calculated as 1 + (offset / 100). For example, slow with offset -20 → multiplier 1 + (-20/100) = 0.8. Tags stack multiplicatively when nested: [xslow][slow]text[/slow][/xslow] = base × 0.6 × 0.8 = 48% of base.

Runtime Speed Control

The +/− buttons on the reading page change the base speed for the current run. All relative speed tags ([xslow], [slow], [fast], [xfast]) automatically scale with the new base, preserving their proportional relationship. For example, pressing + to increase from 140 to 150 WPM means [slow] changes from 112 to 120 WPM.

Volume

[loud]important announcement[/loud]       # Louder delivery
[soft]gentle aside[/soft]                 # Softer, quieter delivery
[whisper]secret or intimate[/whisper]     # Whispered delivery

Volume tags control the intended loudness of delivery. Renderers should visually distinguish volume levels (e.g., larger/bolder text for [loud], smaller/lighter for [soft], styled differently for [whisper]).

Highlighting

[highlight]key point[/highlight]    # Visual highlighting (background overlay)

highlight is a visual formatting tag — it applies a semi-transparent background overlay to make text stand out on the teleprompter. It does not imply a specific delivery change.

Emotion Styling

[warm]friendly greeting[/warm]      # Apply emotion-based styling inline
[urgent]breaking news[/urgent]      # Inline emotion override

Breath Marks

[breath]                            # Natural breath point

A breath mark indicates where the speaker should take a breath. Unlike pauses, breath marks do not add time — they guide the reader to breathe naturally at that point. Useful in long passages where phrasing might otherwise cause the reader to run out of air.

Edit Points

[edit_point:high]                   # High priority edit point
[edit_point:medium]                 # Medium priority edit point
[edit_point]                        # Standard edit point (no priority)

Pronunciation Guides

[phonetic:ˈkæməl]camel[/phonetic]              # IPA pronunciation
[pronunciation:KAM-uhl]camel[/pronunciation]    # Simple guide

Syllable Stress

Inline wrap — wrap the stressed part of a word:

develop[stress]me[/stress]nt        # Stress on "me"
[stress]in[/stress]frastructure     # Stress on "in"

The tag can wrap a single letter or a syllable. Renderers should visually distinguish the stressed portion (e.g., larger font size, underline, or bold).

Stress guide — full syllable breakdown with a parameter:

[stress:de-VE-lop-ment]development[/stress]
[stress:IN-fra-struc-ture]infrastructure[/stress]

Hyphens separate syllables. The stressed syllable is UPPERCASE, unstressed are lowercase. Renderers should display the guide as a tooltip or overlay — not replace the word. Use this for complex or unfamiliar words where the reader needs the full pronunciation map.

Delivery Mode Tags

[sarcasm]Oh, that went really well[/sarcasm]         # Say the opposite of what you mean
[aside]By the way, we also support webhooks[/aside]  # Parenthetical, "to the audience"
[rhetorical]Isn't that exactly what we need?[/rhetorical]  # Question delivered as statement
[building]Each phrase gets bigger. And bigger. And BIGGER.[/building]  # Gradually rising energy

Delivery mode tags describe how to deliver a passage, beyond emotion and volume:

Tag	Delivery	Use when
[sarcasm]	Say it straight, but mean the opposite. Deadpan or exaggerated.	Comedy, skepticism, irony.
[aside]	Step out of the main narrative. Lower energy, more intimate.	Parenthetical comments, tangents, notes to audience.
[rhetorical]	Deliver as a statement with question syntax. No rising intonation.	Rhetorical questions that don't expect answers.
[building]	Start at lower energy, gradually increase through the passage.	Reveals, motivational build-ups, crescendo moments.

Speaker Tags

For multi-talent scripts, mark who reads each section:

## [Interview|Warm|Speaker:Alex]

### [Question|Speaker:Jordan]
So tell us about the project. //

### [Answer|Speaker:Alex]
We started with a simple idea. //

The Speaker:Name parameter is added to segment or block headers using the same |-separated syntax. The parser identifies it by the Speaker: prefix. Renderers should visually distinguish speakers (e.g., different text colors or labels).

Keyword Reference

Emotions (case-insensitive)

Emotions are a closed set — parsers must reject unknown emotion keywords. Each emotion describes a delivery style that affects how the speaker reads the text: tone of voice, energy level, and pacing feel.

Keyword	Delivery	Typical pacing	Use when
neutral	Even, balanced tone. No particular emotional coloring.	Steady	Default. Informational content, transitions.
warm	Friendly, approachable. Slight smile in the voice.	Relaxed	Greetings, introductions, audience connection.
professional	Formal, authoritative. Clear articulation.	Measured	Business content, reports, official statements.
focused	Concentrated, precise. Each word matters.	Deliberate	Technical details, step-by-step instructions.
concerned	Worried, empathetic. Lower energy, careful tone.	Slower	Problems, risks, bad news, sensitive topics.
urgent	High alert, immediate attention. Tense, direct.	Faster	Breaking news, critical warnings, deadlines.
motivational	Inspiring, encouraging. Building energy.	Building	Calls to action, closing statements, rallying.
excited	Enthusiastic, high energy. Wider pitch range.	Faster	Announcements, reveals, good news.
happy	Joyful, positive. Light and upbeat.	Relaxed	Celebrations, positive results, thank-yous.
sad	Somber, reflective. Lower pitch, slower.	Slower	Loss, disappointment, memorial.
calm	Peaceful, reassuring. Steady and even.	Slow	De-escalation, meditation, closing thoughts.
energetic	Dynamic, high tempo. Punchy delivery.	Fast	Demos, action sequences, rapid-fire content.

Renderers map each emotion to a visual style (colors, background, text treatment) appropriate for the rendering context. The exact visual representation is implementation-defined, but should be consistent and distinguishable.

Volume Levels

Keyword	Description
loud	Louder, more projected delivery
soft	Quieter, gentler delivery
whisper	Whispered, intimate delivery

Delivery Modes

Delivery modes are a closed set — parsers should treat unknown delivery mode keywords as unknown tags (see Error Handling).

Keyword	Delivery	Use when
sarcasm	Say it straight, but mean the opposite. Deadpan or exaggerated.	Comedy, skepticism, irony.
aside	Step out of the main narrative. Lower energy, more intimate.	Parenthetical comments, tangents, notes to audience.
rhetorical	Deliver as a statement with question syntax. No rising intonation.	Rhetorical questions that don't expect answers.
building	Start at lower energy, gradually increase through the passage.	Reveals, motivational build-ups, crescendo moments.

Inline Tags

Tag	Syntax	Description
Pause	[pause:Ns] or [pause:Nms]	Pause for N seconds/milliseconds
Short pause	/	300ms pause
Medium pause	//	600ms pause
Emphasis	[emphasis]text[/emphasis]	Standard emphasis (level 1)
Markdown emphasis	*text*	Converted to emphasis level 1
Strong emphasis	**text**	Converted to emphasis level 2
Highlight	[highlight]text[/highlight]	Visual highlighting
Speed (absolute)	[NWPM]text[/NWPM]	Temporary absolute speed change (e.g., [150WPM])
Speed (preset)	[xslow]text[/xslow]	Extra slow: base × 0.6
Speed (preset)	[slow]text[/slow]	Slow: base × 0.8
Speed (preset)	[fast]text[/fast]	Fast: base × 1.25
Speed (preset)	[xfast]text[/xfast]	Extra fast: base × 1.5
Speed (reset)	[normal]text[/normal]	Reset to base speed: base × 1.0
Edit point	[edit_point] or [edit_point:priority]	Mark edit location
Loud	[loud]text[/loud]	Louder, projected delivery
Soft	[soft]text[/soft]	Quieter, gentler delivery
Whisper	[whisper]text[/whisper]	Whispered delivery
Phonetic	[phonetic:IPA]text[/phonetic]	IPA pronunciation guide
Pronunciation	[pronunciation:guide]text[/pronunciation]	Simple pronunciation guide
Stress (wrap)	develop[stress]me[/stress]nt	Stressed part of a word
Stress (guide)	[stress:de-VE-lop-ment]word[/stress]	Full syllable breakdown
Breath	[breath]	Natural breath point (no added time)
Sarcasm	[sarcasm]text[/sarcasm]	Deadpan/ironic delivery
Aside	[aside]text[/aside]	Parenthetical, "to the audience"
Rhetorical	[rhetorical]text[/rhetorical]	Question delivered as statement
Building	[building]text[/building]	Gradually rising energy/crescendo
Emotion	[warm]text[/warm], [urgent]...[/urgent], etc.	Inline emotion override (see Emotions table)

Speed Presets

All speed presets are relative to base_wpm — they apply a multiplier, not an absolute value.

Preset	Multiplier	Effect at base 140	Usage
xslow	0.6×	84 WPM	Very careful delivery, critical warnings
slow	0.8×	112 WPM	Important points, emphasis
fast	1.25×	175 WPM	Quick mentions, asides
xfast	1.5×	210 WPM	Rapid transitions, low-importance text
normal	1.0×	140 WPM	Reset to base speed

Edit Point Priorities

Priority	Usage
high	Critical edit points, must review
medium	Important but not critical
(none)	Standard edit point

Escape Sequences

Sequence	Result	Usage
\[	[	Literal bracket in text
\]	]	Literal bracket in text
|	`	`
\/	/	Literal slash (not a pause)
\*	*	Literal asterisk (not emphasis)
\\	\	Literal backslash

Parsing Rules

Inheritance

Properties flow downward through the hierarchy. Each level can override its parent:

1. Front matter sets document-level defaults (base_wpm, speed_offsets).
2. Segment overrides document defaults for WPM, emotion.
3. Block overrides segment defaults for WPM, emotion.
4. Inline tags override block defaults for the tagged span only.

If a child omits a value, it inherits from its nearest ancestor.

Best practice: Only specify WPM or emotion when they differ from the inherited value. If base_wpm is 140 and a segment runs at 140 WPM, omit the WPM parameter — ## [Intro|Warm] not ## [Intro|140WPM|Warm]. Similarly, if a block's emotion matches its parent segment, omit it — ### [Details] not ### [Details|140WPM|Warm]. Redundant declarations add noise and make overrides harder to spot.

WPM Resolution

For any word, the effective WPM is determined by (highest priority first):

1. Inline speed tag ([150WPM]...[/150WPM], [xslow], [slow], [normal], [fast], [xfast])
2. Block header WPM
3. Segment header WPM
4. base_wpm from front matter
5. Default: 140 WPM

Pause Handling

• / inserts a 300ms pause at the word boundary.
• // inserts a 600ms pause at the word boundary.
• [pause:Ns] inserts N×1000 ms pause.
• [pause:Nms] inserts N ms pause.
• Pauses at word boundaries are additive if multiple markers appear together.

Emotion Transitions

When emotion changes between segments or blocks, renderers should apply a smooth visual transition (recommended: 3-second fade between color schemes).

Tag Precedence

Emotion: When inline emotion tags are nested, the innermost tag wins for the enclosed span. Block-level emotion serves as the default styling; inline emotion tags override it for their span only.

Volume vs. emotion: Volume and emotion are independent dimensions. [soft] inside an Urgent block means: deliver with urgent tone but at lower volume. They do not conflict — volume controls loudness, emotion controls tone.

Delivery modes ([sarcasm], [aside], [rhetorical], [building]) override the current emotion for their span. They are specialized delivery instructions that take priority over the block emotion.

Volume + delivery modes: Volume tags apply independently to delivery modes. [building][loud]text[/loud][/building] starts at loud volume and gradually increases energy while maintaining the loud level. Volume controls loudness; delivery modes control the shape of delivery.

Phrase Boundaries

A phrase is a unit of text delimited by:

• Sentence-ending punctuation: . ? !
• Pause markers: /, //, [pause:...]
• Block or segment boundaries

Phrases are the smallest unit for timing calculation.

WPM word counting is performed on clean text — after all tags and markup are stripped. The parser first removes all tag syntax ([tag], [/tag], [tag:param]), then joins any text fragments split by mid-word tags (e.g., develop[stress]me[/stress]nt → development), then counts words using whitespace tokenization. Each whitespace-separated token in the clean text counts as one word. Hyphenated words (e.g., state-of-the-art) count as one word.

Tag Nesting

• Tags must be properly closed: [loud]text[/loud].
• Tags must not cross-nest: [loud][emphasis]text[/loud][/emphasis] is invalid.
• Valid nesting: [loud][emphasis]text[/emphasis][/loud].
• If a tag is never closed, the parser should implicitly close it at the end of the current block.

Nested Speed Resolution

When speed tags are nested, relative tags ([slow], [fast], etc.) stack multiplicatively against the base speed — not against each other:

• [slow]text[/slow] = base × 0.8
• [xslow][slow]text[/slow][/xslow] = base × 0.6 × 0.8 = base × 0.48

When an absolute speed tag ([150WPM]) contains a relative tag, the absolute value becomes the new base for the inner tag:

• [150WPM][slow]text[/slow][/150WPM] = 150 × 0.8 = 120 WPM

Content Without Segments

If a TPS file has no ## segment headers, the entire content (after front matter) is treated as a single implicit segment with Neutral emotion and default WPM.

Simple Headers

Plain markdown ## Title and ### Title headers (without [...] brackets) are also recognized as segments and blocks respectively, with default (neutral) emotion and inherited WPM.

Rendering Principles

A TPS file is source markup, not display output. The teleprompter application must process the markup and present clean, styled text to the reader. The reader should never see raw tags like [emphasis] or [slow] on screen.

Tag Visibility

All tags ([emphasis], [slow], [loud], [sarcasm], etc.) are invisible in the rendered output. The renderer applies their effects visually:

• [emphasis]word[/emphasis] → the word appears bold or in a distinct color
• [slow]text[/slow] → text may appear with a pacing indicator or wider spacing
• [loud]text[/loud] → text appears larger or bolder
• [whisper]text[/whisper] → text appears smaller or lighter
• [sarcasm]text[/sarcasm] → text styled with a distinct visual cue (e.g., italic + indicator)
• [building]text[/building] → text may gradually increase in size or intensity
• [breath] → a small visual indicator (e.g., a subtle mark or gap)
• Segment/block headers → rendered as section dividers, not raw markdown

The reader sees only the spoken text with visual styling applied. Tags are commands for the renderer, not content for the speaker.

Content Guidelines

TPS scripts contain spoken text only. Authors should avoid including non-spoken content. Parsers treat everything as plain text — these are authoring guidelines, not parsing constraints.

• URLs or hyperlinks — not spoken content; rewrite as "visit our website" or similar
• Code blocks or technical syntax — rewrite as spoken language
• Images or embedded media references — describe verbally instead
• Raw data tables — narrate the data instead

Rendering Context

TPS is designed for teleprompter use — text is always rendered on a dark background (typically near-black: #1A1B2E or similar). All visual choices assume this context.

Visual Rendering Hints

Renderers should use text size, letter spacing, weight, and animation to communicate delivery cues without the reader needing to see tags. Recommended visual mappings:

Tag	Font size	Letter spacing	Weight	Other
[loud]	Larger (120–140%)	Normal	Bold	—
[soft]	Smaller (80–90%)	Normal	Light	Lower opacity
[whisper]	Smaller (70–80%)	Wider (+1–2px)	Light	Italic or distinct style
[emphasis]	Normal	Normal	Bold	—
[stress] (wrap)	Larger on stressed part	Normal	Bold	Underline or distinct color
[stress:...] (guide)	Normal	Normal	Normal	Tooltip/overlay with syllable guide
[slow]	Normal	Wider (+1–2px)	Normal	Stretches word visually
[fast]	Normal	Tighter (-0.5–1px)	Normal	Compresses word visually
[building]	Gradually increasing	Normal	Gradually bolder	Animated size ramp
[sarcasm]	Normal	Normal	Normal	Italic + visual indicator
[aside]	Smaller (85–90%)	Normal	Light	Dimmed or offset
[highlight]	Normal	Normal	Normal	Background overlay

These are recommendations, not requirements. Renderers may adapt the visual treatment to their platform. The key principle: the reader should feel the delivery instruction from the visual presentation alone.

Dark Background Rules

1. Text base color is white/light (#F8F9FA or similar).
2. Minimum contrast — all styled text must produce at least WCAG AA 4.5:1 contrast ratio against the dark background.
3. Emotion color schemes (background, text, accent) are pre-defined per emotion and tuned for the dark rendering context.
4. highlight uses a semi-transparent yellow background overlay, not a text color change.

WPM Guidelines

Actor Profile (Spoken Reading)

The Actor profile targets natural spoken delivery — reading aloud from a teleprompter while maintaining eye contact with the camera.

Use Case	WPM Range	Recommendation
Slow, formal (news anchor, legal)	100–130	Clear diction, long pauses between phrases
Standard teleprompter	130–160	Comfortable for most speakers
Conversational / podcast	150–170	Natural speech rhythm
Fast presentation (pitch, TED)	170–200	Experienced speakers only

Default base_wpm: 140 — sits in the middle of the standard range. Most people read comfortably at 130–150 WPM from a teleprompter.

Duration formula: phrase_duration_ms = (word_count / effective_wpm) × 60000. Total duration is the sum of all phrase durations plus all pause durations.

Advice for script authors:

• Start at 130 WPM for new speakers, increase gradually.
• Use [xslow]...[/xslow] for critical warnings or very important statements.
• Use [slow]...[/slow] for key points and emotional moments.
• Use [fast]...[/fast] for asides and throwaway lines.
• Use [xfast]...[/xfast] for rapid transitions or low-importance filler.
• Add / pauses between clauses; // between sentences.

Profiles and Validation

Validation Requirements

Rule	Value
WPM error range	< 80 or > 220
WPM warning range	< 90 or > 200
Recommended WPM	130–160
Segment/Block WPM	Single integer
Inline speed	Integer, respects allowed range

Additional validation:

• Emotions must be from the predefined closed set (see Emotions table). Unknown emotion keywords are a parse error.
• Timing calculations should not exceed target duration by > 20%.
• All markup tags must be properly closed; no cross-nesting.
• Edit points should be at phrase or block boundaries.
• Pronunciation guides should use valid IPA or phonetic notation.

Casing, Whitespace, Escaping

• Tags are case-insensitive; canonical form is lower-case (e.g., [emphasis]).
• WPM suffix is uppercase by convention (e.g., 140WPM). 140wpm is also valid — parsers should normalize.
• Parameters inside headers are trimmed; 140 WPM normalizes to 140WPM.
• Escape reserved characters in plain text with backslash: \[, \], \|, \/, \*, \\.
• Escape sequences apply only in plain text, not inside tag parameters or header parameters.

Error Handling

Parsers should handle invalid input gracefully:

• Unknown tag: Treat as plain text (display the brackets and content literally).
• Unknown emotion keyword: Parse error. Reject the keyword and use the inherited emotion.
• Unclosed tag: Implicitly close at the end of the current block (see Tag Nesting).
• Closing tag without opening: Ignore the closing tag.
• Invalid WPM (< 80 or > 220): Parse error. Use the inherited WPM value.
• Malformed pause (e.g., [pause:abc]): Treat as plain text.
• Cross-nested tags: Parse error. The parser should close tags in order and report a warning.
• Duplicate parameters in headers (e.g., two WPM values): Use the last one.

Complete Example

---
title: Product Launch
profile: Actor
base_wpm: 140
speed_offsets:
  xslow: -40
  slow: -20
  fast: 25
  xfast: 50
author: Jane Doe
---

# Product Launch

## [Intro|Warm]

### [Opening Block]
Good morning everyone, / and [emphasis]welcome[/emphasis] to what I believe /
will be a [emphasis]transformative moment[/emphasis] for our company. //

[pause:2s]

### [Purpose Block|145WPM]
[emphasis]Today[/emphasis], / we're not just launching a product – / [breath]
we're introducing a [highlight]solution[/highlight] that will [emphasis]revolutionize[/emphasis] /
how our customers interact with tech[stress]no[/stress]logy. //

## [Problem|135WPM|Concerned]

### [Statistics Block|Neutral]
But first, / let's address the [xslow]elephant in the room[/xslow]. /
Our industry has been [emphasis]struggling[/emphasis] with a fundamental problem. //

[edit_point:high]

According to recent studies, /
[slow][emphasis]73% of users a[stress]ban[/stress]don[/emphasis] applications within the first three interactions[/slow] /
due to [highlight]complexity and poor user experience[/highlight]. //

### [Impact Block]
This affects [emphasis]millions[/emphasis] of people worldwide, /
costing businesses [loud][emphasis]billions[/emphasis] in revenue[/loud] annually. //

## [Solution|Focused]

### [Introduction Block]
That's where our [emphasis]new platform[/emphasis] comes in. /
[building]We've developed a local-first teleprompter workflow that /
[highlight]simplifies complex processes[/highlight] and [emphasis]enhances user experience[/emphasis].[/building] //

### [Benefits Block|150WPM|Excited]
With our solution, / you can expect a [emphasis]50% reduction[/emphasis] in user abandonment /
and a [emphasis]30% increase[/emphasis] in engagement. //

[pause:1s]

[aside]Full details are available in the handout.[/aside] /
[highlight]Thank you[/highlight] for your time. //

[edit_point:medium]

Examples

The examples/ directory contains sample TPS files demonstrating the format:

File	Description
basic.tps	Minimal valid TPS file — front matter, title, segments, blocks, pauses, emphasis, simple headers, escape sequences.
advanced.tps	All format features — speed, volume, delivery modes, syllable stress, breath marks, emotions, pronunciation, edit points, tag nesting.
multi-segment.tps	Multi-segment script with varying speed, emotion, and delivery cues across segments.

File Extension

• Primary: .tps (TelePrompterScript)
• Alternative: .tps.md (for markdown-aware editors)