Hi Ralf,
I have written some tooling to bring the TinyMCE langpacks in and turn them into Moodle language strings. I need to do a little bit of work to get them to apply to other languages, but it’s on my agenda for the next few days. Unfortunately I’ve had a sick wife and child over the past few weeks which has pushed a few things down my list and I’m tryin got get everything done before the release.
I need to speak to Koen or Victor to find out the best format to incorporate these, and I’m looking into an optimization that we may also need to make to accommodate a limitation in AMOS.
I’d advise holding off a few days before translating TinyMCE while I try and get things sorted.
Best wishes,
Andrew
Any time Andrew, just give me a ping 
.
We don't have a really good solution for the translation of third party integrated components in Moodle - I don't think it is even possible.
Included in core are the H5P-components, which are terrible to translate the last time I looked, there is BigBlueButton and now TinyMCE - may be I missed one. The integrations with plugins are sometimes closed source components not available in your language at all - I think of things like plagiarism plugins with a translatable Moodle interface, but sending back untranslatable reports.
As for TinyMCE - it is of course right in your face as soon as you start using Moodle - it's everywhere. So no compromises possible in the quality of the translation. Wording, capitalisation etc should be in sync with the rest of the language pack. From your post and the post by the bot, earlier mentioned, I get the impression that the strings for TinyMCE will be available in AMOS, which would be great. At the moment there are only two new strings on top of the loads of 2.4 TinyMCE-strings.
We don't have a really good solution for the translation of third party integrated components in Moodle - I don't think it is even possible.
Included in core are the H5P-components, which are terrible to translate the last time I looked, there is BigBlueButton and now TinyMCE - may be I missed one. The integrations with plugins are sometimes closed source components not available in your language at all - I think of things like plagiarism plugins with a translatable Moodle interface, but sending back untranslatable reports.
As for TinyMCE - it is of course right in your face as soon as you start using Moodle - it's everywhere. So no compromises possible in the quality of the translation. Wording, capitalisation etc should be in sync with the rest of the language pack. From your post and the post by the bot, earlier mentioned, I get the impression that the strings for TinyMCE will be available in AMOS, which would be great. At the moment there are only two new strings on top of the loads of 2.4 TinyMCE-strings.
Hi Andrew,
I translated all strings of the "Editor Tiny" for the german language pack. How do we get the translated editor? I think we will find better translations for some strings but we should see these strings in the platform.
Berst regards,
Ralf
I translated all strings of the "Editor Tiny" for the german language pack. How do we get the translated editor? I think we will find better translations for some strings but we should see these strings in the platform.
Berst regards,
Ralf
Hi Andrew,
why do we need to translate the new editor tiny for Moodle when there are a lot of translations on the tiny page? I just found this page. https://www.tiny.cloud/get-tiny/language-packages/
why do we need to translate the new editor tiny for Moodle when there are a lot of translations on the tiny page? I just found this page. https://www.tiny.cloud/get-tiny/language-packages/
Hi Ralf, found your tracker about the error MDL-76986. Added information about the error, identified that all language locale variations do not work.
For example, locales containing only 2 characters like es, du, fr, ja and pt the translation loads correctly. But the variations es_mx, de_du, fr_ca, ja_kids and pt_br the translation doesn't work.
I am also posting this here with the hope that this issue will gain more visibility. ;)
Suggestion: It would be more appropriate to update the issue to refer to Tiny6 instead of TinyMCE.
For example, locales containing only 2 characters like es, du, fr, ja and pt the translation loads correctly. But the variations es_mx, de_du, fr_ca, ja_kids and pt_br the translation doesn't work.
I am also posting this here with the hope that this issue will gain more visibility. ;)
Suggestion: It would be more appropriate to update the issue to refer to Tiny6 instead of TinyMCE.
Yes, the problem exists for the child languages. The german child package de_du is made for schools, de_kids is made specially for primary schools. In these cases the untranslated tiny editor is a blocker!