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

De-listing flag #5510

Closed
comradekingu opened this issue Feb 23, 2021 · 8 comments
Closed

De-listing flag #5510

comradekingu opened this issue Feb 23, 2021 · 8 comments
Labels
wontfix Nobody will work on this.

Comments

@comradekingu
Copy link
Contributor

comradekingu commented Feb 23, 2021

With changelogs piling up and old ones often not included or worthwile to translate, it would be nice to flag them "delist" to remove them from the translation bars and tallies.

Isn't there something like that for read-only already?

I see two not-completed projects and I have to remember whether I translated the recent one, and also know whether a version has been released afterwards.
If it was all full if done and not-full if not done, I could spend more time translating current changelogs.

I thought about "current-changelog", but that is a bit iffy since there might be more versions released, and there are also short-desc and long-desc type strings in the same Fastlane components. Similar for SailfishOS.

@nijel
Copy link
Member

nijel commented Feb 24, 2021

@comradekingu
Copy link
Contributor Author

comradekingu commented Feb 24, 2021

So unless I am as stupid as I thought I was just now, that only describes "read-only"?

I actually want to allow translation, I just don't want those strings to count towards the totals (as if it was read-only). If I translate everything that isn't delisted, I want full bars.

So all of read-only, without the actual read-only.

Bonus for also applying a low priority: to any string that is flagged "delisted".

Other than metadata,

say you want to delete some of your strings. A part of the program got deprecated for example. Now instead of losing the translation memory of it, you can de-list those strings. It helps people look up translations, it helps populate new strings. All that good stuff.

None of the "throw new strings in with the old ones and have everyone translate everything", and especially no "lets have to identical components for two versions and forget to set up linking". Just de-list whatever isn't new, and everyone wins.

And I am somewhat thinking it can help formats that don't support fuzzy strings by just updating the string(?).

@nijel
Copy link
Member

nijel commented Feb 25, 2021

Now it sounds like a duplicate of #1993

@comradekingu
Copy link
Contributor Author

Yes, only now more relevant since changelogs are very ephemeral.
There is no use losing the data, and currently translating the latest one is hard because of old ones being kept as is.

@nijel
Copy link
Member

nijel commented Feb 27, 2021

The strings should be ordered correctly, so the first one to translate should be the latest one.

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had any recent activity.

It will be closed soon if no further action occurs.

Thank you for your contributions!

@github-actions github-actions bot added the wontfix Nobody will work on this. label Mar 10, 2021
@comradekingu
Copy link
Contributor Author

comradekingu commented Mar 18, 2021

Don't see any other way of solving this.
The ordering once opened doesn't signify in the overview whether a component is to be opened or not.

@nijel
Copy link
Member

nijel commented Mar 18, 2021

I don't see other way of solving this than #1993 (besides what is already in place).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix Nobody will work on this.
Projects
None yet
Development

No branches or pull requests

2 participants