locli

Project overview from locli.json: languages, missing texts per language, open Git features and whether unreleased changes wait for release approval. Read-only.

无需输入参数。

The project's feature areas (a key's first segment, e.g. login in login_username_label) with key counts and examples. With feature="login" it returns the existing area to use (by name or synonym such as auth/signin) or proposes a new one, which the first push of keys with that prefix creates. Call it when you start building a feature. Read-only.

The project's translation guide: tone and form of address per language, glossary terms with their required translation, terms that stay as written (keep), and every current translation that breaks the glossary. Read it before translating. Read-only.

无需输入参数。

Scans the app's code for every key in locli.json's files: where it is used (file:line), as what (toolbar item, tab, button, menu item, screen title, form field, push notification, email, alert, error message, accessibility label, text) and its length budget in characters. Lists translations in the files that exceed their budget and keys not found in the code. Call it before translating and fix every too-long text (shorter wording, or a layout that wraps). Local, read-only.

Search existing keys, translator comments and values (case-insensitive, all words must match). Call this before creating a key so a text with the same meaning is reused. Read-only.

Create missing keys and values in locli. Never overwrites: values that already exist are reported as skipped (change them in locli instead). Use lower_snake_case keys whose first segment is the feature area and always give a comment saying where the text appears and what each placeholder holds. Placeholders are printf style (%@, %lld, %1$@) for iOS/Android, ICU names ({used}, {n, number}) for keys used only on web/backend; give plural texts as forms with "other". New keys join the current Git branch's feature. Prefer adding the text to the app's source file and calling locli_push when the app has one.

Upload texts from the app files in locli.json that locli lacks (new keys, missing languages). Never overwrites existing texts. Reports how many texts wait for a release.

Write the latest approved release into the app files from locli.json. Replaces the released keys' texts in those files; local-only keys stay. draft=true writes the unapproved working state for local checks only.

Delete keys that no release ever contained: in locli (texts, translations, history) and in the app files from locli.json, so the next push does not add them back. Keys locli does not know are removed from the files only. If any key was already released, nothing is deleted: apps may still show it, so a project owner deletes it in the web editor. Warns about code that still uses a deleted key. Use for duplicates, typos and texts of a feature that was dropped; run with dryRun first and show the user the list.

Suggestions from the project's public community catalog (anyone can suggest translations of released texts, vote and discuss, without an account), the most voted first. Each has an id, key, language, source text, today's text in locli, the suggestion, score, votes and the public discussion. Read-only.

Decide one community suggestion: accept makes it the working text (it ships with the next approved release; you never approve releases), reject declines it, hide removes spam or abuse from the public page. Before accepting, check that placeholders, the glossary (locli_guide) and the tone fit; when several suggestions compete, prefer the clearly better wording, not only the score.