TLDR; CrowdIn is finally here. All we have to do is update .en.json and CrowdIn will keep the other languages in sync, using the english strings from .en.json as placeholders.
Sweet! Anything I have to take care of if I have some message strings (not for the editor but the content) that need localization?
I think they all were gathered in semantics.json as a group named "l10n" or "UI" and labeled "Localization", but this seems to be different among content types. I would want other content types to be able to identify those. For example, IV puts all the localization stuff for interactions at the bottom. I wouldn't want to break that. How does the editor identify the strings that are supposed to appear as "Text overrides and translations"?
For others with the same question: Just add an element with the attribute common = true to semantics.json containing your text items and H5P will figure out that those are meant for translation and add the "Text overrides and translations" section to the editor.
tim
Thu, 08/17/2017 - 08:46
Permalink
Yes, I'm going to explain it
Yes, I'm going to explain it a bit more in the release note but here's the updated documentation:
https://h5p.org/contributing
TLDR; CrowdIn is finally here. All we have to do is update .en.json and CrowdIn will keep the other languages in sync, using the english strings from .en.json as placeholders.
otacke
Thu, 08/17/2017 - 11:57
Permalink
Sweet! Anything I have to
Sweet! Anything I have to take care of if I have some message strings (not for the editor but the content) that need localization?
I think they all were gathered in semantics.json as a group named "l10n" or "UI" and labeled "Localization", but this seems to be different among content types. I would want other content types to be able to identify those. For example, IV puts all the localization stuff for interactions at the bottom. I wouldn't want to break that. How does the editor identify the strings that are supposed to appear as "Text overrides and translations"?
otacke
Thu, 08/17/2017 - 13:22
Permalink
Okay, I might have well tried
Okay, I might have well tried it myself first ;-)
For others with the same question: Just add an element with the attribute common = true to semantics.json containing your text items and H5P will figure out that those are meant for translation and add the "Text overrides and translations" section to the editor.
tim
Fri, 08/18/2017 - 10:05
Permalink
Thanks for documenting your
Thanks for documenting your findings otacke :))