Skip to content
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

Add translations in users/settings.html.erb (2) #9295

Closed
5 tasks
Manasa2850 opened this issue Mar 12, 2021 · 2 comments · Fixed by #9297
Closed
5 tasks

Add translations in users/settings.html.erb (2) #9295

Manasa2850 opened this issue Mar 12, 2021 · 2 comments · Fixed by #9297
Labels
first-timers-only They need to be well-formatted using the First-timers_Issue_Template. gsoc outreachy

Comments

@Manasa2850
Copy link
Member

Hi, this is a first-timers-only issue. This means we've worked to make it more legible to folks who either haven't contributed to our codebase before, or even folks who haven't contributed to open source before.

If that's you, we're interested in helping you take the first step and can answer questions and help you out as you do. Note that we're especially interested in contributions from people from groups underrepresented in free and open source software!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

If you have contributed before, consider leaving this one for someone new, and looking through our general help wanted issues. Thanks!

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

  • 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

  • 📝 Update the file app/views/users/settings.html.erb in the plots2 repository (press the little pen Icon) and edit the line as shown below.

See this page for some help in taking your first steps!

Below is a "diff" showing in red (and a -) which lines to remove, and in green (and a +) which lines to add:

-<h4><b>Email notifications are sent for each post in topics you follow. If you prefer to receive a digest, choose one of these options: </b></h4>
+<h4><b><%=translation('users.settings.email_notifications')%> </b></h4>

  <div style="display: inline-flex; justify-content: space-between; width: 90%;">
-    <span>In a weekly digest </span>
+    <span><%=translation('users.settings.weekly_digest')%> </span>
    <span>
    <label style=" vertical-align: middle;" class="switch">
      <p> Notification switch </p>
      <input type="checkbox" name="digest:weekly" <% if UserTag.exists?(current_user.id, 'digest:weekly') %>checked<% end %>>
      <span class="slider round"></span>
    </label>
    </span>
  </div>

  <br />
  <br />

  <div style="display: inline-flex; justify-content: space-between; width: 90%;">
-    <span>In a daily digest</span>
+    <span><%=translation('users.settings.daily_digest')%> </span>
    <span>
    <label style=" vertical-align: middle;" class="switch">
      <p> Notification switch </p>
      <input type="checkbox" name="digest:daily" <% if UserTag.exists?(current_user.id, 'digest:daily') %>checked<% end %>>
      <span class="slider round"></span>
    </label>
    </span>
  </div>

  <br />
  <br />

  <% if current_user.can_moderate? %>
    <div style="display: inline-flex; justify-content: space-between; width: 90%;">
-      <span>In a weekly digest for unmoderated posts</span>
+      <span><%=translation('users.settings.spam_weekly_digest')%> </span>
      <span>
        <label style=" vertical-align: middle;" class="switch">
          <p> Notification switch </p>
          <input type="checkbox" name="digest:weekly:spam" <% if UserTag.exists?(current_user.id, 'digest:weekly:spam') %>checked<% end %>>
          <span class="slider round"></span>
        </label>
      </span>
    </div>

    <br />
    <br />

    <div style="display: inline-flex; justify-content: space-between; width: 90%;">
-      <span>In a daily digest for unmoderated posts</span>
+      <span><%=translation('users.settings.spam_daily_digest')%> </span>
      <span>
        <label style=" vertical-align: middle;" class="switch">
          <p> Notification switch </p>
  • 💾 Commit your changes

  • 🔀 Start a Pull Request. There are two ways how you can start a pull request:

  1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

  2. You can also edit files directly in your browser and open a pull request from there.

  • 🏁 Done Ask in comments for a review :)

Please keep us updated

💬⏰ - We encourage contributors to be respectful to the community and provide an update within a week of claiming a first-timers-only issue. We're happy to keep it assigned to you as long as you need if you update us with a request for more time or help, but if we don't see any activity a week after you claim it we may reassign it to give someone else a chance. Thank you in advance!

If this happens to you, don't sweat it! Grab another open issue.

Is someone else already working on this?

🔗- We encourage contributors to link to the original issue in their pull request so all users can easily see if someone's already started on it.

👥- If someone seems stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

🤔❓ Questions?

Leave a comment below!

@Manasa2850 Manasa2850 added first-timers-only They need to be well-formatted using the First-timers_Issue_Template. gsoc outreachy labels Mar 12, 2021
@abhishek-geek
Copy link

Hey @Manasa2850
I would like to work on this issue
Thanks.

@adedejisalim
Copy link
Contributor

Worked on the issue already, Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
first-timers-only They need to be well-formatted using the First-timers_Issue_Template. gsoc outreachy
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants