config.docker.yaml

target_project_root: '/target_repo'
# Mounted Git repository root
input_folder: '/target_repo/i18n/src/main/resources' # Path relative to target_project_root
glossary_file_path: 'glossary.json' # Mounted directly to /app/glossary.json
model_name: 'gpt-4o-mini'
translation_queue_folder: 'translation_queue' # Relative to /app
translated_queue_folder: 'translated_queue' # Relative to /app
dry_run: false
retranslate_identical_source_strings: false
translation_key_ledger_file_path: "/app/logs/translation_key_ledger.json"
supported_locales:
  - code: "cs"
    name: "Czech"
  - code: "da"
    name: "Danish"
  - code: "de"
    name: "German"
  - code: "es"
    name: "Spanish"
  - code: "et"
    name: "Estonian"
  - code: "fr"
    name: "French"
  - code: "ga"
    name: "Irish"
  - code: "hi"
    name: "Hindi"
  - code: "hr"
    name: "Croatian"
  - code: "it"
    name: "Italian"
  - code: "id"
    name: "Indonesian"
  - code: "is"
    name: "Icelandic"
  - code: "ja"
    name: "Japanese"
  - code: "kk"
    name: "Kazakh"
  - code: "km"
    name: "Khmer"
  - code: "ko"
    name: "Korean"
  - code: "lt"
    name: "Lithuanian"
  - code: "lv"
    name: "Latvian"
  - code: "mk"
    name: "Macedonian"
  - code: "ms"
    name: "Malay"
  - code: "nl"
    name: "Dutch"
  - code: "vi"
    name: "Vietnamese"
  - code: "pt_PT"
    name: "Portuguese"
  - code: "pt_BR"
    name: "Brazilian Portuguese"
  - code: "tl"
    name: "Tagalog"
  - code: "be"
    name: "Belarusian"
  - code: "bn"
    name: "Bengali"
  - code: "bg"
    name: "Bulgarian"
  - code: "ca"
    name: "Catalan"
  - code: "el"
    name: "Greek"
  - code: "fi"
    name: "Finnish"
  - code: "hu"
    name: "Hungarian"
  - code: "no"
    name: "Norwegian"
  - code: "ro"
    name: "Romanian"
  - code: "ta"
    name: "Tamil"
  - code: "th"
    name: "Thai"
  - code: "tr"
    name: "Turkish"
  - code: "pcm"
    name: "Nigerian Pidgin"
  - code: "pl"
    name: "Polish"
  - code: "ru"
    name: "Russian"
  - code: "sk"
    name: "Slovak"
  - code: "sl"
    name: "Slovenian"
  - code: "sq"
    name: "Albanian"
  - code: "sr"
    name: "Serbian"
  - code: "sv"
    name: "Swedish"
  - code: "sw"
    name: "Swahili"
  - code: "af_ZA"
    name: "Afrikaans"
  - code: "am"
    name: "Amharic"
  - code: "ha"
    name: "Hausa"
  - code: "jv"
    name: "Javanese"
  - code: "pa"
    name: "Punjabi"
  - code: "yo"
    name: "Yoruba"
  - code: "zh-Hans"
    name: "Simplified Chinese"
  - code: "zh-Hant"
    name: "Traditional Chinese"
max_concurrent_api_calls: 1
logging:
  log_level: "INFO"
  log_file_path: "/app/logs/translation_log.log"
  log_to_console: true
