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
If you do not like that, bundled translations without gettext are still officially supported.
So you should be able to use translations without gettext, the question is whether you want to use the new slint translation syntax (i.e., @tr macro) and their officially supported bundled translations or use a slightly more cumbersome syntax and still leverage fluent and the existing czkawka translation architecture/content in a manner akin to #469 (especially if you name the global callback fl although tr seems nice too; maybe even tr.fl leaving room for other potential translation systems).
I used a slightly different approach.
I implemented a Translations singleton that gets updated each time the language changes. All properties within it are linked to translatable elements in the GUI and this will be available in next version
Feature Description
My English is very poor, I want to compile a krokiet with a non-English interface, what would I probably have to do?
The text was updated successfully, but these errors were encountered: