Possible conflict with Tiles course format?

[berthelemy]

To replicate

1. Create a course using the Tiles format
2. Create two topics, one with a short title, and one with a long title

3. Switch language to French
4. Turn on inline translations

Expected behaviour

• Both tiles should display the titles, with the translation button

Actual behaviour

• Short titles display OK, with the translation button
• Long titles are truncated, and no translation button is seen. It's not even in the HTML

Is this a Tiles problem, or an issue with the filter?

[berthelemy]

There is a workaround:

Give the translator editing rights over the course (which I was hoping to avoid). They can then switch to editing mode to view the translation buttons.

[jgramp]

What happens if you switch the course format? Do they display properly? It'd be good to note this plugin is not fully compatible with the Tiles format somewhere in the documentation if so. https://docs.moodle.org/311/en/Content_translation_plugin_set

[berthelemy]

@jgramp I took a copy of a portion of the course (to save on Google Translate fees), and then switched it to Topics format.

All the buttons appeared in the right place, as far as I could tell.

So, yes, it looks like the plugin is not fully compatible with the Tiles format. I'm happy to add that to the docs if you're OK with that?

I guess I'll just have to play with the permissions to give the translators some editing rights, but not enough to mess up the courses.

[jgramp]

Thanks @berthelemy .

That would be great if you could add this to the docs!

Hopefully the issue can be resolved at some point. It must have something to do with how this course format renders the topics.

Cheers.

Jess

[berthelemy]

@jgramp All done: https://docs.moodle.org/311/en/Content_translation_plugin_set#Known_issues

[andrewhancox]

The problem is that the tiles plugin is running text through the format_string/format_text function as expected and then truncating it to a known length to ensure it will render in a predictable way. It's not really anyone's fault...

It may be that by editing the function \filter_translations::filter and changing it to add the translation information to the start of the string instead of the end the issue would be avoided but... I would worry that there may be other consequences so it would need testing.