Localization 🌍 #208
FelixMalfait
announced in
.Roadmap
Replies: 2 comments 1 reply
-
If you plan to localize, don't forget custom objects and custom fields. This might be a problem in multi-country companies, since English is not widely used, particularly in sales teams. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Being able to choose formats should probably be implemented well before actual localization. US-styled dates and calendars are especially annoying to deal with for us iso-standard people. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
As some users don't speak english, it could be interesting to offer the software in other languages.
This is probably not something we want to prioritize in the short-term though since it could heavily slow the development workflow.
One alternative we could consider to do this without slowing the development workflows is to have translations be auto-generated through CI, however this would lead to lower quality translations since automatic translation can't perfectly capture nuances and context.
Beta Was this translation helpful? Give feedback.
All reactions