{"result":{"depiction_url":null,"edges":{"observes":{"objects":[{"created":"2026-09-09T13:47:41Z","object_id":{"id":1349,"is_a":["text","documentation","reference","notification"],"name":"doc_notification_user_context","title":"observe_user_context\/3","uri":"https:\/\/zotonic.com\/id\/1349"},"seq":1},{"created":"2026-09-09T13:47:41Z","object_id":{"id":1441,"is_a":["text","documentation","reference","notification"],"name":"doc_notification_set_user_language","title":"observe_set_user_language\/2","uri":"https:\/\/zotonic.com\/id\/1441"},"seq":2},{"created":"2026-09-09T13:47:41Z","object_id":{"id":1442,"is_a":["text","documentation","reference","notification"],"name":"doc_notification_request_context","title":"observe_request_context\/3","uri":"https:\/\/zotonic.com\/id\/1442"},"seq":3},{"created":"2026-09-09T13:47:41Z","object_id":{"id":1466,"is_a":["text","documentation","reference","notification"],"name":"doc_notification_admin_menu","title":"observe_admin_menu\/3","uri":"https:\/\/zotonic.com\/id\/1466"},"seq":4},{"created":"2026-09-09T13:47:41Z","object_id":{"id":2019,"is_a":["text","documentation","reference","notification"],"name":"doc_notification_dispatch_rewrite","title":"observe_dispatch_rewrite\/3","uri":"https:\/\/zotonic.com\/id\/2019"},"seq":5},{"created":"2026-09-09T13:47:41Z","object_id":{"id":2020,"is_a":["text","documentation","reference","notification"],"name":"doc_notification_url_rewrite","title":"observe_url_rewrite\/3","uri":"https:\/\/zotonic.com\/id\/2020"},"seq":6},{"created":"2026-09-09T13:47:41Z","object_id":{"id":2160,"is_a":["text","documentation","reference","notification"],"name":"doc_notification_scomp_script_render","title":"observe_scomp_script_render\/2","uri":"https:\/\/zotonic.com\/id\/2160"},"seq":7},{"created":"2026-09-09T13:47:41Z","object_id":{"id":2405,"is_a":["text","documentation","reference","notification"],"name":"doc_notification_language_detect","title":"observe_language_detect\/2","uri":"https:\/\/zotonic.com\/id\/2405"},"seq":8}],"predicate":{"id":2550,"is_a":["meta","predicate"],"name":"observes","title":{"_type":"trans","tr":{"en":"Observes"}},"uri":"https:\/\/zotonic.com\/id\/observes"}},"references":{"objects":[{"created":"2020-05-30T05:47:58Z","object_id":{"id":1409,"is_a":["text","documentation","developerguide"],"name":"doc_developerguide_translation","title":{"_type":"trans","tr":{"en":"Translate interface text"}},"uri":"https:\/\/zotonic.com\/id\/1409"},"seq":1000000},{"created":"2020-05-30T05:47:58Z","object_id":{"id":1541,"is_a":["text","documentation","developerguide"],"name":"doc_developerguide_dispatch_rules","title":{"_type":"trans","tr":{"en":"Follow a request to its template"}},"uri":"https:\/\/zotonic.com\/id\/1541"},"seq":1000000},{"created":"2020-05-30T05:47:58Z","object_id":{"id":1279,"is_a":["text","documentation"],"name":"doc_glossary","title":"Glossary","uri":"https:\/\/zotonic.com\/id\/1279"},"seq":1000000}],"predicate":{"id":332,"is_a":["meta","predicate"],"name":"references","title":{"_type":"trans","tr":{"en":"References"}},"uri":"https:\/\/zotonic.com\/id\/references"}},"subject":{"objects":[{"created":"2026-09-09T13:47:41Z","object_id":{"id":2555,"is_a":["categorization","keyword","keyword_information_type"],"name":"zotonic_topic_reference","title":"Reference","uri":"https:\/\/zotonic.com\/id\/2555"},"seq":1},{"created":"2026-09-09T13:47:41Z","object_id":{"id":2561,"is_a":["categorization","keyword","keyword_audience"],"name":"zotonic_topic_content_editor","title":"Content editor","uri":"https:\/\/zotonic.com\/id\/2561"},"seq":2},{"created":"2026-09-09T13:47:41Z","object_id":{"id":2588,"is_a":["categorization","keyword","keyword_domain"],"name":"zotonic_topic_localization_and_translation","title":"Localization and translation","uri":"https:\/\/zotonic.com\/id\/2588"},"seq":3},{"created":"2026-09-09T13:47:41Z","object_id":{"id":2635,"is_a":["categorization","keyword","keyword_architecture"],"name":"zotonic_topic_module","title":"Module","uri":"https:\/\/zotonic.com\/id\/2635"},"seq":4},{"created":"2026-09-09T13:47:41Z","object_id":{"id":2641,"is_a":["categorization","keyword","keyword_task"],"name":"zotonic_topic_render","title":"Render","uri":"https:\/\/zotonic.com\/id\/2641"},"seq":5},{"created":"2026-09-09T13:47:41Z","object_id":{"id":2668,"is_a":["categorization","keyword","keyword_data_type"],"name":"zotonic_topic_language_code","title":"Language code","uri":"https:\/\/zotonic.com\/id\/2668"},"seq":6},{"created":"2026-09-09T13:47:41Z","object_id":{"id":2669,"is_a":["categorization","keyword","keyword_data_type"],"name":"zotonic_topic_translated_text","title":"Translated text","uri":"https:\/\/zotonic.com\/id\/2669"},"seq":7}],"predicate":{"id":308,"is_a":["meta","predicate"],"name":"subject","title":{"_type":"trans","tr":{"en":"Keyword"}},"uri":"http:\/\/purl.org\/dc\/elements\/1.1\/subject"}}},"export_revision":4164,"id":1410,"is_a":["text","documentation","reference","module"],"links":[{"rel":"self","target":"https:\/\/zotonic.com\/.zotonic\/websub\/topic\/1410"},{"rel":"hub","target":"https:\/\/zotonic.com\/.zotonic\/websub"}],"medium":null,"medium_url":null,"name":"doc_module_mod_translation","page_url":{"en":"https:\/\/zotonic.com\/docs\/1410\/mod_translation","x-default":"https:\/\/zotonic.com\/docs\/1410\/mod_translation"},"preview_url":null,"resource":{"version":4164,"pivot_location_lat":null,"title":"mod_translation","is_authoritative":true,"body":"

This module provides support for dealing with multiple languages.<\/p>\n

How content and static strings are translated is explained in full in Translation<\/a>.<\/p>\n

Language as part of the URL<\/h2>\n

By default, mod_translation<\/a> prefixes each URL (using URL\nrewriting<\/a>) in your website with the code of the current\nlanguage. The idea behind this is that each language version of a resource<\/a> gets its\nown URL, and is as such indexable for Google.<\/p>\n

This behaviour is enabled by default, but can be switched off in the admin, by going to Structure, Translation. There is\na checkbox labelled “Show the language in the URL”.<\/p>\n

Alternatively you can set the config key mod_translation.rewrite_url<\/code> to false<\/code>.<\/p>\n

Default language fallback<\/h2>\n

By default, the site default language is added as the first fallback after the selected languages. This makes\nuntranslated content use the site default language before other fallback languages are tried. Set\ni18n.default_language_is_fallback<\/code> to false<\/code> to keep the fallback language order based only on the selected request\nlanguage and the previous context language fallbacks.<\/p>\n

This can be changed in the admin by going to Structure, Translation. There is a checkbox labelled “Use the default\nlanguage for untranslated texts”.<\/p>\n

Language recognition<\/h2>\n

When a resource is saved without a language, Zotonic can infer one from its text.\nIt extracts plain text from title<\/code>, chapeau<\/code>, subtitle<\/code>, summary<\/code>, and body<\/code>,\nthen compares its n-gram statistics with trained language profiles. Short input\n(at most 10 bytes after stripping HTML and trimming) or an unsuccessful detection\nfalls back to the current context language. Detection is a heuristic; review the\nselected language when importing short or multilingual content.<\/p>\n

translation_detect:detect(Text, Context)<\/code> restricts matches to the site's editable\nlanguages; translation_detect:detect(Text)<\/code> considers all installed profiles.\nBoth return {ok, LanguageCode}<\/code> or {error, nomatch}<\/code>. Recognition identifies the\nlanguage of existing text; it does not call an automatic translation service.<\/p>\n

The bundled profiles in priv\/data\/profiles<\/code> cover:<\/p>\n
Code<\/th>Language<\/th><\/tr><\/thead>
af<\/code><\/td>Afrikaans<\/td><\/tr>
ar<\/code><\/td>Arabic<\/td><\/tr>
be<\/code><\/td>Belarusian<\/td><\/tr>
bg<\/code><\/td>Bulgarian<\/td><\/tr>
bs<\/code><\/td>Bosnian<\/td><\/tr>
cs<\/code><\/td>Czech<\/td><\/tr>
da<\/code><\/td>Danish<\/td><\/tr>
de<\/code><\/td>German<\/td><\/tr>
el<\/code><\/td>Greek<\/td><\/tr>
en<\/code><\/td>English<\/td><\/tr>
es<\/code><\/td>Spanish<\/td><\/tr>
et<\/code><\/td>Estonian<\/td><\/tr>
fa<\/code><\/td>Persian<\/td><\/tr>
fi<\/code><\/td>Finnish<\/td><\/tr>
fr<\/code><\/td>French<\/td><\/tr>
fy<\/code><\/td>Frisian<\/td><\/tr>
ga<\/code><\/td>Irish<\/td><\/tr>
he<\/code><\/td>Hebrew<\/td><\/tr>
hi<\/code><\/td>Hindi<\/td><\/tr>
hr<\/code><\/td>Croatian<\/td><\/tr>
hu<\/code><\/td>Hungarian<\/td><\/tr>
id<\/code><\/td>Indonesian<\/td><\/tr>
is<\/code><\/td>Icelandic<\/td><\/tr>
it<\/code><\/td>Italian<\/td><\/tr>
ja<\/code><\/td>Japanese<\/td><\/tr>
ko<\/code><\/td>Korean<\/td><\/tr>
lt<\/code><\/td>Lithuanian<\/td><\/tr>
ms<\/code><\/td>Malay<\/td><\/tr>
nl<\/code><\/td>Dutch<\/td><\/tr>
no<\/code><\/td>Norwegian<\/td><\/tr>
pl<\/code><\/td>Polish<\/td><\/tr>
pt<\/code><\/td>Portuguese<\/td><\/tr>
ro<\/code><\/td>Romanian<\/td><\/tr>
ru<\/code><\/td>Russian<\/td><\/tr>
si<\/code><\/td>Sinhalese<\/td><\/tr>
sk<\/code><\/td>Slovak<\/td><\/tr>
sl<\/code><\/td>Slovenian<\/td><\/tr>
sv<\/code><\/td>Swedish<\/td><\/tr>
sr<\/code><\/td>Serbian<\/td><\/tr>
sq<\/code><\/td>Albanian<\/td><\/tr>
ta<\/code><\/td>Tamil<\/td><\/tr>
th<\/code><\/td>Thai<\/td><\/tr>
tl<\/code><\/td>Tagalog<\/td><\/tr>
tr<\/code><\/td>Turkish<\/td><\/tr>
uk<\/code><\/td>Ukrainian<\/td><\/tr>
vi<\/code><\/td>Vietnamese<\/td><\/tr>
xh<\/code><\/td>Xhosa<\/td><\/tr>
zh-hant<\/code><\/td>Traditional Chinese (Cantonese training text)<\/td><\/tr>
zh<\/code><\/td>Chinese<\/td><\/tr><\/tbody><\/table>\n

Training texts come from Wikipedia, typically articles about a country or language.\nCountry articles also include names characteristic of the language.<\/p>\n

Adding a recognition profile<\/h3>\n
  1. Add a UTF-8 training file named <language-code>.txt<\/code> to priv\/data\/texts<\/code>.\nThe code must be recognized by z_language<\/code>.<\/li>
  2. In the Erlang shell, run translation_detect:generate_profile_data().<\/code> This\ngenerates profiles from the training files and loads the profile data.<\/li>
  3. Check the training text and generated priv\/data\/profiles\/<language-code>.dat<\/code>\ninto version control. Review other generated files before committing them.<\/li>
  4. To load newly installed profiles without regenerating them, run\ntranslation_detect:load_profile_data().<\/code> Use translation_detect:profiles()<\/code>\nto list the installed profile codes.<\/li><\/ol>\n

    Programmatically switching languages<\/h2>\n

    In a template, you can use mod_translation<\/a>’s postback hook to switch between languages:<\/p>\n

    {% button text="Dutch" postback={set_language code="nl"} delegate=`mod_translation` %}\n<\/code><\/pre>\n
    Creates a button which switches to Dutch. And another one for english:<\/p>\n
    {% button text="English" postback={set_language code="en"} delegate=`mod_translation` %}\n<\/code><\/pre>\n
    Supporting right-to-left languages<\/h2>\n
    For basic use you don’t need to do anything. Zotonic base site adds a lang<\/code> attribute to the html tag, and when a\nright-to-left language is selected (for instance Arabic), the browser will interpret lang="ar"<\/code> and automatically\nadapt the content to right-to-left.<\/p>\n
    Custom right-to-left content<\/h3>\n
    If you write your own templates, you can add the lang<\/code> tag in the html or body tag, for instance:<\/p>\n
    <body {% include "_language_attrs.tpl" id=id %} >\n<\/code><\/pre>\n
    This will generate the following, when Zotonic selected Arabic for the page with id id:<\/p>\n
    <body xml:lang="ar" lang="ar" dir="rtl" class="rtl">\n<\/code><\/pre>\n
    When you want to add an extra class added to the rtl or ltr class you can use:<\/p>\n
    <body {% include "_language_attrs.tpl" id=id class="my-body-class" %} >\n<\/code><\/pre>\n
    To create individual right-to-left elements, you can use the same principle:<\/p>\n
    <div {% include "_language_attrs.tpl" %}><\/div>\n<\/code><\/pre>\n
    And when you want to force a specific language:<\/p>\n
    <div {% include "_language_attrs.tpl" language=`en` %} >This is English content<\/div>\n<\/code><\/pre>\n
    Translating a single resource<\/h2>\n
    Use the translation dialog in the admin or frontend editor to manage a page's languages. Select an existing source\nlanguage, a destination language, and one of these methods:<\/p>\n
    • Automatic translation<\/strong> sends the source texts to the configured translation service. This option is available\nwhen a module provides a translation service.<\/li>
    • Copy texts<\/strong> fills the destination fields with the source texts for manual translation.<\/li>
    • Leave texts empty<\/strong> enables the destination language so its texts can be entered manually.<\/li><\/ul>\n
      Copying and automatic translation fill blank destination fields. Select Overwrite existing texts with new\ntranslations<\/strong> to replace filled fields as well. These actions update the edit form: review the texts and save the\npage to persist them. If automatic translation is incomplete, the editor uses the source text for missing\ntranslations and asks the user to review the result.<\/p>\n
      The dialog also lists the page's current translations. Deleting a translation requires confirmation and disables\nthat language on the edit form; its translated texts are removed from the database when the page is saved.<\/p>\n
      Translating a saved resource from Erlang<\/h3>\n
      Use m_translation:add_translation\/5<\/code> to translate and save a resource directly. For example, to translate resource\nId<\/code> from English to Dutch while preserving existing Dutch texts:<\/p>\n
      ok = m_translation:add_translation(Id, en, nl, false, Context).\n<\/code><\/pre>\n
      The resource must be editable in Context<\/code>, both languages must be editable languages for the site, and the source\nlanguage must be present on the resource. The call returns ok<\/code> or {error, Reason}<\/code> and waits for the translation\nservice and resource update to finish. Successful translations add the destination language and mark it for review\nin translation_status<\/code>. Pass true<\/code> as the fourth argument to overwrite existing destination texts.<\/p>\n
      The resource translator processes translation records and known binary text properties, including nested blocks,\nusing the property rules described below for tree translation. Binary text is assumed to be in the selected source\nlanguage. translation_translate_rsc:copy_translation\/5<\/code> copies source texts and saves the resource without calling\na translation service. m_translation:remove_translation\/3<\/code> removes a language from the saved resource.<\/p>\n
      For an in-memory property map, m_translation:add_translation_map\/5<\/code> returns {ok, TranslatedMap}<\/code> or an error without\nsaving a resource. m_translation:remove_translation_map\/2<\/code> similarly removes languages from a map.<\/p>\n
      Editing texts in the admin<\/h2>\n
      The resource translation overview opens a single-field dialog when an editable\ntext is clicked. Body properties and properties ending in _html<\/code> use z_editor<\/code>;\nshort plain texts use an input and other plain texts use a textarea. Sites can\noverride the blocks in _translation_edit_field.tpl<\/code>. The rich-text dialog inherits\nthe page's editor profile (advanced in the admin) and works with any enabled editor module.<\/p>\n
      Saving changes only the selected property and language, preserving other languages\nand block structure. Named block fields are supported; structured survey answer\nlists, unnamed blocks and unsafe properties remain read-only. Missing translations\nopen empty, without falling back to a different language.\nThe page slug is editable only when the resource has Customize page slug enabled\n(custom_slug<\/code>). This condition is checked when opening and saving the dialog.<\/p>\n
      The translation overview, admin and frontend-admin edit forms warn when a newer\nresource version is observed. A successful translation dialog save acknowledges\nits new version in the overview only if the overview was current when the dialog\nopened. Saves never clear warnings about intervening external updates.\nResource update notifications include version<\/code>, including updates through\nm_rsc:touch\/2<\/code>. Media notifications also trigger a version check. Reconnects,\nwindow focus and periodic checks recover missed notifications. Notifications never\nadvance the version of an unsaved form, and stale saves are rejected under a database\nrow lock. Reloading asks for confirmation when the form has unsaved edits.<\/p>\n
      Media replacements initiated in the edit page send a private version acknowledgement\nto that browser. The form advances only from the exact pre-update version and keeps\nits unsaved edits; other tabs and already-stale forms still show the warning.<\/p>\n
      Video conversion marks resource updates with the update option\n{update_reason, media_processing}<\/code>. Resource update notifications include\nprevious_version<\/code> and reason<\/code>. The media_processing<\/code> reason is emitted only when\nthe resource properties are unchanged except for version, modification date and\nmodifier. Otherwise the reason is update<\/code>, including when upload observers change\ntext or category. Editors and translation overviews acknowledge only the next\nconsecutive processing version, preserving unsaved edits and existing conflicts.\nMissed notifications conservatively require reloading; polling alone cannot prove\nthat a skipped version contained no text changes. Failed conversion and preview-only\nmedium updates do not themselves increment the resource version.<\/p>\n
      The single-field edit dialog offers Translate from<\/strong> when a translation service\nand another nonempty source language are available. It translates the saved source\nproperty (including named-block fields) using the configured services, with HTML\nmode for rich text and text mode otherwise. The result replaces only the dialog's\ndraft, after confirmation; Save still performs the normal version-checked update.\nSource languages use exact translations, not fallback. Failed requests and results\narriving after further edits or closing the dialog do not overwrite the draft.\nResource permissions, field eligibility and source\/target languages are rechecked\non the server. Automatic translation may send the source text to a remote service.<\/p>\n
      Custom admin form templates must include _admin_edit_version.tpl<\/code> inside the form\n(pass version_form<\/code> for a form id other than rscform<\/code>). The z_edit_version<\/code>\nhidden input is required for version-checked saves.<\/p>\n
      Bulk translation management<\/h2>\n
      The admin Bulk update<\/strong> dialog offers Manage translations<\/strong> for the selected pages. It opens the language-count\nand translation dialog with automatic translation, copying, empty languages, and confirmed language removal.\nOnly the selected pages are processed, without following menu or collection descendants. Duplicate selections count\nonce, and removing a language preserves pages where it is the last language.<\/p>\n
      Opening the dialog requires edit access to every selected page. The server stores the selection for one day and\nrestricts access to the user who created it. A sidejob processes the selection, rechecking edit access before each\npage, while the browser polls progress and displays a blocking modal. Starting a job only waits for startup, not\ncompletion. Reopening the same selection under the same user reconnects to its running job. Reload after completion\nto refresh the overview. These changes are saved immediately, independently of the bulk property update form.<\/p>\n
      Translating a tree<\/h2>\n
      The Translate all pages<\/strong> button manages translations for an entire menu or collection. It is available in the\nfrontend editor and at the bottom of the admin + Translate<\/strong> dialog for menus and pages with outgoing haspart<\/code>\nconnections. Sites can use the same\nfeature for menu-based content such as timelines; the frontend editor's translate-all<\/code> button acts on its tree_id<\/code>.<\/p>\n
      A tree includes its root resource, nested menu entries, and resources connected through haspart<\/code>. Each resource is\ncounted and processed once, even when it occurs more than once or the tree contains a cycle. The dialog shows the\nunion of the pages' languages, with the number of pages in each language. Resources without a language list count\nas using the site's default language.<\/p>\n
      Translation and language removal<\/h3>\n
      The dialog offers the same translation options as the single-page editor:<\/p>\n
      • Automatic translation<\/strong> uses the configured translation service and marks translated content for review.<\/li>
      • Copy texts<\/strong> copies text from the selected source language to the destination language.<\/li>
      • Leave texts empty<\/strong> enables the destination language without copying or translating text.<\/li><\/ul>\n
        Copying and automatic translation fill empty destination fields. Existing text is preserved unless the overwrite\noption is selected. Pages without the selected source language in their language list are skipped for these two\nmethods. Empty source text is allowed when the source language is listed. Before starting,\nthe dialog refreshes the page count and asks the user to confirm applying the selected options to that many pages.\nChanges are saved immediately; save or discard any pending editor changes before starting a tree operation.<\/p>\n
        Plain binary text is also translated, assuming it is in the resource's selected source language. The shared\nresource translator recognizes title<\/code>, short_title<\/code>, chapeau<\/code>, summary<\/code>, body<\/code>, body_extra<\/code>, date_remarks<\/code>,\nprompt<\/code>, explanation<\/code>, matching<\/code>, narrative<\/code>, feedback<\/code>, seo_title<\/code>, seo_desc<\/code>, seo_keywords<\/code>, and properties\nending in _html<\/code>. This also applies inside nested blocks. These fields become translation records retaining the\nsource text alongside the destination text. Other binary properties remain unchanged; existing translation records\ncontinue to use their explicit language entries.<\/p>\n
        Deleting a language requires a separate warning and confirmation. It removes that language from every editable\npage in the tree, except pages where it is the last language. Those pages are kept unchanged.<\/p>\n
        Permissions, progress, and completion<\/h3>\n
        Opening the dialog or starting a job requires edit access to the root. Traversal requires visibility of every page.\nThe worker checks edit permission again immediately before processing each resource and skips resources that are\nno longer editable. Normal resource-update permission checks also apply when saving changes.<\/p>\n
        Translation and removal run in a sidejob that is unique per tree and site on the current Erlang node. Startup returns\na running status as soon as the worker registers, before traversing the tree or calling a translation service. The\nrequest does not wait for completion, and the tree job has no overall translation deadline. A second job for the\nsame tree returns busy<\/code> while the first is running.<\/p>\n
        The editor shows progress in a modal that cannot be dismissed, including when an editor is opened or reloaded during\na running job. This is a UI-only lock: it does not add ACL restrictions or block unrelated server-side updates.\nProgress includes the total number of pages, pages processed, pages skipped, and pages that failed. The final\ndialog lists skipped pages with links to open their edit pages in a new tab. If an automatic\ntranslation service returns incomplete translations for a page, that page's texts are left unchanged and it is counted\nas failed. Changes already saved on other pages are retained. After completion or failure, the dialog offers a reload\nso the editor shows the saved content.<\/p>\n
        Model and template integration<\/h3>\n
        The m_translation_tree<\/code> model exposes these paths through templates and the model API:<\/p>\n
        Method<\/th>Path<\/th>Result<\/th><\/tr><\/thead>
        get<\/code><\/td>\/<id><\/code><\/td>Page total and language counts for the tree.<\/td><\/tr>
        get<\/code><\/td>\/status\/<id><\/code><\/td>Current or most recently cached job progress for the root.<\/td><\/tr>
        post<\/code><\/td>\/<id><\/code><\/td>Start a job and return its initial running status.<\/td><\/tr><\/tbody><\/table>\n
        A translation payload contains method<\/code> (translate<\/code>, copy<\/code>, or empty<\/code>), src<\/code>, dst<\/code>, optional overwrite<\/code>, and\nconfirmed: true<\/code>. A removal payload contains method: remove<\/code>, language<\/code>, and confirmed: true<\/code>.<\/p>\n
        The worker publishes progress on model\/rsc\/event\/<root>\/translation_tree<\/code>. Browser clients subscribe through\nbridge\/origin\/model\/rsc\/event\/<root>\/translation_tree<\/code> and can poll the status path to recover after reconnecting.\nRunning status is owned by the worker; completed results are cached for one hour. The initial total is zero until\ntree traversal finishes.<\/p>\n
        Custom editors can include _translation_tree_button.tpl<\/code> and _translation_tree_init.tpl<\/code>, passing the root as\ntree_id<\/code>. The initialization template also wires an existing button with id translate-all<\/code>. The standard admin\nand frontend editors already include this initialization.<\/p>\n
        Accepted Events<\/h2>\n
        This module handles the following notifier callbacks:<\/p>\n
        • observe_admin_menu<\/code>: Add translation and language administration entries to the admin menu.<\/li>
        • observe_dispatch_rewrite<\/code>: Removes the language from the path parts and sets it as the page language.<\/li>
        • observe_language_detect<\/code>: Recognize the language of supplied text using n-gram profiles, optionally restricted to editable languages.<\/li>
        • observe_request_context<\/code>: Check if the user has a preferred language (in the user's config) using z_context:get_cookie<\/code>.<\/li>
        • observe_scomp_script_render<\/code>: Add translation runtime variables to rendered client-side script blocks.<\/li>
        • observe_set_user_language<\/code>: Persist a user language change to the authenticated user profile when allowed.<\/li>
        • observe_url_rewrite<\/code>: Rewrite URLs to include\/remove language prefixes according to translation settings.<\/li>
        • observe_user_context<\/code>: Set user context language\/timezone defaults based on the user profile resource.<\/li><\/ul>\n
          Delegate callbacks:<\/p>\n
          • event\/2<\/code> with postback<\/code> messages: language_default<\/code>, language_delete<\/code>, language_status<\/code>, set_language<\/code>, toggle_url_rewrite<\/code>, translation_generate<\/code>, translation_reload<\/code>.<\/li>
          • event\/2<\/code> with submit<\/code> messages: language_add<\/code>, language_list<\/code>.<\/li><\/ul>","slug":"mod_translation","doc_module_config":[{"default":""en"","description":"The default language to use for this site. Defaults to 'en'. Note that this is set by reordering the languages in \/admin\/translation","has_default":true,"key":"language","module":"i18n","type":"string"},{"default":""en"","description":"The default language stemmer to use for this site. Defaults to 'en'. This is used for search indexing and stemming.","has_default":true,"key":"language_stemmer","module":"i18n","type":"string"},{"default":"true","description":"Add the default language as a fallback language for requests in another language. This makes untranslated texts fall back to the site default language instead of the previous request language fallback order.","has_default":true,"key":"default_language_is_fallback","module":"i18n","type":"boolean"},{"default":"true","description":"Rewrite URLs to include the language code, e.g. \/en\/ instead of \/","has_default":true,"key":"rewrite_url","module":"mod_translation","type":"boolean"},{"default":"false","description":"Force the default language if no language is set in the request. If not set then language negotation using the request's Accept-Language header is used.","has_default":true,"key":"force_default","module":"mod_translation","type":"boolean"}],"is_protected":false,"visible_for":0,"tz":"UTC","language":["en"],"doc_source_hash":"f7e0e3ffb9957a61426289fc33734f696c310c870673ec0be0d1c742c37bf1ea","is_featured":false,"content_group_id":{"id":2551,"is_a":["meta","content_group"],"name":"content_group_imported_docs","title":"Imported documentation","uri":"https:\/\/zotonic.com\/id\/content_group_imported_docs"},"category_id":{"id":320,"is_a":["meta","category"],"name":"module","title":"Modules","uri":"https:\/\/test.zotonic.com\/id\/320"},"doc_source_path":"apps\/zotonic_mod_translation\/src\/mod_translation.erl","publication_start":"2023-06-24T08:17:44Z","github_url":"https:\/\/github.com\/zotonic\/zotonic\/blob\/master\/apps\/zotonic_mod_translation\/src\/mod_translation.erl","pivot_location_lng":null,"doc_source_kind":"module","name":"doc_module_mod_translation","is_unfindable":false,"is_published":true,"pivot_geocode":null,"created":"2020-05-30T05:47:21Z","uri":null,"doc_status":"current","is_dependent":false,"erlang_app":"zotonic_mod_translation","publication_end":"9999-06-01T00:00:00Z","modifier_id":{"id":1,"is_a":["person"],"name":"administrator","title":"Site Administrator","uri":"https:\/\/zotonic.com\/id\/1"},"privacy":0,"doc_source_commit":"f3c6a9a2dde17cb5b121dd3e3018d9ef4b1b3943\n","creator_id":{"id":336,"is_a":["person","robot"],"name":"gitbot","title":"Git","uri":"https:\/\/zotonic.com\/id\/336"},"modified":"2026-11-09T21:39:23Z","title_slug":"mod_translation"},"uri":"https:\/\/zotonic.com\/id\/1410","uri_template":"https:\/\/zotonic.com\/id\/:id","version":4164,"websub":{"hub":"https:\/\/zotonic.com\/.zotonic\/websub","topic":"https:\/\/zotonic.com\/.zotonic\/websub\/topic\/1410"}},"status":"ok"}