-
Notifications
You must be signed in to change notification settings - Fork 1.3k
"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
Comments
Hi, I made a correction for English, German and Polish. |
…s-app#2874)" This reverts commit 174efe0.
Hello, I made some more corrections for English |
Reopened because the issue is not completely solved. |
May I contribute to this issue. |
@neslihanturan What is left on this issue? |
You can search mentioned strings in strings.xml file and fix them as guided in the issue description. |
I found the same problem with two others messages : |
Sure @a18jouan , it is yours:) |
can I Work on this issue if it is not solved yet? |
@a18jouan are you still working on this issue? If not @vibhusharma101 wants to take it. |
Is this issue closed already? if not, what is left to be done? |
correct me if I'm wrong, it looks like the remaining strings that still contain 'success and failure" are:
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 Any suggestions? |
Can this issue be assigned to me and my team? |
Hello, |
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. |
Hello, if the issue has not yet been solved, I would like to work on it! |
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. |
@neslihanturan |
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. |
Here are the replacements that I suggest for these strings :
|
Sounds good to me:) |
@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 :) |
@sivaraam My team has submitted a PR request from the user account : isdl03. Kindly review it. |
Here is the link to the PR submitted by my team isdl03 |
It seems like changes were requested on #4000 . Is there a reason you created a 2nd PR? |
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. |
@neslihanturan is this issue still open. Can i work on it? |
@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. |
@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. |
@misaochan We are unable to make the changes in the current PR #4024 . Is it alright if we create a new PR? |
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. |
@misaochan PR #4024 is showing changes in the complete file, and we could not get rid of these unnecessary changes. |
We have made the changes as requested in the PR #4000. |
These two messages say:
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:
The text was updated successfully, but these errors were encountered: