Skip to content

"check category failure title" and "check category success title" shouldn't use the words "success" and "failure" #2874

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
amire80 opened this issue Apr 10, 2019 · 37 comments · Fixed by #3162

Comments

@amire80
Copy link
Contributor

amire80 commented Apr 10, 2019

These two messages say:

  • Requesting category check: Success
  • Requesting category check: Failed

Using the words "Success" and "Failed" in user interface messages is a bad practice. See the explanation here: https://www.mediawiki.org/wiki/Localisation#Avoid_jargon_and_slang .

They should be rephrased in a more human way. For example:

  • Category check requested
  • Category check request didn't work: explanation with suggested actions
@marcin-kwasniak
Copy link
Contributor

Hi, I made a correction for English, German and Polish.

marcin-kwasniak pushed a commit to marcin-kwasniak/apps-android-commons that referenced this issue Apr 11, 2019
misaochan pushed a commit that referenced this issue Apr 13, 2019
* Avoid jargon and slang, change for default, de and pl (#2874)

* Revert "Avoid jargon and slang, change for default, de and pl (#2874)"

This reverts commit 174efe0.

* check_category_success_title text changed to: Category check requested

* check_category_failure_title new text
@MitchellAugustin
Copy link
Contributor

Hello, I made some more corrections for English

@neslihanturan
Copy link
Collaborator

Reopened because the issue is not completely solved.

@chaytanyasinha
Copy link

May I contribute to this issue.

@akonic
Copy link

akonic commented Nov 29, 2019

@neslihanturan What is left on this issue?

@neslihanturan
Copy link
Collaborator

You can search mentioned strings in strings.xml file and fix them as guided in the issue description.

@a18jouan
Copy link

I found the same problem with two others messages :
Sending Thanks: Failure
Sending Thanks : Success
Can I fix that ?

@neslihanturan
Copy link
Collaborator

Sure @a18jouan , it is yours:)

@vibhusharma101
Copy link

can I Work on this issue if it is not solved yet?

@neslihanturan
Copy link
Collaborator

@a18jouan are you still working on this issue? If not @vibhusharma101 wants to take it.

@avivith
Copy link

avivith commented Mar 11, 2020

Is this issue closed already? if not, what is left to be done?

@FawziyahAlebiosu
Copy link
Contributor

correct me if I'm wrong, it looks like the remaining strings that still contain 'success and failure" are:

<string name="login_success">Login success!</string>

<string name="wallpaper_set_successfully">Wallpaper set successfully!</string>

<string name="send_thank_success_title">Sending Thanks: Success</string>

Meanwhile there are a slew of other words that definitely still use the word 'failed' in user interactions. The link you included in your original post does not give more options on what to say instead of failure.
I can definitely understand how "file was not renamed... use a different name" is a good replacement for failure, but now I'm definitely going to start a running list on what to say in cases like:

someone does not login successfully or
authentication failed. etc

Any suggestions?

@arishtajain14
Copy link

Can this issue be assigned to me and my team?

@darshan934
Copy link

Hello,
Can I clean up the remaining parts of this?

@neslihanturan
Copy link
Collaborator

Thanks for your intersts @darshan934 , @arishta and @FawziyahAlebiosu . I think before start to implement some changes, we need to discuss what has left from this issue and how we should proceed.

@harshsaver
Copy link

Hello, if the issue has not yet been solved, I would like to work on it!

@neslihanturan
Copy link
Collaborator

Hello everyone seems interested, please make sure you noted the remained parts of the issue (ie. related strings) along with your request to work on it. I am not sure if the issue is solved or not and I would like to discuss before you start working on it.

@arishtajain14
Copy link

@neslihanturan
As mentioned by @FawziyahAlebiosu , there are strings which still contain 'success and failure' that need to be replaced.
We could start with that.

@neslihanturan
Copy link
Collaborator

Seems like a good start @arishta , thanks! What kind of replacements do you suggest? If @FawziyahAlebiosu is not interested anymore, you can start to work on this issue (since you were the first interested person after FawziyahAlebiosu). Otherwise, @FawziyahAlebiosu can claim the issue.

@arishtajain14
Copy link

Here are the replacements that I suggest for these strings :

  1. Replace "Login success!" with "You are logged in!", the latter sounds more user friendly.
  2. Replace "Wallpaper set successfully" with "Wallpaper set", since I think the word "successfully" is redundant here.
  3. Replace "Sending Thanks : Success" with "Thanks Sent!".

@neslihanturan
Copy link
Collaborator

Sounds good to me:)

@arishtajain14
Copy link

@neslihanturan since @FawziyahAlebiosu does not seem to be active on this issue, can it assigned to me so that I can start working on it.

@neslihanturan
Copy link
Collaborator

neslihanturan commented Oct 11, 2020

@neslihanturan since @FawziyahAlebiosu does not seem to be active on this issue, can it assigned to me so that I can start working on it.

Please go for it @arishta :)

@arishtajain14
Copy link

@sivaraam My team has submitted a PR request from the user account : isdl03. Kindly review it.

@sivaraam
Copy link
Member

Strangely, I don't see any PRs from the mentioned account. I only see PR #3991 for this issue which doesn't seem to be from the mentioned account. @arishta Could you share a link to the PR or clarify what I'm missing?

@arishtajain14
Copy link

@sivaraam Here is the link to the PR : #4000

@arishtajain14
Copy link

Here is the link to the PR submitted by my team isdl03
link

@misaochan
Copy link
Member

It seems like changes were requested on #4000 . Is there a reason you created a 2nd PR?

@arishtajain14
Copy link

A new member of our team started working on this issue and submitted a new PR. The changes should have been made in existing PR only. We will ensure this in the future.

@AdityaArunSharma
Copy link

@neslihanturan is this issue still open. Can i work on it?

@misaochan
Copy link
Member

misaochan commented Dec 1, 2020

@arishta Would you /your teammate like to make the requested changes in #4000 ?

@AdityaArunSharma Thanks for your interest, but there is already a PR up for this (pending requested changes). :) If the owner of the PR doesn't make the changes, we can reassign it, but we should give them a bit more time. Please feel free to look for any other issues with the "bug" or "good first issue" label.

@isdl03
Copy link

isdl03 commented Dec 1, 2020

@misaochan Since we are working on two more issues from this app, there has been some delay. We will make the requested changes and submit the PR as soon as possible.
Thanks.

@isdl03
Copy link

isdl03 commented Dec 1, 2020

@misaochan We are unable to make the changes in the current PR #4024 . Is it alright if we create a new PR?

@misaochan
Copy link
Member

Hi @isdl03 , it seems like this is the 3rd PR you are creating for fixing a small issue. Could you elaborate on the problems you are experiencing with just pushing your changes to the existing PR? Maybe we can help you.

@isdl03
Copy link

isdl03 commented Dec 3, 2020

@misaochan PR #4024 is showing changes in the complete file, and we could not get rid of these unnecessary changes.

@sivaraam
Copy link
Member

sivaraam commented Dec 3, 2020

@isdl03 PR #4000 didn't have unnecessary changes. So, you could try updating that.

@arishtajain14
Copy link

We have made the changes as requested in the PR #4000.
Kindly review the same.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment