TosinAF

# i18n Phase 2: HTML Help Text Blocks

## Context

As part of an i18n audit of the Harvey frontend, we identified ~23 large HTML help text blocks that contain user-facing content with zero Lingui wrapping. These are more complex than simple string wrapping (Phase 1) because they contain multi-paragraph HTML with inline formatting.

This doc covers the 7 blocks in `src/components/workflows/constants.ts`. There are also 16 similar blocks in `src/components/research/constants.tsx` (not covered here).

---

TosinAF

[ERD] Text-to-Speech for Harvey Responses

Related Links

• Implementation Plan: https://gist.github.com/TosinAF/dfe34acbef8cba0b74d4ac6d7f52acd8
• Audio Seeking Decision Doc: https://gist.github.com/TosinAF/26654dcc2c84dea4808ca4472e00e2fe
• Reference ERD (Audio Transcription): https://www.notion.so/harveyai/ERD-Audio-Video-Transcription-330ac3fcdd7a81c9b347c5560bb8f1b0
• Linear: MOBILE-16 (voice reliability), MOBILE-59 (TTS on response)
• ElevenLabs channel: #ext-harvey-elevenlabs
• Voice eng channel: #voice-eng

TosinAF

TTS Implementation Plan — Dual Approach

Use Case & Requirements (from team discussion)

Primary use case: Playing Harvey assistant responses out loud. Responses can be long.

Control Priorities (from Anna, corrected)

Priority	Control	Notes

TosinAF

i18n Call-Site Migration Plan — Agent-Ready PR-by-PR Guide

Date: 2026-03-30 Status: Ready for execution Prerequisite PRs (all merged): #39975 (infra), #40117 (PO fill), #40174 (fixups)

---

How to Use This Plan

TosinAF

TTS Audio Delivery: Seeking Support on iOS & Web

Decision needed: How should we deliver TTS audio to clients so that seeking (scrubbing forward/backward) works reliably on both iOS and Web?

---

The Problem

When a user listens to generated audio, they expect standard playback controls: play, pause, and seek (scrub to any point in the audio). This is trivial with a normal audio file but breaks with streamed audio.

TosinAF

i18n Completion PR Plan: Hardcoded Strings + i18next→Lingui Migration

Date: February 24, 2026 Branch base: main Total scope: ~3,460 string changes across 19 PRs (18 done, 1 remaining) Prerequisite: Lingui v5 infrastructure already deployed (PR #19175)

---

How to Use This Document

TosinAF

Lingui Migration Plan: i18next → Lingui v5

Unified plan synthesized from two independent research efforts and framework documentation research. Date: 2026-02-08

---

Executive Summary

Migrate the Harvey frontend from i18next (runtime JSON loading via HTTP backend) to Lingui v5 (compile-time PO catalogs via Vite plugin). The migration covers the main app, Word Add-In, and Outlook Add-In. It is phased into atomic PRs grouped by product area for reviewability.

TosinAF

Lingui Unlocalized Strings Audit Report

Generated: 2026-03-03

Total warnings: 1657 across 428 files

---

Table of Contents

TosinAF

// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console

TosinAF

//
//  TNPageViewController.m
//  The News
//
//  Created by Tosin Afolabi on 26/06/2014.
//  Copyright (c) 2014 Tosin Afolabi. All rights reserved.
//

#import "TNPageViewController.h"