Post #898671

2026-04-01 10:59 UTC

If you&#39;re using #Pachli Current and use the on-device #translation feature, would you mind taking a look at &quot;Preferences &gt; Manage language packs&quot;? You shouldn&#39;t notice any difference from previous behaviour. If you do notice a difference please let me know. To explain - at #Google there are two ways to do things. The way that works but is deprecated, and the way that doesn&#39;t work yet.

Replies (4)

@pachli@mastodon.social 2026-04-01 11:00

In #Android this manifests as two different ways an app can define the user interface. The writing is on the wall for the way that works ( #xml ), so it's time to (carefully) migrate to the way that doesn't work yet ( #compose ). Hopefully Compose'll work properly by the time I'm finished (this is going to be a multi-month effort over multiple releases). I've migrated the language packs preference screen to see how much work this is (https://github.com/pachli/pachli-android/pull/1750), and what needs to be done.

Open ##2372255
@stonebear2@hachyderm.io 2026-04-01 11:12

@pachli@mastodon.social gyaaaah... is there a way to do this that doesn't involve Google atall? #DigitalSoverignty

Open ##2372257
@badnetmask@hachyderm.io 2026-04-01 11:36

@pachli@mastodon.social I haven't looked at that screen since the day I enabled the option, but it looks okay. I can see "English" with a blue checkmark, and 8 other languages with a trash icon, then all the other languages have a down arrow icon. Is that what you expected?

Open ##2372264
@evgandr@mastodon.bsd.cafe 2026-04-01 11:58

@pachli@mastodon.social Ugh, I have a related question — is it possible to have on-device translation for Pachli installed from F-Droid? #Pachli #fdroid

Open ##2372273