it is associated when the icon is grey. as one may directly click on the icons, one will get in the side by side an empty item already tagged to the chosen language when it is orange.

That's a MASSIVE accessibility fail. You should NEVER just use a colour to
indicate anything.

On 11 Mar 2017 5:44 p.m., "infograf768" notifications@github.com wrote:

it is associated when the icon is grey. as one may directly click on the
icons, one will get in the side by side an empty item already tagged to the
chosen language when it is orange.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#14490 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPH8XQABHZ97yECfKQzL8jaAovj1vsMks5rkt2KgaJpZM4MaO5n
.

i would not use UPPERCASE like this, but, anyway, the intent was to show if an item was already associated or not in the available content languages.
To keep this information (which is important), i am sure it would be possible to display another column titled something like 'Not yet Associated' to separate them.

This code is an accessibility fail. It can't be released like this. We
should take accessibility seriously.

On 11 Mar 2017 7:44 p.m., "infograf768" notifications@github.com wrote:

i would not use UPPERCASE like this, but, anyway, the intent was to show
if an item was already associated or not in the available content languages.
To keep this information (which is important), i am sure it would be
possible to display another column titled something like 'Not yet
Associated' to separate them.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#14490 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPH8f82t87Pe_e0EZVWdR_1FZ_9Y5pvks5rkvmSgaJpZM4MaO5n
.

cool. i will,look at this tomorrow.

@brianteeman
would that be OK for you?

1. Technically this will still fail accessibility rules as you are still using colour to indicate a meaning.

1.4.1. Use of Color: Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. (Level A)

2. What is the purpose of even showing the not associated languages? The list of languages you are generating it the list of installed site languages. NOT the content languages. On a site at joomla.com for example where all the available joomla languages are installed you would have a list of 60+ languages here.

So surely you only need to be using content languages not installed languages and I still dont see the use case for showing languages that do not have associations. But if you have a use case for that then you must find a way not to only use color as the sole means of conveying information

I was opposed to the fact that Content languages were created at the same time as languages was installed. And that is indeed what would happen now if more languages than necessary are installed...
In any case, I doubt that users would install more languages than they need. The multilang feature in core is not designed to take care of big sites with dozains of languages and thousands of items

The column heading in this proposal indicates clearly that there is no associations for these content languages. The color is only added to differentiate easily.
Clicking on one of them displays directly the Target for the language instead of multiple clicks once in the side by side.

If no one agrees with the GSOC group on this matter, it is very simple to only show the languages which do have associations. Using a false instead of true in the tmpl.

@alikon @rdeutz @dgt41
What do you think? In both cases, I can patch easily.

The multilang feature in core is not designed to take care of big sites with dozains of languages and thousands of items

Hmmm, com_assosiations, com_fields and com_tags fall in the same category. The idea of adding more functionality with a high price tag on performance makes the cms a toy...
Let's go back to the idea of modularising the system, there are better solutions for tags, fields and multilingual from 3PDs

@dgt41
That was not the question here. ?
Shall we present only the associated items in one column or use 2 columns as Brian is opposed to the present situation?

? for the two colums.

My comments are nothing to do with one or two columns

My comments are threefold -

1. accessibility - current one column and two column proposals both fail
2. what is the purpose of showing languages that do not have an association
3. why are we showing installed languages as opposed to content languages. Remember as I stated that joomla.com is preinstalled with all languages

3. We are showing Content Languages and not Installed languages.
   You can see that easily by deleting one of the automatically created Content Languages.

4. The purpose of showing languages that do not have an association is clear: it is a very important information and I already explained that it saves clicks.

5. I do nit see why using 2 columns changes accessibility: it is a list.

Making PR now.

We are showing Content Languages and not Installed languages.

You can see that easily by deleting one of the automatically created Content Languages.

Ah so it is using content languages but completely ignoring if the content language is published?

it also ignores if the content language is trashed

The system we have and had since 1.6 is that one can prepare a full Content Language and publish it only when ready.
As for Trashed, it is as everything in J!: if not deleted it still exists.

We dont display categories that are trashed ;)

(now that I know it is referring to content and not installed languages we can ignore the joomla.com comments

#14530

Closed as we have a patch.

Set to "closed" on behalf of @infograf768 by The JTracker Application at issues.joomla.org/joomla-cms/14490

just one note as I worked on it, I saw that to show a status with only one indicator is not a brillant idea but I was focused on the functionality. It is something we should look at.

reopened as we no longer have a patch

closing again as the patch has been re-opened