[Localization] Translation effort for Instruqt tracks

[rh-tchuang]

Hi @cloin I'm opening this issue to track our effort of localizing the Instruqt files into Japanese.

I will proceed with further testings by trying to lock some of the keys and see if the source content imports better in our TMS. Attaching a screenshot of the issue we've observed in Memsource.

Thanks for the call today, was very informative!

[rh-tchuang]

Hi @cloin Just wondering if you've had a chance to get some screen shots/guides drafted so we can follow them as a guideline :) ?

Cheers! Terry

[cloin]

Hello! The assignment.md files contain markdown with metadata. Metadata and markdown sections are separated by ---. The metadata section is formatted as key: value (e.g. "title: Incident creation") where the key (in previous example, key would be title) can not be localized but the value can be.

There are some cases where neither the key nor the value can be localized. In the picture attached, you can see the first 3 lines of the file cannot be localized (noted by the red box), whereas the values on lines 5 and 6 can be localized (noted by the green box around those values)

Here's a rough idea of what can be localized within the assignment.md file of a track challenge:

There are some tracks that utilize in-line scripts interspersed with markdown that may contain strings requiring localization, but these may have to be manually updated.

Is this enough to get started?

[rh-tchuang]

Hi @cloin We have translated some tracks and I've pushed them to: https://github.com/Red-Hat-l10n/Ansible-Instruqt/tree/devel/tracks I've invited you as a maintainer so that you can take a look at the translated content and let me know if they look okay. Not all tracks have been localized yet but we're working through them in the next couple of weeks. Please let me know what you think. Terry