Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

intent: notify languageFrom localizes only the attached print - the mail's subject/body and its multilingual placeholders ({escalation.wording}) stay in the default language

Open
  • Is something wrong?
#7,906 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
java
Domain
internationalization

Research direction

Start by reading NotificationIntent and the notify handling that generates OverdueInvoiceRemindersJob; the issue identifies these as the entry points but gives no file paths or tests. Trace how language and languageFrom reach attached-print rendering, then inspect how multilingual _LANG overlays are read. Done means the whole mail uses the selected language for placeholders and translated subject/body text, with the stated fallbacks.

Written by the indexing model from the issue text.

Description

What happens

A notify: block with languageFrom: (e.g. a dunning schedule, languageFrom: Language.code) renders the attached print in the record's language, but the mail around it does not follow:

  • the authored subject: / body: text is emitted as a Java string literal in the generated job (OverdueInvoiceRemindersJob), with no i18n key, so it is always the intent's (English) text;
  • a placeholder that reads a multilingual row - {escalation.wording} / {escalation.name} of an escalate: ladder over a multilingual: true setting, or {SentMethod.name}-style hops - is read through the repository in the job's default locale, so the <ENTITY>_LANG overlay (which the seed already fills, e.g. SALES_INVOICES_REMINDER_LEVEL_LANG.Wording) is never applied.

Result (BusinessIntents base-sales-invoices#72, 14.88.0 and 14.90.0): a Bulgarian customer receives an English dunning sentence around a Bulgarian invoice PDF, although the Bulgarian wording is in the database.

Ask

When languageFrom: (or language:) is declared on a notify, resolve the WHOLE mail in that language:

  1. the multilingual placeholders ({escalation.*}, {<relation>.name} over a multilingual target) read the overlay row for that language, falling back to the base row;
  2. the authored subject/body get an i18n key (like checks.* messages do) so a module can ship i18n/bg-BG text for them, falling back to the authored text.

NotificationIntent has no knob for this on v14.88.0 or v14.90.0 (language/languageFrom are documented as the attach render language only).

Filed from BusinessIntents base-sales-invoices#72 (pre-train wave 2026-10-17). The module side is ready: the bg wording is seeded into the _LANG table.

Dominant language
Java
Stars
278
Forks
97
Avg merge
18h 57m
Merged PRs (30d)
249

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-dirigible/dirigible

All issues in eclipse-dirigible/dirigible

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.