Oh, you want the complete answer.
BrutusNL started in Dutch, and the client app calculated the offset for the display using the length of the Dutch phrase. That same offset was used when switching the language to English. It was only restarting the client app with English as the default that cause the display offset to be recalculated.
Yes, you could argue that the client app should do those recalculations when the language is changed. Not a very common use case.
Better to get a Dutch translation with a short length so a) you don't need to change language, and b) the difference if you did would not be noticeable.
I hope that helps explain what I think
is going on. Frankly the client app code makes my head hurt. And we're still waiting on an abbreviated translation.