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

Improved 2.6 release tour #39

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

comradekingu
Copy link
Contributor

No description provided.

@jralls
Copy link
Member

jralls commented Jan 1, 2021

A bit pointless to update this, 2.6 was 6 years ago. We don't even use jpPlot anymore.

@comradekingu
Copy link
Contributor Author

@jralls it is less pointless than arguing not to :)
There are a few strings mentioned in here, and it is much easier to have consistency and no errors when trying to fix things. The 2.6 tour is offered up first for translation in the website component, which I am trying to do something about.

@jralls
Copy link
Member

jralls commented Jan 1, 2021

@comradekingu The alternative to fixing up the strings is to disable them for translation. Since the page is only kept around to avoid broken links in the old announcements (which aren't translated) ISTM that would make more sense than making all the translators work on new ones.

@fellen
Copy link
Member

fellen commented Jan 1, 2021

I have set priority by location now, see https://wiki.gnucash.org/wiki/Weblate#Setup

@comradekingu
Copy link
Contributor Author

@fellen Nice, how did you do that?
@jralls The legacy strings are featured last now, so that is fine.

@fellen
Copy link
Member

fellen commented Jan 1, 2021

@fellen Nice, how did you do that?

#bulk-edit search: location:index, add flag: priority:101 …

@jralls
Copy link
Member

jralls commented Jan 1, 2021

@fellen, low translation priority is good but removing the translation marking would be better.

@fellen
Copy link
Member

fellen commented Jan 1, 2021

@fellen, low translation priority is good but removing the translation marking would be better.

After the Russian docs you want to destroy the work of CWehli, Marco … of the last days?

@jralls
Copy link
Member

jralls commented Jan 1, 2021

After the Russian docs you want to destroy the work of CWehli, Marco … of the last days?

Sunk cost. I want to save Avi the trouble of translating it into Hebrew, and future unknown translators into their languages.

@comradekingu
Copy link
Contributor Author

comradekingu commented Jan 1, 2021

Is it hard to relegate older strings to a "defunct/bonus" Weblate component?
As a sidenote, I think it would be elegant if strings with negative priority were given their own colour in the bar, and not count towards the totals.

@fellen
Copy link
Member

fellen commented Jan 1, 2021

Most recent work on he was done by Yaron. We have to think different here. Almost every active translator found a compagnion here.

I think at least parts of the 2.6-Features should be joined with the (2.0-) Features page before dissolving.

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

Successfully merging this pull request may close these issues.

3 participants