Browse keywords uses case-sensitive index
When going to browse keywords there are due case-sensitiveness for some letters two indexes, e.g. there is l
and a L
. But the layout makes it that you don't see the difference in the subheading, it looks always like upper-letter. In general, the feeling would be, that for creating the letter indexes, the case should be ignored, so that there is only one L
with both the lower l
and the upper L
combined and sorted case-insensitive.
How do others feel? @lbarbot @stefan.probst (and I think this is not coming from backend, as /api/item-search
don't give an option to order the delivered keywords, thus frontend does it by its own, right?)