Updated Swedish translation

[Regnander]

In this PR, I added new and updated existing properties/HTML files. There are some more HTML files to be translated, which I will take care of in a future PR.

No JIRA ticket. Since the majority of the most recent translation PRs lacked one, I figured this wasn't needed.

Testing done

Testing was done by browsing the various menus and settings to get proper context.

Proposed changelog entries

• Major overhaul of the entire Swedish translation.

Proposed upgrade guidelines

N/A

Submitter checklist

Beta Give feedback

1. The Jira issue, if it exists, is well-described.
2. The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
3. There is automated testing or an explanation as to why this change has no tests.
4. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
5. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
6. New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
7. For dependency updates, there are links to external changelogs and, if possible, full differentials.
8. For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@mention

Before the changes are marked as ready-for-merge:

Maintainer checklist

Beta Give feedback

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
4. Proper changelog labels are set so that the changelog can be generated automatically.
5. If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
6. If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[welcome]

Yay, your first pull request towards Jenkins core was created successfully! Thank you so much!

A contributor will provide feedback soon. Meanwhile, you can join the chats and community forums to connect with other Jenkins users, developers, and maintainers.

[github-actions]

Please take a moment and address the merge conflicts of your pull request. Thanks!

[Regnander]

I have no idea on how to solve the build errors, so any help would be appreciated.

[StefanSpieker]

I think it is complaining about the HTML files.

Code style issues found in 84 files. Run Prettier to fix.

You can build it on your machine and check that you are seeing the same error. You can fix it with prettier. In the ci process you can change the Line 799 in war/pom.xml to lint:fix, which should fix all problems, remember to revert the changes in the pom.xml before committing the changes.

[Regnander]

My local repo is currently broken, so I manually formatted the affected HTML files. However, I still get the same lint error.

[NotMyFault]

My local repo is currently broken, so I manually formatted the affected HTML files. However, I still get the same lint error.

The correct way to fix prettier issues is by running yarn run lint:fix followed by lint:ci to ensure locally, that your PR passes CI checks.

[Regnander]

The correct way to fix prettier issues is by running yarn run lint:fix followed by lint:ci to ensure locally, that your PR passes CI checks.

That fixed the lint errors. Thanks!

However, this time the logs say "hudson.PluginManagerTest.updateSiteURLCheckValidation failed". Is there something I can do about this?

Edit: It seems like it was an external issue,

[github-actions]

Please take a moment and address the merge conflicts of your pull request. Thanks!

[MarkEWaite]

Thanks very much for the pull request.

I resolved the conflict and merged the latest changes from the master branch so that a new CI build would evaluate the pull request again.

I've run the Jenkins controller with locale set to "sv_SE" using the Jenkins locale plugin and was able to see the Swedish translations from my Google Chrome browser. I checked a few of the translations with Google translate and confirmed that Google translate agrees with the translated strings.

I don't speak Swedish, but I believe that @rsandell does. I've approved this pull request based on my testing and my use of google translate to confirm the few strings I checked agreed with Google translate.

[github-actions]

Please take a moment and address the merge conflicts of your pull request. Thanks!

[Regnander]

@MarkEWaite Thanks for merging again. Is there anything I should do once the build is finished?

[MarkEWaite]

@MarkEWaite Thanks for merging again. Is there anything I should do once the build is finished?

No, I think that the preferred next step is a review by another Swedish speaker. If that doesn't happen within a week, I will ask for a review by someone who is not a Swedish speaker so that it can be merged.

[NotMyFault]

Thanks!

---

/label ready-for-merge

---

This PR is now ready for merge. We will merge it after ~24 hours if there is no negative feedback.
Please see the merge process documentation for more information about the merge process.
Thanks!

[welcome]

Congratulations on getting your very first Jenkins core pull request merged 🎉🥳

This is a fantastic achievement, and we're thrilled to have you as part of our community! Thank you for your valuable input, and we look forward to seeing more of your contributions in the future!

We would like to invite you to join the community chats and forums to meet other Jenkins contributors 😊
Don't forget to check out the participation page to learn more about how to contribute to Jenkins.