major
nice-to-have
minor
Images can be uploaded and embedded in WYSIWYG attributes. And WYSIWYG attributes can be I18N attributes, meaning they display one input field per language. However, images can no longer be uploaded in such I18N WYSIWYG attributes.
Improvement
It should also be possible to upload images in I18N-WYSIWYG attributes. To achieve this, it is necessary to use something other than StringFields —something that StructuredText can use as a model. In non-I18N-WYSIWYG attributes, HiddenFields are used for this purpose.
Accordingly, the StructuredText feature set `i18n-html ` should also be extended to include the missing features that are not yet present compared to the `html` feature set: `styles`, `insert`, and `links`.
Usage
This will work automatically for all attributes of type tl.model.wysiwyg:Html.
Related Issues
Required as part of #19000: Documentation without images is hard to sell.
Test
- In the demo, it must be possible to upload, save, and display images for the i18NHTMLNormal attribute.
- This must also work when images are used for multiple languages simultaneously.
- This must work both when the same image is used in all languages and when a different image is used in each language.
- The same WYSIWYG functions must be available here as in the html attribute.
- The `html ` attribute must not have lost any WYSIWYG functions. In particular, the images must continue to function properly.