go-i18n VS cobra

Thanks for sharing, from a quick read this looks easier to maintain than nicksnyder/go-i18n.

I am using Nick Snyder's go-i18n for translations. I am also building a go library intented to be imported by either by other libraries or cli executables. All of the documentation I have seen about supporting i18n assume this is being used in an app, but don't cover the scenario where this is being implemented in a library.

On a different note you may consider exploring nicksnyder/go-i18n as well, it simplifies things a bit.

I am trying to get to grips with i18n in Go but finding that most articles on the subject are either inadequate or geared towards web applications. This query is specifically for cli applications and libraries. The kind of articles I've looked at so for are i18n managing translations and internationalization i18n go. I have also investigated using Nick Snyder's go-i18n, but the more I learn, the more I'm coming to the conclusion that it's not necessary for my needs.

What you are looking for is I18N like https://github.com/nicksnyder/go-i18n

This article will show you how to prepare your Go project for localization using a very popular go-i18n package.

I've looked at many packages for this operation (including the one built into the Go core), but nicksnyder/go-i18n was the only one I enjoyed working with in my projects. We will create our demo application using this particular package.

We can use the flag with --date or -date, Go already does the automatic check. We can make our entire boilerplate with this approach, but let's make it a little easier and use the Cobra CLI package.

In this tutorial, we'll walk through the process of creating a simple command-line tool similar to curl using Go and Cobra, a CLI library for Go.

I use https://github.com/spf13/cobra religiously for this kind of thing - it handles all the annoying corner cases of parsing flags, and also has an intuitive notion of subcommands (with basic usage/help text generated) for picking which task you want to run with positional arguments.

We recently chose cobra[1] to create a cli application. It comes with so many best practices already packaged like autocompletions, help texts etc. etc.

[1]: https://github.com/spf13/cobra

github.com/spf13/cobra

I looked at the docs: https://cobra.dev/ ... and there are only examples on how to add new flags.

For installing Cobra-CLI you can go to Cobraor run go install github.com/spf13/cobra-cli@latest in the terminal.

In my build phase, I compile the source to create a k3sup binary and I also run the binary to generate shell script completions. Give kudos to this functionality which comes from spf13/cobra Go library for CLIs.

NWA is a command-line tool built on cobra. Here's an overview of NWA's commands: