aboutsummaryrefslogtreecommitdiff
path: root/src/lang
AgeCommit message (Collapse)Author
2021-12-31[fix] adding missing french translationsAlystrasz
2021-12-30Merge branch 'main' into feat/version-indicator0neGal
2021-12-30buttons now disable when updating, and app logs0neGal
The buttons in the GUI disable whilst you're updating Northstar and potentionally doing other things in the future, I also added a way to log things in the app, albeit it just prints it in the "Welcome to Viper!" part of the app, which is just fine. I also added all the needed language strings for the GUI logs and removed "gui.missinggamepath" as we use it for both the CLI and GUI even tho "general.missinggamepath" exists, and so we now use the general one for both, as the messages are the same.
2021-12-30Merge branch 'main' of 0neGal/viper into feat/version-indicator0neGal
2021-12-30version now refreshes, fixed and renamed stuff0neGal
The version now refreshes when you update/install Northstar, I renamed vpVersion/nsVersion to just vpversion/nsversion and getInstalledVersion() to getNSVersion(), removed uses of getElementById() with just the ID. I also added English localization. The versions text color is now bound by a CSS variable (we may use it in the future again). I'm also not sure what the point of `style="white-space: nowrap;"` was, as I don't see much of a difference? Rather instead use `<nobr>` in the lang file if needed. Besides that I did tiny code cleanup.
2021-12-30added --version argument0neGal
This will need to be remade once #10 is merged, as to include the installed Northstar version.
2021-12-29[feat] adding French localisation fileAlystrasz
2021-12-29cli is now fully localized0neGal
That is, it's now using our localization module...
2021-12-28if no lang is set, use "en"0neGal
By error I forgot to include this check... I also added in the ability for it to look for a lang file without the extra locale info on the end, i.e if "en-GB" is not found it'll try "en"
2021-12-28attempt at making localization0neGal
This may or may not be how we actually do localization in the future, however for now this seems doable. I will obviously need to look at how we detect the language, as I think instead of relying on names like "en-US" just have "en", so we don't have to symlink various editions of English to the same file. But for now this is a draft, and the important part of this is rather how the underlying localization works.