Musicgens-scale-update #612
Conversation
|
@jaburgoyne , I went over the file and added translation tags everywhere. Okay? Or rather keep them out? One unwanted side effect might be that if somebody answered the questionnaire coming from a Dutch language browser, they'd get "Ja" , "Nee", so translations for everything that has been translated. On the other hand, I think it is good practice to make sure our texts are i18n ready. |
|
In this very particular case, @BeritJanssen, it is actually better not to translate. There are 'service' questions for a consortium that is VERY sensitive about exact wording and answer choices, and so I suspect that some of them would want to throw out data even for such trivial changes as Yes becoming Ja for a Dutch speaker. (In just about any other context, of course, I 100% agree that i18n is the way to go.) |
|
@jaburgoyne , we can "enforce" experiments to always be shown in English. Would this be sufficient to ensure we're keeping consortium members happy while already integrating the capability to translate? |
|
Yes, absolutely, @BeritJanssen – good solution! |
Revised scale-point descriptions and added new questions to the MusicGens list (as requested at the September consortium meeting).