New answers tagged

1

Title case of user submitted text is a problem because of names such as MacDonald, acronyms such as BBC, etc. You can code round these cases but unless you control the dataset from the start, there will always be new cases. I have done title case on large datasets but I had the data to begin with and hence could check through and fix any oddities, and even ...


6

Reviews are a very tricky case because if people see you altering user reviews, it may come off as you censoring the reviews. If someone writes an all caps review because they are yelling about bad service, it may look like you changed the case so it doesn't look as bad. I think there are only three ways to go about this: Try to avoid the all caps on the ...


-1

The point is not about how it is written on a single line. Humans are conditioned to reading lists top to bottom or left to right. When you change the orientation, it reduces confusion if top to bottom also coincides with Left to right. For instance, if there are are three books that are Part 1, 2, 3. Our natural way of stacking them would be to keep 1 on ...


0

I agree with "clockwise on right, counter-clockwise on left" approach. My hunch is that this mental mode comes to us from building signage, where text which appears on flags or banners looks more "natural" if its baseline aligns with the building wall (longer, visually dominant surface). Likewise, vertical screen edges are visually dominant surfaces in UI ...


0

This very much is a usability issue, though others might disagree. Best format I can think of while a little heavy on the columns is the only way to guarantee without requiring users to remember hyper-specialized formating codes: A B C D E FREQUENCY EVERY 1ST EVERY 2ND EVERY 3RD EVERY 4TH ...



Top 50 recent answers are included