Skip to content
This repository has been archived by the owner on Feb 22, 2023. It is now read-only.

Missing Translation Strings #2159

Closed
bengreeley opened this issue Feb 8, 2023 · 2 comments · Fixed by #2161
Closed

Missing Translation Strings #2159

bengreeley opened this issue Feb 8, 2023 · 2 comments · Fixed by #2161
Assignees
Labels
🕹 aspect: interface Concerns end-users' experience with the software 🛠 goal: fix Bug fix 🟥 priority: critical Must be addressed ASAP
Projects

Comments

@bengreeley
Copy link

bengreeley commented Feb 8, 2023

Description

I noticed there are a couple of strings that aren't translated on the site at https://openverse.org. This may be something that will be taken care of in the future since the new layout just launched, but I wanted to flag it. I tested in German, but other languages also seem to be consistent with these findings.

Reproduction

  1. Go to https://openverse.org, change the language (I selected Deutsch), and a couple of strings on the homepage aren't translated:
  • 'Search for Content' in search field
  • 'All Openverse content is under a Creative Commons license or is in the public domain.' under the search field.
    Screenshot 2023-02-08 at 9 58 04 AM
  1. Search for content and you'll find additional untranslated strings such as https://openverse.org/de/search/?q=test
  • The 'Use' filters aren't translated
  • The 'Creator' filter isn't translated
  • The string 'Not finding what you're looking for? Try an external source:' isn't translated on the bottom of the page.

Screenshot 2023-02-08 at 9 59 21 AM

@bengreeley bengreeley added 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🛠 goal: fix Bug fix labels Feb 8, 2023
@AetherUnbound AetherUnbound added 🟧 priority: high Stalls work on the project or its dependents 🕹 aspect: interface Concerns end-users' experience with the software and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Feb 8, 2023
@AetherUnbound AetherUnbound transferred this issue from WordPress/openverse Feb 8, 2023
@obulat
Copy link
Contributor

obulat commented Feb 9, 2023

I did some investigation about this. The problem is with the translation JSON keys nested more than 2 levels deep.

child.ancestors.push(...this.ancestors, this.key)

Here, the ancestors are only added to the direct children, but the grandchildren's ancestors array stays the same, at max 2-level deep.

@dhruvkb
Copy link
Member

dhruvkb commented Feb 9, 2023

@obulat that makes sense, the ancestors are not populated till later so the array only holds 1 element, the parent.

That would mean that our POJO file has been incorrect 😱 since moving to JSON5. Seems like "🟥 priority: critical" would be appropriate here.

@dhruvkb dhruvkb added 🟥 priority: critical Must be addressed ASAP and removed 🟧 priority: high Stalls work on the project or its dependents labels Feb 9, 2023
@dhruvkb dhruvkb self-assigned this Feb 9, 2023
@openverse-bot openverse-bot moved this from Backlog to In progress in Openverse Feb 9, 2023
Openverse automation moved this from In progress to Done! Feb 9, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🕹 aspect: interface Concerns end-users' experience with the software 🛠 goal: fix Bug fix 🟥 priority: critical Must be addressed ASAP
Projects
No open projects
Openverse
  
Done!
Development

Successfully merging a pull request may close this issue.

4 participants