Closed hrvoj3e closed 4 months ago
fallbackLanguage
only concerns strings from the IIIF manifest, not the interface language.
The current behavior is intended, but I recognize that we could soften the impact by allowing TIFY to load if the translation is missing or invalid and just display an error message. Or maybe you have another suggestion?
My bad about fallbackLanguage
- I just assumed it is for UI.
I suggest that you define a fallback for UI language.
Viewer should load in any case (never break) and EN is always available so user can see images (that is the point of this viewer).
Thanks! To keep things simple, I would stick to the previous language if loading a translation fails. This will be part of the next minor release.
Using version
0.29.2
I see from README that
fallbackLanguage
is by defaulten
but anyway the viewer will not loadUsing version
0.30.2