✨ Automating Localization import/export (genstrings)

[richardtop]

Is your feature request related to a problem? Please describe.

Currently it seems that the "en" (English) localization file is created manually. Automating this process will ensure no missing keys as well as streamline the update process

Describe the solution you'd like

Use genstrings to extract the LocalizedStringsKey and create the "en" (English) localized file. https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/LoadingResources/Strings/Strings.html

A script could be added to the project that will regenerate all of the English strings, which later can be used to translate the app to other languages.

Describe alternatives you've considered

Doing things manually

Additional context

An automation / DevOps task. If interested, I can submit a PR, although this will require regenerating all of the English strings (thus changing that file completely).

[Jeehut]

I already mentioned an alternative to this in https://github.com/CodeEditApp/CodeEdit/issues/285, which was closed because the app isn't localized yet ... I think the approach I outlined there is superior to using genstrings directly.

[richardtop]

This ticket is not about a concrete implementation of the localizable string export, but about the idea of automating it. The proposed solution is simply the bare minimum that does the job.

[austincondiff]

We haven't forgotten about this and will get to localization soon. Our priority now is getting a preview release out and making what we have more stable.