core/translations: add 🇮🇹 🇵🇹

[mmilata]

Turkish translation fails click tests and from UI reports it seems there are also some missing glyphs. PR adds this third language in the current state but does not enable tests for it.

[github-actions]

core UI changes	device test	click test	persistence test
T2T1 Model T	test(screens) main(screens)	test(screens) main(screens)	test(screens) main(screens)
T2B1 Safe 3	test(screens) main(screens)	test(screens) main(screens)	2724
T3T1	test(screens) main(screens)	test(screens) main(screens)	test(screens) main(screens)
All	main(screens)

[github-actions]

legacy UI changes	device test(screens) main(screens)

[obrusvit]

Some problems:

• the new lang JSONs contain UPPERCASED titles and buttons (remnant from TR, TT. Now they are uppercased automatically by the used font as of Unicode font uppercasing issues #3696
• some changes which occurred recently are not yet reflected, e.g. reset__slip39_checklist_num_shares_x_template is missing in the new JSONs
• it device test still failing

I guess we can merge even with these limitations so that someone can start testing it. WDYT @mmilata

[mmilata]

Since we're not in a rush wrt blob signing I'd say let's fix these issues & then merge.

If QA or anybody wants unsigned blobs then please let me know.

[Hannsek]

Do you know why it device tests are failing? Is there a reason for it?

[mmilata]

The failing T2B1 click tests are mysterious, it's happening in every language including english, and this PR doesn't even touch any code that's involved, seemingly?

https://github.com/trezor/trezor-firmware/actions/runs/10066871496/job/27829340045

[Hannsek]

I was reffering to it device test still failing

[mmilata]

Got it in a state where only (it,pt,tr) T2B1 click tests are failing. There is some issue with how the test code handles translated strings. Possibly related: if inputs__delete translation string is not uppercase the T2B1 click tests also break apart.

[ibz]

LGTM as far as this PR is concerned.

Whether the translations are good, complete, etc, is outside the scope of this.

We will probably need some way to at least dump keys that are missing in various translations, but more generally to ease keeping translations in sync.

[ibz]

I think we need a mechanism to detect if a char is missing (as part of the tests?). For example, you did not include some chars that are technically allowed in some languages, and I understand that it is an optimization, but that also means that if something containing an "È" suddenly appears in Italian, for example, we will probably not notice it, and it will render as a "?"...

[mmilata]

Thanks for the review!

We will probably need some way to at least dump keys that are missing in various translations, but more generally to ease keeping translations in sync.

core/transaltions/cli.py sounds like the right place for this.

I think we need a mechanism to detect if a char is missing

Agreed, opened #4149.

[bosomt]

QA OK

Info:

• Suite version: desktop 24.10.0 (55ac8cb8a4edc1ac546c163acb3482cf53c4e4f8)
• Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) TrezorSuiteDev/24.10.0 Chrome/124.0.6367.243 Electron/30.3.1 Safari/537.36
• OS: MacIntel
• Screen: 1512x982
• Device: Trezor T3T1 2.8.3 regular (revision 7f373ae)
• Transport: BridgeTransport 2.0.33