go-i18n

I name them by component.context.phrase There's https://cldr.unicode.org/index . In Angular I liked Transloco [0] very much. For Vue I use vue-i18n, I don't think there's any alternative. For Go I like go-i18n [1] when doing SSR Go. For Svelte.. not sure if there's a best package. [0] https://github.com/ngneat/transloco [1] https://github.com/nicksnyder/go-i18n

With the release of Go 1.13, I've recently started digging into Go modules in order to upgrade my code base. After a whole day of reading and researching, I'm still baffled by some of the features. In particular, I find problematic the combination of these two pieces of docs: 1 About semantic import versioning: https://github.com/golang/go/wiki/Modules#semantic-import-versioning 2 Releasing a v2+ module: https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher Basically they turned a piece of advice into a requirement. I'm talking about the import compatibility rule, summarized by this statement: "If an old package and a new package have the same import path, the new package must be backwards compatible with the old package." This mostly results in having to maintain either separate branches, or even same-branch separate s