Opened 8 years ago

Closed 8 years ago

Last modified 3 years ago

#4082 closed defect (fixed)

Consider removing website content translations

Reported by: phobos Owned by: runa
Priority: Medium Milestone:
Component: Community/Translations Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I propose scrapping translation of the web pages on our site. We can create user manuals for translation. We can continue to translate tor, vidalia, aurora/firefox, our manual pages, and other documentation included with the various bundles.

Justifications for this proposal are:

  1. We spend a lot of time managing the translated pages on the website.
  2. The English pages are frequently updated, thereby invalidating all of the other languages.
  3. The switch to transifex hasn't made more translators appear, especially for the languages we may care about the most.
  4. The translators for many languages that have a right-to-left orientation complain that the transifex interface is a nightmare to use and refuse to update.
  5. Lots of users simply use google translate, or read English anyway.
  6. getting translated software into the hands of people is more important than them reading our web pages (especially if the documentation is translated and available locally)
  7. at last parse of the webserver logs, our translated website traffic is less than 2% of total GET requests, nevermind page views.

Child Tickets

Change History (3)

comment:1 Changed 8 years ago by runa

+1. I'll wait a few days for people to comment and scream "no" if they actually want to keep website translations.

comment:2 Changed 8 years ago by runa

Resolution: fixed
Status: newclosed

Pulled translations from Transifex for the last time in r25128. Removed the website resources from Transifex. Updated Makefile.common to only build English pages in r25129, deleted translated wml files in r25130.

comment:3 Changed 3 years ago by isabela

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