Replies: 1 comment 2 replies
-
@brandonkelly So this is biting me in the rear on a currently in-development project. The site's primary content is RTL, but there's all sorts of fields for things like telephone numbers and URLs that get really, really messed up when rendered as RTL. Worth noting is that said fields are not just the normal Craft fieldtypes, but also things like the 3rd-party Typed Link and Phone Number fields. I'm not sure which is the "proper" way to resolve this, but from my POV it would be great if this were something that was defined and addressed at the CMS level, not at the level of individual plugins. In other words, on an RTL site, if a custom field could be set to LTR (through a control that the CMS provides), then ideally that custom field wouldn't really be aware that the site is RTL at all. |
Beta Was this translation helpful? Give feedback.
-
Ref #9616
It would make sense to be able to override the directionality/language of specific fields to something other than the site language. For example, even in an RTL site, with an RTL user preference, text fields for computer code (for display or for embedding) should 99.99% of the time be LTR.
I can't think of a specific use case for a directionality toggle on fields like dropdowns and the like, only for textual input fields, but I'm not sure if implementing it for textual fields only is a good thing or not.
Now that I think about it though, it might make sense to be able to specify the language of a field (which would supersede the directionality toggle). For example, a scholarly site showing translations of a sentence in multiple languages on the same page. That's not something that multi-site would be able to help with, is it?
Beta Was this translation helpful? Give feedback.
All reactions