Not sure what didi is, but I would not integrate Google Translate to any application. The translation quality fluctuates a lot, from quite good to completely wrong. Integrating Google Translate says that I back up these translations. End users can use Google Translate or whatever translation mechanism they prefer themselves.
Translations are an architectural choice. That means it is a big decision and also hard to change later on. You want to support translations early on, with at least two languages. Preferably the translations would be in some standard format, so the translations can be loaded to a translation interface (e.g. Poedit), making life easier for translators.
Then you also have to consider localization, things that are not translations, but other things that are culturally different. That can be things like date formats, but also layouts.
How’s it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK 🇬🇧
Education
10 plus years* active enterprise development experience and a Fine art degree 🎨
I suppose to give some context, didi is a cli and configuration frontend for a compiler. That and the docs are all public facing. The project is open source (community driven project) and if didi facilitates the ability to easily add translations localization then that might be the way to go. There is a wonderful i18next library I found today for such a task.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Not sure what didi is, but I would not integrate Google Translate to any application. The translation quality fluctuates a lot, from quite good to completely wrong. Integrating Google Translate says that I back up these translations. End users can use Google Translate or whatever translation mechanism they prefer themselves.
Translations are an architectural choice. That means it is a big decision and also hard to change later on. You want to support translations early on, with at least two languages. Preferably the translations would be in some standard format, so the translations can be loaded to a translation interface (e.g. Poedit), making life easier for translators.
Then you also have to consider localization, things that are not translations, but other things that are culturally different. That can be things like date formats, but also layouts.
I suppose to give some context, didi is a cli and configuration frontend for a compiler. That and the docs are all public facing. The project is open source (community driven project) and if didi facilitates the ability to easily add translations localization then that might be the way to go. There is a wonderful i18next library I found today for such a task.