Hey, thank you for the suggestion.
Adding translations to the tool with Weblate is indeed on the backlog. But for now, I want to make the tool work properly first and once it has proven it's utility, move to translate it.
Also, most information around custom ROMs online is in English, so people should know basic English to be able to get help if something goes wrong in the alpha/beta stage of the tool.

I support this request and will provide the Dutch translation once implemented. 🙂

First step is to start using gettext for all strings, that can already be done now. Then setting up the project for multiple languages and possibly using a service like Weblate.

Thank you, I'll look into that :)

I greatly support this issue and would be glad to provide a french translation once t10n and i18n is decided upon.

Also we'll have to remember the website will need translating as well ! Should i open an issue on the website's repo just to be sure ?

Adding translations to the tool with Weblate is indeed on the backlog. But for now, I want to make the tool work properly first and once it has proven it's utility, move to translate it.

What would be required for you to consider your software complete enough so as to start work on integrating other languages ? Do you have a roadmap of the features/issues you want to resolve before moving onto this ?
Would be appreciated, and some might even be able to help you towards that goal :)