After an outage on September 1, the Instructure Community is now fully available, including guides, release notes, forums, and groups. If some styling still looks unusual, clear your cache and cookies.
Found this content helpful? Log in or sign up to leave a like!
I found that explicit keys of i18n were described under the section "Deprecated Features" in the Canvas Wiki document https://github.com/instructure/canvas-lms/wiki/I18n. However, I think explicit keys are still useful since there are cases where a string contains multiple meanings in English and there should be different translation for each meaning. For example, at present, there are three places which are using
I18n.t('For')
in Ruby or
{{#t}}For{{/t}}
in handlebars but there are languages which do not have prepositions, so it should be translated to some other descriptions depending on their contexts. I'd like to specify explicit keys to distinguish the meanings of this string. Is that OK? If not, what is the correct way to give proper translations?
To interact with Panda Bot, our automated chatbot, you need to sign up or log in:
Sign inTo interact with Panda Bot, our automated chatbot, you need to sign up or log in:
Sign in