translatable-strings
Skill1.7k starsChanged yesterdayMITView on GitHub
Use when adding or changing a React component in packages/ that draws or announces text (a label, a button's text, a tooltip, an aria-label, a placeholder, an option in a select, a formatted readout), when working on issue #808, or when asked whether the library can be translated or works with an i18n framework.
Trending
Quiet this year.thin dataabout the whole repository
Who's talking about naomiaro/waveform-playlist
- WebAudio/web-audio-api“Ability to change the playback rate of an AudioBufferSourceNode without affecting the pitch”GitHub · Apr 27, 2022 · 26 reactions
- A Hacker News story“Web Audio API Playlist”Hacker News · Jun 24, 2013 · 2 points
- gilpanal/waveform-playlist“Fetchtest”GitHub · Mar 20, 2024
- lifeart/sm-annotate“Add audio spectrogramm?”GitHub · Aug 2, 2023
- Micrufun/daw“Stream”GitHub · Jan 29, 2023
The biggest 5 of 11 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 11
Talked about on GitHub, Stack Overflow and Hacker News (11 times).
On GitHub · 8
- Apr 27, 2022Ability to change the playback rate of an AudioBufferSourceNode without affecting the pitch — WebAudio/web-audio-api26 reactions · 8 comments
- Mar 20, 2024Fetchtest — gilpanal/waveform-playlist0 reactions
- Aug 2, 2023Add audio spectrogramm? — lifeart/sm-annotate0 reactions · 1 comment
- Jan 29, 2023Stream — Micrufun/daw0 reactions
- May 13, 2022[Feature Request] — doublesymmetry/react-native-track-player0 reactions · 15 comments
3 more on GitHub
- Feb 6, 2022using waveform-playlist with opus-recorder — chris-rudmin/opus-recorder0 reactions · 1 comment
- Dec 27, 2021Waveform playlist: mixing audio tracks — Tonejs/Tone.js0 reactions · 2 comments
- Jul 24, 2020add https://github.com/naomiaro/waveform-playlist — amilajack/awesome-web-audio0 reactions
On Stack Overflow · 2
- Jan 30, 2021Play multiple wave at the same time0 votes
- Apr 4, 2018Customising waveform-playlist plugin0 votes · 1 answer
On Hacker News · 1
- Jun 24, 2013Web Audio API Playlist2 points
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- website/CLAUDE.mdCLAUDE.md
- browser-probesSkill
- dependency-updatesSkill
- design-proposalsSkill
- dnd-kitSkill
- e2e-playwrightSkill
- mutation-testingSkill
- react-patternsSkill
- releaseSkill
- review-roundsSkill
- state-ownershipSkill
- unit-testingSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 43
Never build a sentence by joining translated pieces: word order differs between languages.
- Very specific: line 49
Before using it, find it: git grep -n 'Messages' -- 'packages/*/src/index.ts*'.
- Distinctive: line 51
If it exists: read the default through it, add the new key to the default English table, and keep the prop as the override.
- Very specific: line 60
Do not change an English default in passing: e2e specs and consumers' tests find controls by it (getByRole(..., { name, exact: true })).
- Distinctive: line 68
Run from the repository root.
- Very specific: line 80
Every hit is a finding: a literal written where it is drawn.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Translatable strings
The library owns no translation framework. Every string a component draws or announces can be supplied by the app; the default is the English text.
Scope: the React packages. The web components in packages/dawcore have no
decided mechanism yet (#808).
The order a string is resolved in
- The control's own prop, when the app passed one.
- The app's entry in the messages catalogue.
- The English default.
Both mechanisms exist on purpose (maintainer, 2026-11-13): the catalogue gives an app one place for all strings, the prop overrides a single control.
The prop for each kind of string
| String | Prop |
| Visible label or button text | children |
| Tooltip | title |
| Accessible name with no visible text | aria-label |
| Text built from a value ("120 BPM", "Track 3"), option texts of a select included | a format function prop that takes the value, e.g. formatTempo(tempo), formatRate(rate) |
A symbol or a number format is a string too (×, the decimal point in 0.5):
it goes through the same format function. State the English default in the
prop's JSDoc.
A control in ui-components often has a bound wrapper of the same name in
browser or annotations. The wrapper takes the same string props and passes
them on; without that the app cannot reach them.
Template: packages/annotations/src/components/DownloadAnnotationsButton.tsx
(children and title, English defaults in the destructuring).
Never build a sentence by joining translated pieces: word order differs between languages. One string per message, with the value passed to a format function.
The catalogue
Before using it, find it: git grep -n 'Messages' -- 'packages/*/src/index.ts*'.
- If it exists: read the default through it, add the new key to the default English table, and keep the prop as the override.
- If it does not exist yet: give the prop an English default, and post a comment on #808 with one line per string: the file and line, the English text, the prop. Do not invent a catalogue or its name.
Rules that travel with this
- Ids come from
useId(); no literalid=orhtmlFor=. - Do not change an English default in passing: e2e specs and consumers' tests
find controls by it (
getByRole(..., { name, exact: true })). - A new prop or catalogue key is a doc surface:
llm-reference.md, the component's API page, and the package README if it names the component. - Development warnings and thrown errors are not translated.
Audit: find strings the app cannot replace
Run from the repository root.
# Literal attribute values
git grep -nE '(aria-label|title|placeholder|alt|label)="[^"]*[A-Za-z][^"]*"' -- \
'packages/*.tsx' ':!packages/dawcore*' ':!*__tests__*' ':!*.stories.tsx' ':!*.test.tsx'
# Literal JSX text on one line
git grep -nE '>[^<>{}=;()]*[A-Za-z]{2}[^<>{}=;()]*</' -- \
'packages/*.tsx' ':!packages/dawcore*' ':!*__tests__*' ':!*.stories.tsx' ':!*.test.tsx'Every hit is a finding: a literal written where it is drawn. A string that is
the default of a prop (title = 'Download') matches neither grep.
The greps do not see: JSX text on its own line, an attribute given as an
expression (title={'…'}, a ternary), strings held in arrays or objects
(select options, menu items, shortcut descriptions), template literals,
strings without letters, and .ts files. Read those by hand: selects, menus,
dialogs, and any description: or label: field. Example the greps miss:
TIME_FORMAT_OPTIONS in packages/ui-components/src/components/TimeFormatSelect.tsx.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

