-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Use ellipsis - part 1 #38638
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use ellipsis - part 1 #38638
Conversation
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
tecpromotion
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe this should be separated. Already hyphenated and lowercase elsewhere.
Co-authored-by: Stefan Wendhausen <[email protected]>
Co-authored-by: Stefan Wendhausen <[email protected]>
Sorry I dont understand what you are saying - maybe I need more coffee |
tecpromotion
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @brianteeman
|
I have tested this item ✅ successfully on 56ac93c This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/38638. |
|
@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 ✅ successfully on 56ac93c This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/38638. |
|
RTC This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/38638. |
|
@brianteeman https://developer.joomla.org/en-gb-user-interface-text-guidelines/punctuation.html Notice it says "three periods" |
|
@N6REJ thanks - the docs have been updated just waiting for a merge |
|
Thank you |
|
thanks |
joomla/joomla-cms#38638 + joomla/joomla-cms#38622 + joomla/joomla-cms#38619 + joomla/joomla-cms#38592 + joomla/joomla-cms#38541 - (только для en-GB) joomla/joomla-cms#38537 - (только для en-GB) joomla/joomla-cms#38570 + joomla/joomla-cms#38459 + joomla/joomla-cms#38451 + joomla/joomla-cms#38449 + joomla/joomla-cms#38313 + joomla/joomla-cms#38447 +
|
Also in joomla-cms/language/en-GB/com_media.ini Line 101 in 835d986
and
|
|
@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? |
**I was wrong and should have listened more to what @HLeithner was saying.** He was obviously correct that you can't use &hellip, in a language string in the cli. I still think the lack of readability of using utf characters in a search string is an issue so I have reverted the use to ... I have also reviewed all the other changes that I made in that PR and instead of reverting I am removing the … as it really served no purpose As far as I can see now the remaining uses from that PR all relate to Read more where I still believe it is best to use &hellip but I would be happy to revert those as well. Sorry for causing this issue. I am not sure if we are in a freeze for strings in 4.2 so if required I can rebase to 4.3

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