Opened 6 years ago

Last modified 3 years ago

#5257 assigned task

Translate the Chrome port of HTTPS-E

Reported by: pde Owned by: zyan
Priority: Immediate Milestone:
Component: HTTPS Everywhere/EFF-HTTPS Everywhere Version:
Severity: Keywords:
Cc: micahlee, pde@… Actual Points:
Parent ID: #5274 Points:
Reviewer: Sponsor:

Description

The FF and Chrome builds should use the same translation sources.  This probably means we need a script to parse the FF translation .dtds during the chrome build process, and write them out into whatever format Chrome uses for its translations.

Child Tickets

TicketStatusOwnerSummaryComponent
#12018newphoulAdd HTTPS Everywhere for Chrome to TransifexCommunity/Translations

Change History (10)

comment:1 Changed 6 years ago by pde

Parent ID: #5274

comment:2 Changed 5 years ago by pde

Priority: majorblocker

This outstanding task is a major obstacle to doing a big multi-lingual campaign to push for HTTPS Everywhere adoption.  Upgrading.

comment:3 Changed 5 years ago by pde

comment:4 Changed 5 years ago by pde

Cc: micahlee runa added

Micah Lee has taken a first pass at this:

https://gitweb.torproject.org/https-everywhere.git/commitdiff/8c15850d7de6339aacb8c8ac1c1c597aef38cfb4

There are several things we should figure out next:

  1. Make sure the English messges.json file has canonical contents (Micah is working on this now)
  2. Make sure that Transifex supports messages.json formatted files (it seems not to so we may have to add it
  3. Configure Transifex to pull our English messages.json file.

If any of those turn out to be a lot of work, let's make subtickets for them as we realise it.

comment:5 Changed 5 years ago by pde

Summary: Translate the Chrome portTranslate the Chrome port of HTTPS-E

Contrary to what I said in the original ticket, most (but not all) of the strings in the Chrome and Firefox ports are different. Therefore we will not share them unless someone dreams up a crazy way to suck the identical strings in from the Firefox DTD files. I'm skeptical of that.

Runa, does Tor use this Transifex feature? That would save translators work when HTTPS-E Chrome and Firefox strings are similar.

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

Replying to pde:

Runa, does Tor use this Transifex feature? That would save translators work when HTTPS-E Chrome and Firefox strings are similar.

I believe Transifex includes this feature by default, and it's up to the translators to use it.

comment:7 Changed 5 years ago by micahlee

I've removed all the unused strings and renamed them to make more sense for Chrome:

https://github.com/micahflee/https-everywhere/commit/07b04139cfdbfddfe1569254c40e463199badfa3

The Chrome version ends up with only 8 strings. Peter, do you want to merge this into the development repo?

comment:8 Changed 5 years ago by runa

Cc: runa removed

comment:9 Changed 5 years ago by mikkoharhanen

I would like to translate Chrome into Finnish. If I understood correctly, most of the strings in 'messages.json' are not (yet?) in use. Hence there is not much to translate.

If you are interested, you can pull a Finnish translation from:

git://github.com/mikkoharhanen/https-everywhere.git translations

https://github.com/mikkoharhanen/https-everywhere/compare/translations
https://github.com/mikkoharhanen/https-everywhere/compare/translations.patch

comment:10 Changed 3 years ago by pde

Cc: pde@… added
Owner: changed from pde to zyan
Status: newassigned

Transifex has now added Chrome JSON translations, so let's open a separate ticket to add this to Tor's Transifex account.

Yan, do you want to check that the current messages.json has everything we want it to have?

Note: See TracTickets for help on using tickets.