review_model_name: "gpt-4o"
style_rules:
  da:
    - "Use standard Danish throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Use formal address forms (De/Dem) where appropriate."
    - "Technical crypto terms may remain in English when commonly used in Danish context."
    - "Ensure consistent terminology across the application."
  de:
    - "Use the formal 'Sie' form of address."
    - "For quantities, prefer 'ermitteln' or 'bestimmen' over 'bewerten'."
    - "Ensure compound nouns are correctly formed (e.g., 'Sicherheitsschritt')."
  cs:
    - "Use impersonal and neutral phrasing for system messages; avoid the first-person plural."
    - "For camera-related nouns, use the correct preposition 'ke kameře'."
  es:
    - "When referring to 'billetera' (wallet), use feminine pronouns (e.g., 'Configúrala', 'restáurala')."
    - "Ensure questions that open with '¿' are properly closed with '?'."
  et:
    - "Use standard Estonian throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Follow Estonian grammar rules including vowel harmony and consonant gradation."
    - "Technical crypto terms may remain in English when commonly used in Estonian context."
    - "Ensure consistent terminology across the application."
  fr:
    - "Use formal 'vous' form for user address."
    - "When referring to 'portefeuille' (wallet), use masculine pronouns."
  ga:
    - "Use standard Irish (Gaeilge) throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Follow Irish grammar rules including initial mutations and the genitive case."
    - "Technical crypto terms may be translated or kept in English based on established usage."
    - "Ensure consistent terminology across the application."
  hi:
    - "Use Devanagari script throughout."
    - "Maintain formal tone appropriate for financial applications."
    - "Use formal pronouns (आप) rather than informal (तुम/तू)."
    - "Technical crypto terms may be transliterated when no established Hindi term exists."
    - "Ensure consistent transliteration of technical terms across the application."
  hr:
    - "Use standard Croatian throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Follow Croatian grammar rules and use proper diacritical marks (č, ć, đ, š, ž)."
    - "Technical crypto terms may remain in English when commonly used in Croatian context."
    - "Ensure consistent terminology across the application."
  is:
    - "Use standard Icelandic throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Follow Icelandic grammar rules and use proper characters (á, ð, é, í, ó, ú, ý, þ, æ, ö)."
    - "Technical crypto terms may be translated using Icelandic neologisms or kept in English."
    - "Ensure consistent terminology across the application."
  lt:
    - "Use standard Lithuanian throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Follow Lithuanian grammar rules and use proper diacritical marks (ą, č, ę, ė, į, š, ų, ū, ž)."
    - "Technical crypto terms may remain in English when commonly used in Lithuanian context."
    - "Ensure consistent terminology across the application."
  lv:
    - "Use standard Latvian throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Follow Latvian grammar rules and use proper diacritical marks (ā, č, ē, ģ, ī, ķ, ļ, ņ, š, ū, ž)."
    - "Technical crypto terms may remain in English when commonly used in Latvian context."
    - "Ensure consistent terminology across the application."
  kk:
    - "Use Cyrillic script throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Follow Kazakh grammar rules and orthography."
    - "Technical crypto terms may remain in English or be transliterated when commonly used in Kazakh context."
    - "Ensure consistent terminology across the application."
  km:
    - "Use Khmer script throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Follow Khmer grammar rules and syntax."
    - "Technical crypto terms may be transliterated or kept in English when no established Khmer term exists."
    - "Ensure consistent terminology across the application."
  mk:
    - "Use Cyrillic script throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Follow Macedonian grammar rules and orthography."
    - "Technical crypto terms may remain in English when commonly used in Macedonian context."
    - "Ensure consistent terminology across the application."
  ms:
    - "Use standard Malay (Bahasa Melayu) throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Use standard Malay terminology for technical terms when available."
    - "Technical crypto terms may be kept in English when commonly used in Malay context."
    - "Ensure consistent terminology across the application."
  pt_PT:
    - "Use European Portuguese spelling and vocabulary (e.g., 'ecrã' instead of 'tela')."
    - "Maintain formal tone appropriate for financial applications."
  tl:
    - "Use Filipino/Tagalog terms where natural, but technical crypto terms may remain in English."
    - "Maintain respectful 'po' and 'opo' forms where appropriate for user interactions."
  be:
    - "Use Cyrillic script throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Follow Belarusian grammar rules and orthography."
    - "Technical crypto terms may remain in English when commonly used in Belarusian context."
    - "Ensure consistent terminology across the application."
  bn:
    - "Use Bengali script throughout."
    - "Technical crypto terms may be transliterated when no established Bengali term exists."
  ca:
    - "Use standard Catalan throughout."
    - "Maintain formal and polite tone using 'vostè' form appropriate for financial applications."
    - "Follow Catalan grammar rules and use proper diacritical marks (à, è, é, í, ï, ò, ó, ú, ü, ç)."
    - "Technical crypto terms may remain in English when commonly used in Catalan context."
    - "Ensure consistent terminology across the application."
  ta:
    - "Use Tamil script throughout."
    - "Maintain formal tone appropriate for financial applications."
  th:
    - "Use Thai script throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Use polite particles (ครับ/ค่ะ) where appropriate for user interactions."
    - "Technical crypto terms may be transliterated when no established Thai term exists."
    - "Ensure consistent transliteration of technical terms across the application."
  tr:
    - "Use Turkish alphabet (including ç, ğ, ı, ö, ş, ü) throughout."
    - "Maintain formal tone appropriate for financial applications."
    - "Use polite and professional language suitable for business context."
    - "Technical crypto terms may be transliterated or kept in English when no established Turkish term exists."
    - "Ensure consistent transliteration and terminology across the application."
  pcm:
    - "Maintain consistency with terms like 'connection' and 'camera' (do not use 'kamera')."
    - "For negative outcomes, prefer the 'no gree work' pattern where appropriate."
  pl:
    - "Use formal 'Pan/Pani' address forms for user interactions."
    - "Maintain consistent grammatical case usage appropriate to context."
    - "Technical terms should follow Polish IT convention (mix of borrowed English and Polish terms)."
    - "Use Polish punctuation rules (e.g., space before question marks in informal contexts is optional)."
  ru:
    - "In a wallet context, prefer hyphenated terms like 'seed-фраза' and 'биткойн-кошелька'."
  sk:
    - "Use standard Slovak throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Follow Slovak grammar rules and use proper diacritical marks (á, č, ď, é, í, ľ, ĺ, ň, ó, ŕ, š, ť, ú, ý, ž)."
    - "Technical crypto terms may remain in English when commonly used in Slovak context."
    - "Ensure consistent terminology across the application."
  sl:
    - "Use standard Slovenian throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Follow Slovenian grammar rules and use proper diacritical marks (č, š, ž)."
    - "Technical crypto terms may remain in English when commonly used in Slovenian context."
    - "Ensure consistent terminology across the application."
  sq:
    - "Use standard Albanian throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Follow Albanian grammar rules and use proper diacritical marks (ç, ë)."
    - "Technical crypto terms may remain in English when commonly used in Albanian context."
    - "Ensure consistent terminology across the application."
  sr:
    - "Use Cyrillic script throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Follow Serbian grammar rules and orthography."
    - "Technical crypto terms may remain in English when commonly used in Serbian context."
    - "Ensure consistent terminology across the application."
  sv:
    - "Use formal address appropriate for financial applications."
    - "Compound words should follow Swedish orthography rules."
    - "Technical crypto terms may remain in English when commonly used in Swedish context."
    - "Use Swedish number formatting conventions (space as thousands separator)."
  sw:
    - "Use standard Swahili throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Follow Swahili grammar rules and syntax."
    - "Technical crypto terms may remain in English when commonly used in Swahili context."
    - "Ensure consistent terminology across the application."
  af_ZA: []
  am:
    - "Use Ge'ez/Ethiopic script (Amharic alphabet) throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Follow Amharic grammar rules and syntax."
    - "Technical crypto terms may be transliterated or kept in English when no established Amharic term exists."
    - "Ensure consistent transliteration and terminology across the application."
  ha:
    - "Use standard Hausa (Latin script) throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Follow Hausa grammar rules and syntax."
    - "Technical crypto terms may remain in English when commonly used in Hausa context."
    - "Ensure consistent terminology across the application."
  it: []
  jv:
    - "Use standard Javanese (Latin script) throughout."
    - "Maintain formal and polite tone using 'krama' (formal/polite) register appropriate for financial applications."
    - "Follow Javanese grammar rules and syntax."
    - "Technical crypto terms may remain in English when commonly used in Javanese context."
    - "Ensure consistent terminology across the application."
  pa:
    - "Use Gurmukhi script throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Follow Punjabi grammar rules and syntax."
    - "Technical crypto terms may be transliterated to Gurmukhi when no established Punjabi term exists."
    - "Ensure consistent transliteration and terminology across the application."
  yo:
    - "Use standard Yoruba with proper diacritical marks (á, à, ẹ, ẹ́, ẹ̀, í, ì, ó, ò, ọ, ọ́, ọ̀, ú, ù, ń, ǹ, ṣ) throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Follow Yoruba grammar rules and tonal marks correctly."
    - "Technical crypto terms may remain in English when commonly used in Yoruba context."
    - "Ensure consistent terminology across the application."
  bg:
    - "Use Cyrillic script throughout."
    - "Maintain formal tone appropriate for financial applications."
    - "Use formal address forms (Вие) for user interactions."
    - "Technical crypto terms may be transliterated to Cyrillic when no established Bulgarian term exists."
    - "Ensure consistent transliteration and terminology across the application."
  el:
    - "Use Greek alphabet throughout."
    - "Maintain formal tone appropriate for financial applications."
    - "Use formal address forms (εσείς) for user interactions."
    - "Technical crypto terms may be transliterated to Greek when no established Greek term exists."
    - "Ensure consistent transliteration and terminology across the application."
  fi:
    - "Use standard Finnish throughout."
    - "Maintain formal and polite tone using 'Te' form appropriate for financial applications."
    - "Follow Finnish grammar rules including vowel harmony and consonant gradation."
    - "Technical crypto terms may remain in English when commonly used in Finnish context."
    - "Ensure consistent terminology across the application."
  hu:
    - "Use standard Hungarian throughout."
    - "Maintain formal and polite tone using 'Ön/Önök' forms appropriate for financial applications."
    - "Follow Hungarian grammar rules including vowel harmony and agglutination."
    - "Technical crypto terms may remain in English when commonly used in Hungarian context."
    - "Ensure consistent terminology across the application."
  "no":
    - "Use Norwegian Bokmål standard throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Follow Norwegian spelling conventions (Bokmål)."
    - "Technical crypto terms may remain in English when commonly used in Norwegian context."
    - "Ensure consistent terminology across the application."
  ro:
    - "Use standard Romanian with proper diacritical marks (ă, â, î, ș, ț) throughout."
    - "Maintain formal and polite tone using 'dumneavoastră' form appropriate for financial applications."
    - "Follow Romanian grammar rules including genitive-dative case usage."
    - "Technical crypto terms may remain in English when commonly used in Romanian context."
    - "Ensure consistent terminology across the application."
  id:
    - "Use standard Indonesian (Bahasa Indonesia) throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Use standard Indonesian terminology for technical terms when available."
    - "Technical crypto terms may be kept in English when commonly used in Indonesian context."
    - "Ensure consistent terminology across the application."
  ja:
    - "Use appropriate Japanese scripts (Hiragana, Katakana, and Kanji) throughout."
    - "Maintain polite formal tone using です/ます form appropriate for financial applications."
    - "Use appropriate honorifics and respectful language for user interactions."
    - "Technical crypto terms may be transliterated to Katakana when no established Japanese term exists."
    - "Ensure consistent transliteration and terminology across the application."
  ko:
    - "Use Hangul (Korean script) throughout with appropriate Hanja where conventional."
    - "Maintain formal polite tone using 존댓말 (jondaetmal) appropriate for financial applications."
    - "Use formal endings (합니다/습니다) for user interactions."
    - "Technical crypto terms may be transliterated to Hangul when no established Korean term exists."
    - "Ensure consistent transliteration and terminology across the application."
  nl:
    - "Use standard Dutch (Nederlands) throughout."
    - "Maintain formal and polite tone using 'u' form appropriate for financial applications."
    - "Follow Dutch grammar and spelling conventions."
    - "Technical crypto terms may remain in English when commonly used in Dutch context."
    - "Ensure consistent terminology across the application."
  vi:
    - "Use Vietnamese script with proper diacritical marks throughout."
    - "Maintain formal and polite tone appropriate for financial applications."
    - "Use formal address forms and respectful language for user interactions."
    - "Technical crypto terms may be transliterated or kept in English when no established Vietnamese term exists."
    - "Ensure consistent transliteration and terminology across the application."
  pt_BR: []
  zh-Hans:
    - "Use Simplified Chinese characters (mainland China standard)."
    - "Maintain formal tone appropriate for financial applications."
    - "Follow mainland China terminology conventions for technical terms."
    - "Use Chinese punctuation marks (。，、；：？！) rather than Western punctuation."
    - "Maintain consistency with established fintech terminology used in mainland China."
  zh-Hant:
    - "Use Traditional Chinese characters (Taiwan/Hong Kong standard)."
    - "Maintain formal tone appropriate for financial applications."
    - "Follow Taiwan/Hong Kong terminology conventions for technical terms."
    - "Use Chinese punctuation marks (。，、；：？！) rather than Western punctuation."
    - "Maintain consistency with established fintech terminology used in Taiwan/Hong Kong."
