Re: [fsfe-system-hackers/fsfe-cd] New italian translation of new-expired email template (#386)

Il Tue, Feb 03, 2026 at 03:34:30PM +0000, Reinhard Müller ha scritto:
> Sorry, there is a question that I still have to ask, sorry I didn't notice earler:
> 
> In the translation
> 
> > 
> > Abbiamo appena addebitato il tuo contributo di
> > {{m.period(payment.period)}} pari a EURO {{m.money(payment.amount)}} da
> > {{m.source(payment.method)}}.
> > 
> > 
> 
> the block {{m.period(payment.period)}} will automatically be replaced
> by the Italian translation of the word "mothly" or "yearly". Can you
> give me these translations in the correct form so they fit with the rest
> of the sentence?

"monthly" (not mothly ... hope is a typo in this email...) -> "mensile"
"yearly" -> "annuale"

> Also, the block {{m.money(payment.amount)}} will be replaced with the
> actual amount. What is the correct way of writing a decimal number in
> Italian regarding decimal separator and thousands separator?

it is viceversa of us/gb:

- decimal separator -> ","
- thousands separator -> "."

> And the block {{m.source(payment.method)}} will be replaced by the
> Italian translation for the terms "your credit card" (if the payment was
> made by credit card), 

"la tua carta di credito"

> "your bank account" (if the payment was made by
> direct debit of a bank account),

"il tuo conto bancario"

> "your PayPal account" (if the payment
> was made by PayPal),

"il tuo conto PayPal"

> and "your account" (as a fallback for all other
> payment methods). 

"il tuo conto"

> Could you also provide me with a good translation for
> these terms which fit in the context of the above sentence?

Done.

> I have to define these variables once in a central place, and they
> will then be used wherever you use the m.something macros. However,
> please add a language="it" everywhere these macros are used so the
> Italian translation will be accessed. So for example, instead of
> {{m.period(payment.period)}}, you write {{m.period(payment.period,
> language="it")}}.

ok

> Sorry that this is very complicated, but it's not easy to make a text
> translateable which is modified dynamically based on some parameters,
> and I haven't come up with a better solution (yet).

Understandable, but I think .po files (gettext) has solutions for this.

ALL translatable strings should be written in / obtained from / estracted
to files in .po format.

And then there is the "magic" po4all: https://www.po4a.org/

-- 

Amike,
Marco Ciampa
_______________________________________________
Translators mailing list -- [email protected]
To unsubscribe send an email to [email protected]

This mailing list is covered by the FSFE's Code of Conduct. All
participants are kindly asked to be excellent to each other:
https://fsfe.org/about/codeofconduct