I had the same problem, had to search for a while, principally because the buttons are all dark grey. In user interface design, gray and especially dark gray is universally associated with inactive items. Naturally, I was looking for a working button so I overlooked the dark gray icon several times.
Professionally, I have been creating user interfaces for cars for 20 years now, so I think I can claim that the argument it is more than just my personal taste. The selection of dark gray here is very unfortunate and intuitively misleading.
Is there a different default skin available that does show active buttons as disabled?
Once you know it is there, you have it on the same place everywhere.
Discourse UI uses grey to distinguish unique content (our posts, who post it) from repetitive things (icons, navogation, etc). It allows to focus on content, which seems a good approach to me.
Using different shades of grey for different prominence seems to be a little inconsistent with UI one is used to elsewhere (i.e. various UX guidelines). I notice the recycling bin icon next to the button to post this text also looks as if it is disabled.
Yes this is part of the problem for some new user just wanting to have a look and give it a try without logging in. But it is true that the grey icons simulate being deactivated, Nop is definitely right here.
Nevertheless I believe this is not a major problem, as soon as you move the mouse over the icons they change in colour which makes it clear they are active. I was a bit confused at first but it did not take me long to find our how it works.
I have to admit that I like the idea because the grey buttons are much more discreet than rows of various coloured buttons and such helping to keep the focus on the content rather than the colourful surface, as cquest mentioned.
Im Anbetracht der Tatsache, dass der -Button zum Ăbersetzen in einer internationalen Community wie der unseren eine doch recht wichtige Rolle einnimmt und dass das verwendete Icon nicht eines ist, das gemeinhin bekannt ist (im Gegensatz zu , usw.), macht es gegebenenfalls Sinn, dem Button einen Text-Titel zu geben. Also
I do not think this would be a real problem. Unregistered users just âhaving a lookâ do not have access to the translation feature and I think this is absolutely ok considering the costs depending on the number of translations done.
Registered users however will get used to that icon within no time. From that point of view no need to change the icon imho.
Ich denke es wĂ€re gut, nur ein Icon in Zusammenhang mit Ăbersetzungen zu verwenden, um MissverstĂ€ndnisse zu vermeiden. Wenn sich das leicht konfigurieren lĂ€sst, könnte das auch das Wikipedia-Icon sein.
1 Like
Mammi71
(One feature, Six mappers and still More ways to map it)
10
Das kann ich nicht bestĂ€tigen. Vielleicht fĂŒr Menschen, die dieses Symbol in Wikipedia nutzen. Ich nicht. Ich habe erst in dieser Diskussion gelernt, was es bedeutet.
+1
volle Zustimmung. Ich muss es regelmĂ€Ăig nutzen und denke da auch nicht mehr darĂŒber nach.
Just out of curiosity, I let bing retranslate its translation. Not only does it miss the proverbial language, it also misses colloquial language: âschonâ is not a temporal adverb in this sentence.
This does not answer though:
Why is the post of ezekielf hidden? I cannot see, who flagged it?
Should topic titles in lists be translatable too? Like Nop proposed.
Why is the post of ezekielf hidden? I cannot see, who flagged it?
I flagged it as âoff topicâ because I wanted to suggest to branch this discussion into an own topic. Not sure how this works in Discourse. Apparently a flagged post is hidden immediately until a mod decides what to do with the flagging(?)
I am not even sure if Discourse allows (mods) to branch off discussions.
Should topic titles in lists be translatable too? Like Nop proposed.
There is no reason why they shouldnât. It is simply not implemented in that plugin we are using.
The plugin is not really actively developed, but maybe if someone fluent in Ruby created a PR, it would be merged.