-
Notifications
You must be signed in to change notification settings - Fork 6
Description
Just a not so random sample of additional features:
- Keep a copy of all translations locally
-- Make the translations to be held locally configurable?
New commands
poeditor rm [-c <context>] <term> [lang] Adds removal of a term or a specific translation to the staging area
poeditor update [-c <context>] <term> [<defaultTranslation>] [-t <tag>]* Update an existing terms default translation or any tags and put the change to the staging area
poeditor rename [-c <context>] <oldTerm> <newTerm> Add a term rename to the staging ares
poeditor cp [-c <context>] <term> <targetContext> Adds create a copy of a term from one context in another one to the staging area. Includes all translations.
poeditor mv [-c <context>] <term> <targetContext> Adds move a term from one context to another to the staging area. Includes all translations.
poeditor translate [-c <context>] <term> <lang> <translation> Add a new translation for the term to the staging area
poeditor ctx|context [context] Set the default context for all following operations, leave blank to remove
poeditor reset [-c <context] <term> Remove all staged operations for this term from the staging area.
The new commands would require a revised design, as we need to store the necessary information in the staging area to enable review and updates before staging.
Questions
- Should/Can we allow to stage multiple changes for the same context/term?