Replies: 1 comment 1 reply
-
|
An observation (unrelated to the topic raised) - keeping the language codes similar/consistent with the Unicode CLDR might be useful in the long run when considering i18n readiness. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
According to our earlier understanding, we would be specifying languages of delivery of a session in its fulfilment. Meaning; a session could have multiple slots in different languages at different times. Something like this:
The above schema specifies that a session will be delivered in both Hindi and English during a single fulfilment. Like that, this session can have other fulfilments with other set of languages.
But current schema doesn't have this languages field and hence doesn't satisfy above requirement. So how do we specify languages of delivery of a session? Can we add languages schema to root of fulfilment?
Note: Just to clarify, we did add a languages field to Person schema (Here: #327), but that simply indicates that the person knows those languages and isn't directly related to the sessions being taken by that person.
cc: @ravi-prakash-v, @aks30, @vijiurs, @kiranharidas187
Beta Was this translation helpful? Give feedback.
All reactions