Translate default fields according to the `request-language`
Discussion from !44 (merged):
The default fields are translated at the start of the generator, when they are added. I fhte locale changes in between, it is potentially bad to start translating the default fields. That's for the users to solve themselves.
Why would that be bad (assuming you are talking about the
request-language
, not the locale? […]
If you really want translated descriptions I think you should create a new issue. I currently don't know a place where this translation could happen so this would be more work and I still think this is not really necessary. The problem is that the company database (where the localization should take place) doesn't provide the default fields (which could then be correctly translated). Doing all of this on the fly is very hard and a lot guessing the correct result. This is very unexpected behaviour for the user and very hard to control for us.
I still don't see how this would be unexpected for the user. As mentioned in #73 (closed), I would also want the user to be able to change the
request-language
manually.If you want to move the default fields to the data repo, that's fine with me.
Anyway, I'm fine with postponing that.