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

Context menu text in Spanish is too long, #11999

Closed
crar01 opened this issue Dec 20, 2021 · 3 comments
Closed

Context menu text in Spanish is too long, #11999

crar01 opened this issue Dec 20, 2021 · 3 comments
Labels
Area-Localization Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release.

Comments

@crar01
Copy link

crar01 commented Dec 20, 2021

Into folders, the context menu text in Spanish is too long,
is "Abrir en Terminal de Windows en vista previa", perhaps it could be shorter,
something like: "Abrir en Terminal de Windows" or other shorter text.

As the text is very long, it increases the size of the context menu horribly.

@crar01 crar01 added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Dec 20, 2021
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Dec 20, 2021
@zadjii-msft
Copy link
Member

Presumably the "en vista previa" bit is to indicate that you've got the Preview version of the Terminal installed, vs the stable version. I'd assume that the Release version is already "Abrir en Terminal de Windows". I'm open to suggestions here, but we'd need an idea for some string that's different than the one already being used by the stable version 😄

@zadjii-msft zadjii-msft added Area-Localization Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Jan 3, 2022
@ghost ghost added the No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. label Jan 7, 2022
@ghost
Copy link

ghost commented Jan 7, 2022

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@DHowett
Copy link
Member

DHowett commented Jan 7, 2022

This was fixed by #12090 :) (we shortened it, and it's getting re-localized!)

@ghost ghost removed the No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. label Jan 7, 2022
@DHowett DHowett closed this as completed Jan 7, 2022
@DHowett DHowett added the Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release. label Jan 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Localization Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Fix-Committed Fix is checked in, but it might be 3-4 weeks until a release.
Projects
None yet
Development

No branches or pull requests

3 participants