That looks like a great start actually, I like it. Looking over the example you translated, it might make more sense to have a translation mapping that looks like this:

{
    "cli.command.signup": "signup",
    "cli.command.signup_help": "Create a new YeetFile account",
    "cli.command.login": "login",
    "cli.command.login_help": "Log into your YeetFile account"
}

And then in the actual help message, format it like so:

var AuthHelp = []string{
    fmt.Sprintf("%s | %s", 
        globals.I18n.T("cli.command.signup"), 
        globals.I18n.T("cli.command.signup_help")),
    fmt.Sprintf("%s | %s", 
        globals.I18n.T("cli.command.login"), 
        globals.I18n.T("cli.command.login_help")),
    //...
}

Then we could use cli.command.<command_name> for interacting with the CLI instead of the English words, which would make more sense I think (i.e. yeetfile login takes you to login for English language users, and yeetfile einloggen (not sure if that's correct, sorry!) would take you to login for German language users).

As a result a lot of this could be scrapped:

-type Command string
-
-const (
-	Auth     Command = "auth"
-	Signup   Command = "signup"
-	Login    Command = "login"
-	Logout   Command = "logout"
-	Vault    Command = "vault"
-	Pass     Command = "pass"
-	Send     Command = "send"
-	Download Command = "download"
-	Account  Command = "account"
-	Help     Command = "help"
-)

and instead we could init the CommandMap with the translated command names:

CommandMap = map[string][]func(){
	globals.I18n.T("cli.command.signup"): {signup.ShowSignupModel, login.ShowLoginModel},
	globals.I18n.T("cli.command.login"):  {login.ShowLoginModel},
        // ...
}

Hopefully that makes sense, let me know your thoughts!

Setup framework for translations #1

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions