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

Use "audio track(s)" to refer to individual audio works #4037

Merged
merged 13 commits into from
Apr 30, 2024

Conversation

Collins-Webdev
Copy link
Contributor

@Collins-Webdev Collins-Webdev commented Apr 4, 2024

Update References to "Audio Track(s)" in English Text

Description

This pull request addresses issue #3972 by updating references to audio works to use the phrase "audio track(s)" instead of just "audio", following the convention established in issue #3941.

Changes Made

  • Replaced occurrences of "audio" with "audio track(s)" in the English text contained in en.json5.

  • Ensured that the updated references maintain readability and consistency throughout the project.

  • Verified the changes by running the project locally to ensure there are no visible errors.

  • Reviewed and adhered to the established code style of the repository.

  • No changes to tests or documentation were required for this update.

Checklist

  • My pull request has a descriptive title (not a vague title likeUpdate index.md).
  • My pull request targets the default branch of the repository (main) or a parent feature branch.
  • My commit messages follow best practices.
  • My code follows the established code style of the repository.
  • I added or updated tests for the changes I made (if applicable).
  • I added or updated documentation (if applicable).
  • I tried running the project locally and verified that there are no visible errors.
  • I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@Collins-Webdev Collins-Webdev requested a review from a team as a code owner April 4, 2024 18:17
@openverse-bot openverse-bot added the 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work label Apr 4, 2024
@dhruvkb
Copy link
Member

dhruvkb commented Apr 4, 2024

Hi @Collins-Webdev, could you update your PR description to use the pull request template? If you have any questions please let us know in the comments.

I'm labelling the PR as "🧹 status: ticket work required" in the meantime.

@dhruvkb dhruvkb added 🟨 priority: medium Not blocking but should be addressed soon 🛠 goal: fix Bug fix 📄 aspect: text Concerns the textual material in the repository 🧱 stack: frontend Related to the Nuxt frontend 🧹 status: ticket work required Needs more details before it can be worked on and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Apr 4, 2024
Copy link
Member

@dhruvkb dhruvkb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes are good and you've made them in the exact right placc @Collins-Webdev! Thank you for the contributions.

However there are some grammatical issues that I have pointed out in the review. If you could please correct them that would be great. After you have made the text updates, you will need to update the snapshots (see the note about -u in the link) for the frontend tests to pass. Let us know in the comments if you need any help.

For now, I will convert this PR to a draft so that you can make the required changes and once you are done, you can mark is as ready for review, thanks!

@@ -5,7 +5,7 @@
},
hero: {
subtitle: "Explore more than 700 million creative works",
description: "An extensive library of free stock photos, images, and audio, available for free use.",
description: "An extensive library of free stock photos, images, and audio track, available for free use.",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The word "track" was not needed here as we are referring to the entire body of audio works. Please revert.

@@ -80,14 +80,14 @@
},
collection: {
content: {
a: "{openverse} searches across more than 700 million images and audio from open APIs and the {commonCrawl} dataset.",
a: "{openverse} searches across more than 700 million images and audio track from open APIs and the {commonCrawl} dataset.",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We would use the plural form of the word here as we are referring to more than one audio track in this string.

Suggested change
a: "{openverse} searches across more than 700 million images and audio track from open APIs and the {commonCrawl} dataset.",
a: "{openverse} searches across more than 700 million images and audio tracks from open APIs and the {commonCrawl} dataset.",

b: "We aggregate works from multiple public repositories, and facilitate reuse through features like one-click attribution.",
},
},
planning: {
content: {
/** about.planning.content.a-c are parts of a single statement */
a: "Currently {openverse} only searches images and audio, with search for video provided through External Sources.",
a: "Currently {openverse} only searches images and audio track, with search for video provided through External Sources.",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please use the plural form.

Suggested change
a: "Currently {openverse} only searches images and audio track, with search for video provided through External Sources.",
a: "Currently {openverse} only searches images and audio tracks, with search for video provided through External Sources.",

audio: "Audio Sources",
audio: "Audio track Sources",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please revert this change as "track" is not needed here. A source of audio tracks can be called an "audio source".

Comment on lines 625 to 626
count: "See {localeCount} audio track found for {query}.",
countMore: "See over {localeCount} audio track found for {query}.",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please use the plural form.

Suggested change
count: "See {localeCount} audio track found for {query}.",
countMore: "See over {localeCount} audio track found for {query}.",
count: "See {localeCount} audio tracks found for {query}.",
countMore: "See over {localeCount} audio tracks found for {query}.",

Comment on lines 1156 to 1158
zero: "No audio track files provided by this source",
count: "{count} audio track file provided by this source|{count} audio track files provided by this source",
countMore: "Over {count} audio track files provided by this source",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The word "track" and "file" should not both be used as one removes the need for the other.

Suggested change
zero: "No audio track files provided by this source",
count: "{count} audio track file provided by this source|{count} audio track files provided by this source",
countMore: "Over {count} audio track files provided by this source",
zero: "No audio tracks provided by this source",
count: "{count} audio track provided by this source|{count} audio tracks provided by this source",
countMore: "Over {count} audio tracks provided by this source",

Comment on lines 1168 to 1170
zero: "No audio track files with the selected tag",
count: "{count} audio track file with the selected tag|{count} audio track files with the selected tag",
countMore: "Over {count} audio track files with the selected tag",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same note as above^. The use of "track(s)" will eliminate the need for the word "file(s)".

Comment on lines 1144 to 1146
zero: "No audio track files by this creator.",
count: "{count} audio track file by this creator.|{count} audio track files by this creator.",
countMore: "Over {count} audio track files by this creator.",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same note as above^. The use of "track(s)" will eliminate the need for the word "file(s)".

audio: "Audio",
audio: "Audio track",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please revert this change as we are referring to to the collection of all audio tracks so "Audio" is suitable here.

@@ -1000,7 +1000,7 @@
additional: "Coming soon",
statusBeta: "Beta",
seeImage: "See all images",
seeAudio: "See all audio",
seeAudio: "See all audio track",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please use the plural form.

Suggested change
seeAudio: "See all audio track",
seeAudio: "See all audio tracks",

@dhruvkb dhruvkb changed the title Issue #3941 resolved Use "audio track(s)" to refer to individual audio works Apr 4, 2024
@openverse-bot openverse-bot added the 🕹 aspect: interface Concerns end-users' experience with the software label Apr 4, 2024
@dhruvkb dhruvkb marked this pull request as draft April 4, 2024 21:44
@obulat obulat removed the 🧹 status: ticket work required Needs more details before it can be worked on label Apr 5, 2024
@Collins-Webdev Collins-Webdev requested a review from dhruvkb April 5, 2024 16:46
@@ -507,7 +507,7 @@
title: "Source",
},
audioCategories: {
title: "Audio category",
title: "Audio track category",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
title: "Audio track category",
title: "Audio category",

zero: "No audio found for {query}.",
count: "See {localeCount} audio found for {query}.",
countMore: "See over {localeCount} audio found for {query}.",
zero: "No audio track found for {query}.",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
zero: "No audio track found for {query}.",
zero: "No audio tracks found for {query}.",

@@ -1142,7 +1142,7 @@
creator: {
audio: {
zero: "No audio files by this creator.",
count: "{count} audio file by this creator.|{count} audio files by this creator.",
count: "{count} audio track file by this creator.|{count} audio track files by this creator.",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
count: "{count} audio track file by this creator.|{count} audio track files by this creator.",
count: "{count} audio track by this creator.|{count} audio tracks by this creator.",

@@ -1142,7 +1142,7 @@
creator: {
audio: {
zero: "No audio files by this creator.",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
zero: "No audio files by this creator.",
zero: "No audio tracks by this creator.",

@@ -1154,7 +1154,7 @@
source: {
audio: {
zero: "No audio files provided by this source",
count: "{count} audio file provided by this source|{count} audio files provided by this source",
count: "{count} audio file provided by this source|{count} audio track files provided by this source",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
count: "{count} audio file provided by this source|{count} audio track files provided by this source",
count: "{count} audio track provided by this source|{count} audio tracks provided by this source",

@@ -1166,7 +1166,7 @@
tag: {
audio: {
zero: "No audio files with the selected tag",
count: "{count} audio file with the selected tag|{count} audio files with the selected tag",
count: "{count} audio file with the selected tag|{count} audio track files with the selected tag",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
count: "{count} audio file with the selected tag|{count} audio track files with the selected tag",
count: "{count} audio track with the selected tag|{count} audio tracks with the selected tag",

Copy link
Contributor

@obulat obulat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for all your work on this, @Collins-Webdev ! I've added several more suggestions for changes. After adding them, could you mark this PR "Ready for review" so that we can approve and merge it?

@Collins-Webdev
Copy link
Contributor Author

Thank you for all your work on this, @Collins-Webdev ! I've added several more suggestions for changes. After adding them, could you mark this PR "Ready for review" so that we can approve and merge it?

Hello @obulat ,

It's a pleasure for me to be able to participate in such a large-scale project. I have taken your suggestions into account and made the necessary changes. Could you please review them and proceed with merging?
Thanks.

@Collins-Webdev Collins-Webdev requested a review from obulat April 19, 2024 22:53
@Collins-Webdev Collins-Webdev marked this pull request as ready for review April 20, 2024 18:58
@Collins-Webdev Collins-Webdev requested a review from obulat April 20, 2024 18:58
@obulat obulat assigned obulat and Collins-Webdev and unassigned obulat Apr 22, 2024
Copy link
Contributor

@obulat obulat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Collins-Webdev, I added the whitespace changes to fix the linting step of the CI.

Now, the text of the about pages have changed, so we need to update the Visual regression testing snapshots. Here are instructions on how to do it: https://docs.openverse.org/frontend/guides/test.html#updating-snapshots

If you have any problems with this, please comment here - we can help or update for you.

@openverse-bot
Copy link
Collaborator

Based on the medium urgency of this PR, the following reviewers are being gently reminded to review this PR:

@AetherUnbound
@dhruvkb
This reminder is being automatically generated due to the urgency configuration.

Excluding weekend1 days, this PR was ready for review 6 day(s) ago. PRs labelled with medium urgency are expected to be reviewed within 4 weekday(s)2.

@Collins-Webdev, if this PR is not ready for a review, please draft it to prevent reviewers from getting further unnecessary pings.

Footnotes

  1. Specifically, Saturday and Sunday.

  2. For the purpose of these reminders we treat Monday - Friday as weekdays. Please note that the operation that generates these reminders runs at midnight UTC on Monday - Friday. This means that depending on your timezone, you may be pinged outside of the expected range.

Copy link
Contributor

@obulat obulat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I updated the failing snapshots, and the CI now passes.

Thank you for your contribution, @Collins-Webdev 🎉

Copy link
Member

@dhruvkb dhruvkb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the contribution @Collins-Webdev! Also thank you @obulat for making the pending changes.

Collins-Webdev and others added 13 commits April 30, 2024 18:22
Hi there,

I've made some enhancements to the code to address the issue described in WordPress#3941. Following the convention established, I updated references to audio works to use the phrase "audio track(s)" instead of just "audio".

Please review the changes and let me know if there are any further adjustments needed. Thank you for considering my contribution.
Signed-off-by: Olga Bulat <obulat@gmail.com>
Signed-off-by: Olga Bulat <obulat@gmail.com>
@obulat obulat merged commit d181f40 into WordPress:main Apr 30, 2024
40 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🕹 aspect: interface Concerns end-users' experience with the software 📄 aspect: text Concerns the textual material in the repository 🛠 goal: fix Bug fix 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: frontend Related to the Nuxt frontend
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants