Viper - Launcher+Updater for TF|2 Northstar

about summary refs log tree commit diff

path: root/src/lang.js

Age	Commit message (Collapse)	Author
2022-04-13	the user can now manually select a language	0neGal
	This allows someone to have their system in any language, and then have Viper in a separate language. This is also useful for testing.
2022-02-19	[fix] translation file is only loaded is current context didn't set up lang ↵	Alystrasz
	variable
2022-02-19	[fix] loading up translation object each time a translation is needed	Alystrasz

2022-01-17	documented: index.js, cli.js, lang.js app/lang.js	0neGal

2021-12-29	fallback to localizations	0neGal
	If a message is not localized it'll default back to English, instead of just giving back the string...
2021-12-28	if 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-28	attempt at making localization	0neGal
	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.