User tests: Successful: Unsuccessful:
Following the style guide and accessibility recommendations this PR changes the use of ... (dot dot dot) to the html entity for an ellipsis.
For example some screenreaders will announce the three dots eg read more dot dot dot but with an ellipsis they pause and do not say dot dot dot
This PR is only for the language strings. A further PR will follow to address truncation
PARTIAL Pull Request for Issue #38630
Status | New | ⇒ | Pending |
Category | ⇒ | Administration Language & Strings Installation |
Labels |
Added:
Language Change
?
|
I have tested this item
@brianteeman docs will need to be updated as it specifically states "three periods"
Where? Search didn't find any. https://docs.joomla.org/index.php?title=Special:Search&profile=default&search=%22three%20periods%22&fulltext=1
I have tested this item
Status | Pending | ⇒ | Ready to Commit |
RTC
@brianteeman https://developer.joomla.org/en-gb-user-interface-text-guidelines/punctuation.html
An ellipsis is a set of three periods ( ... ) indicating an omission. The group of periods should have a single space on either side. Unless it is at the end of a string where there is no space or period after.
Example
Read more ...
Create some text ... add some pictures.
Notice it says "three periods"
Labels |
Added:
?
|
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-08-31 20:34:39 |
Closed_By | ⇒ | roland-d |
Thank you
thanks
@Razzo1987 thanks - see #38710
What's the reason why you use the html encoding & hellip ; instead of the utf8 character … ?
Clarity.
can we please change this because this would not work in cli script or non-browser context, afaik is that we try to avoid html encoding in language files and use utf8 directly (it's done for easy writing)
No I will not change it and we have plenty of html in our strings.
&hellip is easier to type and visually an editor will not mistakenly type ... when they mean …
As already explained we must use an ellipsis for accessibility and changing to use the utf8 … from the ... will not help as translators etc will not SEE that they are different and will continue to type ... especially as its much easier to type ... than it is to look up the utf8 character. It's certainly easier for me to type &hellip than it is to open a character map and locate the utf8 map and then locate the ellipsis and insert it into a document
That one which also works outside of a webbrowser.
OK so the Unicode consortium are all idiots and we should go back to ascii and HTML encoding. Makes sense to me.
forget the "idiots", I already argument like other people in this tracker and that makes it sick. People are doing anyway what they want to do so I should not take this personally and look at my health.
I know many of the unicode consortium, spoken at their conference twice, nice people. However, unfortunately, much of their work is not accessible at all or more accurately is misused and is therefore not accessible and we have no control/influence on how the different screen reader applications work. - they're all different to each other most of the time.
No one was forced to merge this
is it possible to add the … to tiny as I'm darn sure never going to remember that and I use ... almost hourly
What does that have to do with changing language strings?
Sorry I dont understand what you are saying - maybe I need more coffee