Translate the Chrome port of HTTPS-E

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.

added component::https everywhere/eff-https everywhere owner::zyan parent::5274 priority::immediate severity::normal status::assigned type::task labels

Trac:
Parent: N/A to #5274 (moved)

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

Trac:
Priority: major to blocker

This should be a nice easy task.

https://code.google.com/chrome/extensions/i18n.html

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:

0. Make sure the English messges.json file has canonical contents (Micah is working on this now)
1. Make sure that Transifex supports messages.json formatted files (it seems not to so we may have to add it
2. 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.

Trac:
Cc: N/A to micahlee, runa

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.

Trac:
Summary: Translate the Chrome port to Translate the Chrome port of HTTPS-E

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.

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?

Trac:
Cc: micahlee, runa to micahlee

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

Trac:
Username: mikkoharhanen

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?

Trac:
Status: new to assigned
Owner: pde to zyan
Cc: micahlee to micahlee, pde@eff.org

Set all tickets without a severity to "Normal"

Trac:
Severity: N/A to Normal

moved to tpo/applications/https-everywhere-eff#5257 (closed)