..It could have all been avoided if they were put up in English to begin with. There have been quite a few assets loaded up recently that the name doesn't give an indication to what it is, nor the description and nor the thumbnail, pretty unhelpful really..
I agree on both counts Ian - language and thumbnails.
The 'username' and 'description' tags are mandatory and meant to contain English text, while support for non-English text is available via 'username-xx' and 'description-xx' tags. In too many assets we see non-English text in the 'username' and 'description' fields - which is technically wrong and a pain in the caboose. N3V seem unwilling to enforce their standard, so this doesn't even produce a warning.
On the other hand, they don't mind tampering with perfectly legal English-language assets and adding various, seemingly random, non-English tags to the configs of built-in assets. I've never seen it go the other way where, for example, an asset with a German name in the (supposedly English) username field is corrected to make it English and move the German text into a username-de field. Perhaps I've misunderstood the rules, or not looked hard enough for examples of such corrections, but in any case there are many inconsistencies and double-standards in this area.
Uninformative thumbnails (or 'thumpnails' as one creator keeps calling them
) - again a great source of annoyance. It's so quick and easy to make a reasonable thumbnail image compared to the effort needed to make the asset itself. I think it's the height of laziness to use generic logos instead of showing each individual asset. Once again however, this sin does not attract a warning or an error, so the practice continues.
But none of that impinges on or diminishes the quality of the assets, just makes them harder to find when you're looking for them.
.
