Open infospherebv opened 2 years ago
Hi, thanks for opening this issue. I will test with your files and I will come back to you with more insight.
Hi, have you already had the chance to look into this? Thanks in advance!
I @infospherebv are you use Jetstream ?
Yes we are using jetstreamMet vriendelijke groet,Erwin van den BergInfoSphere BVKastaanjelaan 4005616 LZ EindhovenTel: +31 (0)40 – 340 02 @.: 171.30815BTW: NL 8105.49.153.B01Op 10 nov. 2022 om 17:50 heeft Gildas Tema @.> het volgende geschreven: I @infospherebv are you use Jetstream ?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
The first thing I see is that there are keys in the DE file that do not exist in EN. Which can cause problems. And also please if you can send us the problem cases.
The strange this is that it fails if I change one normal character to a special (accented) character. But the same character is also in one of the other files and there it works (same language).Met vriendelijke groet,Erwin van den BergInfoSphere BVKastaanjelaan 4005616 LZ EindhovenTel: +31 (0)40 – 340 02 @.: 171.30815BTW: NL 8105.49.153.B01Op 10 nov. 2022 om 19:40 heeft Gildas Tema @.> het volgende geschreven: The first thing I see is that there are keys in the DE file that do not exist in EN. Which can cause problems. And also please if you can send us the problem cases.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
Expected behavior
We are using three languages (EN, DE AND NL). In the DE version there are special characters such as ä. For some reason it seems to work in some of the translation files, while in others it causes the @translations string in the app blade to become empty and causes the whole application to no longer render.
Versions
Transalations
Archief.zip
Contents of
Matice.translations
???