Translation status

Which languages this documentation is actually available in, counted from the files rather than claimed. Most of it is English only.

The language menu lists eleven languages. That reads as "this documentation is available in eleven languages", and it is not true — so here is what is actually translated.

{/ BEGIN generated coverage — tools/sync-translations.mjs /}

{/ END generated coverage /}

The interface is translated in all eleven. Navigation, buttons, status labels, callout headings, the safety warnings and the error-page furniture are complete everywhere, including right-to-left layout for Arabic. What is largely not translated is the prose: the pages themselves.

#Why it is set up this way

Falling back to English beats the alternatives. A missing page could 404, or it could serve a stale translation from whenever someone last touched it — and a confidently wrong translation of a page about signature verification is worse than an English page a reader has to work through slowly.

So an untranslated page shows the English body, says it is doing that, and offers a link to help translate it. The language menu marks the same thing before you choose: an option reading "Deutsch (auf Englisch)" is telling you that picking German here will show you English, because this particular page has no German version yet.

#Helping

Translations are the single easiest useful contribution to this project, and the one that most needs doing.

1. Copy the English page

   docs-site/<page>.mdx → docs-site/<locale>/<page>.mdx. Keep the same slug; the build pairs them by path.

2. Translate the prose, not the code

   Code stays as it is. Comments inside code blocks are worth translating; identifiers, endpoints and canonical byte strings are not — a translated did:svrp: is a broken one.

3. Keep every safety statement

   Credits are a test unit; status: "active" does not mean online; a valid signature is not a valid identity; nothing here moves value. A translation may be shorter than the English. It may not be shorter by dropping those.

4. Do not drop the endpoint lists

   Prose can be condensed in another language. The list of what exists cannot — CI fails a translated capability page that names fewer endpoints than the English one, because a reader looking up whether something works has to be able to find out.

The table above is generated by counting files, so it updates itself the moment a translation lands — and a page added in English lowers every percentage, which is the honest direction for that number to move.