Šķîþ ţö ḿàîñ çöñţéñţ

Ļéàŕñ ķàþî › Add languages

Hand off, and carry work in one file

A bilingual file for a translator, and a parcel for another machine.

Not every translation happens inside the loop. kapi extract writes a bilingual file per source and language, pre-filled from the content memory, for a translator or the tool they work in, and kapi merge takes it back. A .kpz carries the whole working state between machines without a server. This lab does both.

  1. A bilingual file per languagekapi extract --target-lang dekapi extract writes one bilingual exchange file per language, in XLIFF, the format translation tools read. It is pre-filled from the content memory: every German unit comes back as an exact match, so a translator starts from what the project already established.
  2. Where it wentls outOne file per source and language, under out/.
  3. Inside the filehead -24 out/site-locales-en-GB.en-GB-to-de.xliffEach unit carries its source and target, and the revision of each, which kapi merge checks the returned file against.
  4. Take it backkapi merge -i out/kapi merge reads the returned file, writes the target catalog, and absorbs the pairs into the content memory, so the next extract starts further along.
  5. One file carries the projectkapi pack -o compass.kpzA .kpz is the whole working state: the recipe, the blocks, every locale's overlays, the memory and the terms. It moves between machines or people without a server.
  6. What is insidekapi info compass.kpzkapi info reads the parcel without unpacking it.