Opened 8 years ago

Closed 8 years ago

Last modified 3 years ago

#3796 closed task (fixed)

Remove torbutton, rename torbutton-alpha to torbutton

Reported by: mikeperry Owned by: Runa
Priority: Medium Milestone:
Component: Community/Translations Version:
Severity: Keywords: MikePerryIteration20110925
Cc: Actual Points: 0
Parent ID: Points: 0
Reviewer: Sponsor:

Description

Torbutton 1.4.0 is now the new stable torbutton. There is no alpha currently.

Torbutton 1.4.0's translations exist in the torbutton-alpha repository on transifex. We probably should archive what is in torbutton somehow, and then rename what is in torbutton-alpha to torbutton, so our translators are more aware of what needs translation for the current stable release.

Child Tickets

Change History (11)

comment:1 in reply to:  description Changed 8 years ago by runa

Replying to mikeperry:

Torbutton 1.4.0 is now the new stable torbutton. There is no alpha currently.

Torbutton 1.4.0's translations exist in the torbutton-alpha repository on transifex. We probably should archive what is in torbutton somehow, and then rename what is in torbutton-alpha to torbutton, so our translators are more aware of what needs translation for the current stable release.

Please pull all translations (using tx pull -f -a for both torbutton and torbutton-alpha). After that, rename your torbutton directory to torbutton.old or something similar, and rename torbutton-alpha to torbutton. You will also want to edit the .tx/config file to say torbutton, not torbutton-alpha.

Once that's done, let me know and I can rename the resources on Transifex.

comment:2 Changed 8 years ago by mikeperry

Do we know if there is a merging step I can perform to somehow merge all translated strings that are the same between the two releases? In case someone translated something in the stable but not alpha?

Or does transifex do this already on the fly?

comment:3 in reply to:  2 Changed 8 years ago by runa

Replying to mikeperry:

Do we know if there is a merging step I can perform to somehow merge all translated strings that are the same between the two releases? In case someone translated something in the stable but not alpha?

Or does transifex do this already on the fly?

Hm, no, not that I know of. I believe rransom suggested msgmerge on irc, but I don't know how well (if at all) it'll work. The translations for -alpha aren't too far behind the translations for stable, so it might be better to just remove, rename and be done with it. Thoughts?

comment:4 Changed 8 years ago by mikeperry

Keywords: MikePerryIterationFires20110911 added

Ok. I will update svn when I do the tx client dance. I will let you know when it's done.

comment:5 Changed 8 years ago by mikeperry

I think I did this right. Is there any way to tell? :)

comment:6 in reply to:  5 ; Changed 8 years ago by runa

Replying to mikeperry:

I think I did this right. Is there any way to tell? :)

The commit logs look OK, and I have renamed the two -alpha resources on Transifex.

The old Torbutton resources had translation priority 1 (meaning they were at the top of the list here: https://www.transifex.net/projects/p/torproject/), but the new ones have translation priority 3. Do you want to change that?

comment:7 in reply to:  6 ; Changed 8 years ago by mikeperry

Replying to runa:

Replying to mikeperry:

I think I did this right. Is there any way to tell? :)

The commit logs look OK, and I have renamed the two -alpha resources on Transifex.

The old Torbutton resources had translation priority 1 (meaning they were at the top of the list here: https://www.transifex.net/projects/p/torproject/), but the new ones have translation priority 3. Do you want to change that?

Good question. Can we manage to tell our translators about #3100 through the transifex interface somehow?

If not, leave it at lower priority. No reason to make them do work we just end up undoing.

comment:8 Changed 8 years ago by mikeperry

Keywords: MikePerryIteration20110925 added; MikePerryIterationFires20110911 removed
Points: 0

comment:9 in reply to:  7 Changed 8 years ago by runa

Resolution: fixed
Status: newclosed

Replying to mikeperry:

Replying to runa:

Replying to mikeperry:

I think I did this right. Is there any way to tell? :)

The commit logs look OK, and I have renamed the two -alpha resources on Transifex.

The old Torbutton resources had translation priority 1 (meaning they were at the top of the list here: https://www.transifex.net/projects/p/torproject/), but the new ones have translation priority 3. Do you want to change that?

Good question. Can we manage to tell our translators about #3100 through the transifex interface somehow?

No.

If not, leave it at lower priority. No reason to make them do work we just end up undoing.

Ok.

comment:10 Changed 8 years ago by mikeperry

Actual Points: 0

comment:11 Changed 3 years ago by isabela

Component: User Experience/TranslationsCommunity/Translations
Note: See TracTickets for help on using tickets.