You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@breakline87 you are looking for Hungarian as the language? If so the code should be hu rather than hun this would cause both issues you have mentioned. I will look at putting some validation into the codebase for the language codes
Well then the language wouldnt load the second time. I fixed this issue by using a timeout on my first screen to populate manually everything. Basically I suspect you can arrive at a screen and the language might be still loading while you call Localizationkit related functions?
Can we get an update on this? To summarize the problem, the localization module starts loading the language on start, but the user might reach the UI before loading the language file finishes. There is no "language available" listener or similar implemented, which would at least give us a way to know when can we direct the user to a screen where translations are used.
Activity
willpowell8 commentedon Jun 1, 2018
I will take a look
willpowell8 commentedon Jun 2, 2018
@breakline87 you are looking for Hungarian as the language? If so the code should be hu rather than hun this would cause both issues you have mentioned. I will look at putting some validation into the codebase for the language codes
breakline87 commentedon Jun 4, 2018
Well then the language wouldnt load the second time. I fixed this issue by using a timeout on my first screen to populate manually everything. Basically I suspect you can arrive at a screen and the language might be still loading while you call Localizationkit related functions?
rursache commentedon Jun 7, 2018
same issue here. also,
Localization.buildLanguageCode = "ro"does not work, it always defaults to english, not Romanianbreakline87 commentedon Aug 26, 2018
Can we get an update on this? To summarize the problem, the localization module starts loading the language on start, but the user might reach the UI before loading the language file finishes. There is no "language available" listener or similar implemented, which would at least give us a way to know when can we direct the user to a screen where translations are used.