General question about internationalization

[kjuice276]

I'm a beginner and I know how to work with I18N. when creating dynamic classroom pages how can I internationalize them? like for the classroom name and description how we are going to make it internationalized?

@Nik-09 @seanlip

[DubeySandeep]

Maybe have schema/dict for each page where the key is the section name and the value is i18n_key

classRoomNameToSectionI18n = {
  maths: {
      title: 'I18N...",
      paragraph1: "I18N..." 
    },
  finance: {...},
  ...
}

Later in the component select the section:

currentPageI18n = classRoomNameToSectionI18n[currentClassRoomName]

In template:

{{ currentPageI18n.title | translate }}

Can we do this or something around that?

[kjuice276]

@DubeySandeep but we still have to update the I18N files before launching any new classroom?? which is not fully dynamic atleast show in english by default

[Nik-09]

Hi @kjuice276 under the scope of the project (and in general) we need to update only en.json and qqq.json. It is fine to show English text in the meantime. Our translations-team will help to write translations in other languages that we support.
Thanks.

[kjuice276]

@Nik-09 thanks but my question is as a admin i should be able to create new calssrooms with title, description, banner and image directly like we create topic....

[Nik-09]

Currently, for classroom names, we use a technique called hacky translation i.e., if the translation is present in assets/i18n then show the translation else present the default English text.

<span *ngIf="!isHackyClassroomTranslationDisplayed()">
  {{ classroomDisplayName }}
</span>
<span *ngIf="isHackyClassroomTranslationDisplayed()">
  {{ classroomNameTranslationKey | translate }}
</span>

We wanted to follow this same technique for other fields e.g., Topics covered, Course details.
Let me know if this does not answer your question or if you need more explanation, I will be happy to guide.
Thanks

[kjuice276]

ohh this helps thanks