Normalize casing in UI text in English

[wetneb]

We do not use a consistent casing throughout the UI.
For instance, in the "Export" menu:

• "Custom tabular exporter" versus "SQL Exporter"

In the "SQL Exporter" dialog:

• "Output empty row (i.e. all cells null)" vs "Trim Column Names"

Expected Behavior

We should consistently use lowercase since that is what is used in most places so far.

To solve this issue

Simply go through the existing translation files (in English) and normalize the phrases with incorrect casing.

[allanaaa]

Thanks for this. Just want to mention an example: "Drop Statement" should become "DROP statement"

[steve-kasica]

This seems like a good issue to tackle as I get familiar with the UI code. I could probably resolve it sometime this week.

[thadguidry]

Great Steve! Go for it! Appreciate all the help we can get on our issues and roadmap!

[leoshrey]

I would like to tackle it, if @swkasica not proceeding...

[steve-kasica]

@leoshrey I am proceeding.

[leoshrey]

Sure thing, please go ahead.

[steve-kasica]

Quick update: I'm about halfway through. End of term stuff took longer than I anticipated. Grammar is kind of tricky in UI because in addition to the normal rules of grammar and usage, there's UX specific conventions. I'm adapting these guidelines from Firefox UX on when to use different capitalization styles: title case, sentence, case, all caps, lowercase, camel case, etc...

[SmritiSharmaBG]

Hello, I am new to Open Source. I want to know if this bug is fixed? If it is fixed and merged then why is it still showing up in Issues section? If not, then can I start to work on it? Any help/feedback will be appreciated. Thankyou :)

[wetneb]

We should ask @swkasica first, to see if he is still working on this.

[steve-kasica]

Hi all,

Sorry I haven't had time to work on this issue this month. Academic stuff has consumed all my time. To boot, my computer died a week ago and I don't have a way of running OpenRefine 😢. But I will have more free time by February 4th (and hopefully a real computer too 🤞).

@SmritiSharmaBG, please feel free to work on this issue but keep me in the loop because I have done a bit of work addressing this issue. I think it requires a bit more thought than just changing the specific examples pointed out in this thread. OpenRefine currently doesn't have a set of guidelines on capitalization. So I was creating some based on the guidelines from the Firefox UX, and implementing these rules throughout the entire interface in English. These fixed the issues mentioned above, but also other areas of the interface where casing isn't consistent.