This is a regression of behaviour. I’m not sure if it is done on purpose. I notice that all data structure in blurbs are given “” empty value by default. Consequently, all untranslated blurbs become blank. Take SN 22.44, this is the Suttaplex card in English:
Is this done on purpose or unintended consequence? Previously, it would still display the blurb in English if the blurb of the selected language hasn’t been translated.
I don’t necessarily think it is bad for blurbs. Showing English blurbs while the reader selects another language may break immersion, especially for those who don’t know English.
The overall problem is that there are two behaviors covered by this change. Previously:
An empty string could mean that a segment was omitted in a translation (such as with repetition).
A missing translation key entirely could mean that it should fallback to the root language (such as with a translator’s name)
There is no distinction between the two now. But there should be, in one way or another (either same as before, or explicit values like <omitted> or <fallback>, or something else)
If I’m not mistaken, generally localizations fallback to the root language rather than leaving blank. That does a few things:
Makes you aware that it isn’t supposed to be blank
Allows you to use a translator
Makes it more likely someone may contribute a translation
There are different ways of handling it, but purely blank is confusing and inconsistent UX IMO
You’re quite right. That was what prompted me to start reading the suttas and translate blurbs because I was frustrated that Indonesian enjoys better support than Chinese over here.
