{"id":147,"date":"2026-10-14T11:40:51","date_gmt":"2026-10-14T11:40:51","guid":{"rendered":"https:\/\/docs.latw.ai\/uncategorized\/glossary-and-prompts\/"},"modified":"2026-10-14T11:40:51","modified_gmt":"2026-10-14T11:40:51","slug":"glossary-and-prompts","status":"publish","type":"post","link":"https:\/\/docs.latw.ai\/pl\/latw-cloud\/glossary-and-prompts\/","title":{"rendered":"Glossary and Prompts"},"content":{"rendered":"

Glossary & prompts<\/strong> in the panel holds the instructions the AI gets with every translation: the
\nterms that must always be translated one way, and the prompt that sets the style. Both belong to
\nyour account, not to a site \u2014 one glossary or prompt can serve any number of your sites, and each
\nsite picks the one it uses in its Settings \u2192 Glossary & prompt<\/strong>.<\/p>\n

Glossaries<\/h2>\n

A glossary keeps brand names and key terms consistent in every language: Checkout<\/em> is always
\nKasse<\/em>, and your product name stays your product name.<\/p>\n

Creating a glossary<\/h3>\n

Press New glossary<\/strong> and give it a Name<\/strong>, a Source language<\/strong> \u2014 the language the terms are
\nwritten in \u2014 and its Target languages<\/strong>, which become the columns of the table. The source
\nlanguage cannot be changed later; the name and target languages can, under Edit name and
\nlanguages<\/strong>.<\/p>\n

How many glossaries you can have depends on your plan: one on Pay as you go and Solo, five on
\nStartup, thirty on Agency.<\/p>\n

Adding terms<\/h3>\n

Add term<\/strong>, type the term and its translation in each language, and save. Click a term to change
\nor delete it.<\/p>\n

A term with no translation in a language is not used for that language. To keep a name
\nuntranslated, enter it unchanged as its translation.<\/p>\n

Importing and exporting<\/h3>\n

Import CSV<\/strong> takes two formats:<\/p>\n

    \n
  • LATW’s own<\/strong> \u2014 a header term,de,fr,\u2026<\/code>, then one term per row with its translations in the
    \ncolumns of those languages. Export CSV<\/strong> writes this format.<\/li>\n
  • A WPML glossary export<\/strong> \u2014 one row per term and language, with the columns
    \noriginal_language_code<\/code>, target_language_code<\/code>, original_term<\/code> and translated_term<\/code>. The
    \nLATW WordPress plugins export the same format, so a glossary you built in WordPress can be
    \nbrought over as it is.<\/li>\n<\/ul>\n

    Importing adds new terms and updates existing ones \u2014 a term is matched by its text, ignoring
    \ncase. Columns of languages the glossary does not have are ignored, and terms written in another
    \nlanguage than the glossary’s source language are skipped. Up to 5,000 terms per import.<\/p>\n

    Using a glossary<\/h3>\n

    Choose it for a site under Settings \u2192 Glossary & prompt \u2192 Glossary<\/strong>. The bottom of the glossary
    \npage lists the sites using it.<\/p>\n

    Only the terms that appear in the text being translated are sent to the AI, so a long glossary
    \ndoes not make every translation more expensive. Models follow the terms well, but it is an
    \ninstruction, not a search-and-replace: a model can still bend a term to fit the grammar of the
    \nsentence.<\/p>\n

    Deleting a glossary deletes all its terms; the sites that used it translate without one.<\/p>\n

    Prompts<\/h2>\n

    The prompt tells the AI how to translate: the tone, the audience, what to keep and what to adapt.
    \nEvery site uses one.<\/p>\n

    LATW Prompt<\/strong> is the built-in prompt. It cannot be edited, but you can make your own: open the
    \nPrompts<\/strong> tab and press New prompt<\/strong>, or open LATW Prompt<\/strong> to read it first.<\/p>\n

    Writing a prompt<\/h3>\n

    The editor shows two fields:<\/p>\n

      \n
    • System prompt<\/strong> \u2014 added by LATW to every translation. It makes the AI answer in a format your
      \nsite can read and keep HTML, shortcodes and placeholders intact, so it cannot be changed.<\/li>\n
    • Prompt<\/strong> \u2014 yours. Reset to default prompt<\/strong> puts the text of LATW Prompt back, as a starting
      \npoint.<\/li>\n<\/ul>\n

      The prompt can use variables, filled in at translation time:<\/p>\n\n\n\n\n\n\n\n\n
      Variable<\/th>\nReplaced with<\/th>\n<\/tr>\n<\/thead>\n
      {{source_language}}<\/code><\/td>\nThe source language name, for example “English”. Required.<\/strong><\/td>\n<\/tr>\n
      {{destination_language}}<\/code><\/td>\nThe target language name, for example “German”. Required.<\/strong><\/td>\n<\/tr>\n
      {{website_context}}<\/code><\/td>\nThe site’s website description, if it has one.<\/td>\n<\/tr>\n
      {{glossary}}<\/code><\/td>\nThe terms of the site’s glossary, if it has one.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      A prompt without the two language variables cannot be saved. A prompt without {{glossary}}<\/code>
      \ncan be, with a warning: the site’s glossary is then not used, even if one is chosen.<\/p>\n

      The default prompt<\/h3>\n

      The prompt marked Default<\/strong> is given to every site connected from then on. Switch Default<\/strong> on
      \nin a prompt, or open LATW Prompt<\/strong> and press Set as default<\/strong> to go back to the built-in one.
      \nSites that are already connected keep the prompt chosen in their settings.<\/p>\n

      Website description<\/h2>\n

      The third instruction is per site, not per account: the Website description<\/strong> in the site’s
      \nSettings \u2192 Glossary & prompt<\/strong>. Describe what the site is about, who reads it and in what tone; it
      \nfills {{website_context}}<\/code>. See Site Settings<\/em>.<\/p>\n","protected":false},"excerpt":{"rendered":"

      Glossary & prompts in the panel holds the instructions the AI gets with every translation: the terms that must always be translated one way, and the\u2026<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_latwm_translated_slug":"","footnotes":""},"categories":[18],"tags":[],"class_list":["post-147","post","type-post","status-publish","format-standard","hentry","category-latw-cloud"],"_links":{"self":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/147","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/comments?post=147"}],"version-history":[{"count":0,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/147\/revisions"}],"wp:attachment":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/media?parent=147"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/categories?post=147"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/tags?post=147"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}