[robingenz]

Summary

The .strings parser ended a key or value at any ", including an escaped \". A file like this failed to load with Error parsing .strings file: unknown character, so every ios.strings operation on it failed:

"NSCameraUsageDescription" = "Allow \"App\" to use the camera";

It also treated /* and */ inside a quoted string as comment markers.

Changes

• The parser now handles quoted strings in one place. Inside a key or value, only an unescaped " ends the string. A \ and the character after it are kept verbatim, and /*, */ are plain text.
• Escape sequences stay as they are in the file, so the file round-trips unchanged and the generator needs no changes.
• New fixture strings-escaped.strings with escaped quotes in a key and a value, plus comment markers in a value.
• Tests load the fixture through StringsFile, check the parsed entries, regenerate the file unchanged, and set a key next to escaped values.

Closes #263
Supersedes #264

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
trapeze	Ready	Preview	Oct 20, 2026 10:47am UTC

[Copilot]

🟢 Approval recommended

The focused parser fix addresses the reported failures with regression coverage and no unresolved findings.

No open issues 🎉

What changed in this PR

Fixes .strings parsing so iOS string operations can handle escaped quotes and comment markers inside quoted keys and values, addressing #263.

Changes:

• Centralizes quoted-string parsing while preserving escape sequences verbatim.
• Adds a fixture and regression tests for parsing, unchanged regeneration, and setting adjacent keys.

File	Description
packages/​project/​test/​strings-file.test.ts	Tests parsing, regeneration, and updates around escaped strings.
packages/​project/​src/​util/​strings.ts	Handles escapes and treats quoted comment markers as text.
packages/​common/​test/​fixtures/​strings-escaped.strings	Provides escaped quotes and embedded comment markers for regression tests.

_{Review effort: Balanced}