.fvlang — Foldervas Language Pack

1. Shape

{
  "format": "fvlang",
  "version": 1,
  "code": "eo",
  "name": "Esperanto",
  "strings": {
    "nodeType.note": "Noto",
    "fs.saveAs": "Konservi kiel…",
    "backup.lastBackup": "Lasta kopio: {when}"
  }
}

• code — short lowercase identifier ([a-z-], ≤ 12 chars). Importing a pack with the same code replaces it.
• name — the language's native name, shown in the language picker.
• strings — message key → translated text. Every key is optional: anything you don't translate falls back to English, so a partial pack is perfectly usable.

2. Rules for translators

• Keep placeholders exactly as-is: {n}, {name}, {when}… They are replaced at runtime; renaming them breaks the message.
• Keep embedded newlines (\n) and symbols (·, →, ↳, ☐, ☑) where the source has them.
• Don't translate product and format names: Foldervas, Markdown, JSON, kanban, .foldervas, .fvbackup.
• Unknown keys are ignored (a pack written for a newer app version still imports).

3. Getting the full key list

Settings → Application → "Export translation template…" writes a complete .fvlang with every key and the English text as starting values. Translate the values, change code and name, and import it back. That template is always in sync with your app version — no need to chase a key list on the web.