brand_technical_glossary:
# (Optional) keep this list alphabetized and unique
  - ACH
  - ACH Transfer
  - Advanced Cash
  - AliPay
  - Amazon eGift Card
  - Bisq
  - Bisq Easy
  - Bitcoin
  - Bizum
  - BSQ Swaps
  - BTC
  - Capitual
  - Cash App
  - CelPay
  - Chase QuickPay
  - CIPS
  - FPS (UK)
  - Faster Payments
  - HalCash
  - I2P
  - IMPS
  - Interac e-Transfer
  - Japan Furikomi
  - Lightning
  - Lightning Escrow
  - Liquid
  - Liquid Assets
  - Monese
  - MoneyBeam (N26)
  - Monero Swaps
  - MuSig
  - NEFT
  - Nequi
  - Paxum
  - PayTM
  - Paysera
  - Perfect Money
  - Pix
  - Popmoney
  - PromptPay
  - RSK
  - RTGS
  - Revolut
  - SEPA
  - SEPA Instant
  - Satispay
  - Strike
  - Submarine Swaps
  - SWIFT
  - SWIFT International Wire Transfer
  - Swish
  - Tikkie
  - Tor
  - UPI
  - US Money Order
  - Uphold
  - Verse
  - WeChat Pay
  - Wire Transfer
  - Wise
  - Wise-USD
  - Zelle

# Set to null or remove to translate all changed files.
# translation_file_filter_glob: null

# Optional: Process all translation files under input_folder instead of only git-changed files.
# Useful for one-time ledger bootstrap or forced full retranslation runs.
# Keep false for normal incremental operation.
process_all_files: false

# Optional: Pull source files (*_en.properties) from Transifex as well as translations.
# Set to `true` if the canonical source of truth for English strings is Transifex.
# The default behavior (`false`) is to only pull translation files and assume
# the source files in the Git repository are the source of truth.
pull_source_files_from_transifex: false