-
Notifications
You must be signed in to change notification settings - Fork 214
chore: clean up translation files #4051
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
base: main
Are you sure you want to change the base?
Conversation
| @@ -0,0 +1,731 @@ | |||
| { | |||
| "api-docs": { | |||
| "en": { | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| "en": { | |
| "ja": { |
This should be changed in all other places too.
|
The image is available at: |
d4b41db to
eb4d452
Compare
|
The image is available at: |
eb4d452 to
d8d8b3c
Compare
|
The image is available at: |
d8d8b3c to
4564786
Compare
|
The image is available at: |
4564786 to
3207784
Compare
|
The image is available at: |
karthikjeeyar
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified the PR changes using the PR image, looks good to me.
I have noticed a place where there is some manual correction needed. PTAL
| "fr": { | ||
| "catalogFilter.title": "Filtres", | ||
| "catalogFilter.buttonTitle": "Filtres", | ||
| "entityKindPicker.title": "Type", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @karthikjeeyar , the "Type" is already a translated word. The thing is in French both "kind" and "type" are "type". I consulted AI regarding translation of
"entityTypePicker.title": "Type",
"entityKindPicker.title": "Kind",
when they are together, AI suggested
"entityTypePicker.title": "Type",
"entityKindPicker.title": "Catégorie"
As in Backstage, Kind and Type have different meanings:
- Kind = entity category (Component, API, Resource, System, Group, User…)
- Type = subtype within a Kind (service, website, library…)
What do you think? If it looks good to you, I will go ahead and update other similar cases to keep everything consistent in French.
- Treat Kind = high-level entity classification: Entity class (Component, API, Resource…)
- Treat Type = subtype / functional type: Subtype (service, website…)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good. Let us use AI suggested translation "Catégorie" to differentiate those headings.
fe9ac37 to
dc78186
Compare
|
/approve |
|
The image is available at: |
dc78186 to
e515b1c
Compare
|
The image is available at: |
e515b1c to
3f6c753
Compare
|
The image is available at: |
3f6c753 to
6b4fc43
Compare
|
The image is available at: |
|
/test e2e-ocp-helm |
ⓘ Your monthly quota for Qodo has expired. Upgrade your plan ⓘ Paying users. Check that your Qodo account is linked with this Git user account |
|
/retest |
1 similar comment
|
/retest |
Signed-off-by: Yi Cai <yicai@redhat.com>
Signed-off-by: Yi Cai <yicai@redhat.com>
Signed-off-by: Yi Cai <yicai@redhat.com>
6b4fc43 to
d37e2d6
Compare
|
The image is available at: |
Signed-off-by: Yi Cai <yicai@redhat.com>
|
|
The image is available at: |
karthikjeeyar
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: karthikjeeyar The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/cherry-pick release-1.9 |
|
@ciiay: once the present PR merges, I will cherry-pick it on top of DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@ciiay @karthikjeeyar Thanks a lot. But can you please remove the date / version inforation from the filenames? This makes it impossible currently to understand the diff (yeah I can use diff locally but I like to understand this on GitHub). Also this would require us to change ts import every time we update the json files. This change also means we're losing translations for all BCP plugins that are not from Red Hat but supports translations, right?! |





Description
Cleaned up translation files with latest it, ja and fr translation for backstage.
Which issue(s) does this PR fix
PR acceptance criteria
Please make sure that the following steps are complete:
How to test changes / Special notes to the reviewer