← Back to team overview

ubuntu-translations-coordinators team mailing list archive

[Bug 1064576] Re: Gmail webapp needs internationalization

 

This seems fixed now:

- Translations are set up in Launchpad for the upstream project and the source package
- Translations are loaded in the commun/utils.js file. There translations coming from PO files are converted from .po to .json, put in the dict variable, and loaded from there. Language detection is done from there by getting the language code from the browser.

However, there's also follow-up bug 1065422

** Changed in: ubuntu-translations
       Status: Triaged => Won't Fix

** Changed in: ubuntu-translations
       Status: Won't Fix => Fix Released

** Changed in: unity-webapps-gmail (Ubuntu)
       Status: Confirmed => Fix Released

** Changed in: webapps-applications (Ubuntu)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1064576

Title:
  Gmail webapp needs internationalization

Status in Ubuntu Translations:
  Fix Released
Status in WebApps: Initial set of Apps:
  Fix Released
Status in “unity-webapps-gmail” package in Ubuntu:
  Fix Released
Status in “webapps-applications” package in Ubuntu:
  Fix Released

Bug description:
  The current webapp for Gmail adds entries in the Launcher and
  Messaging Indicator to compose new messages and to display the Inbox
  count.

  These entries are in English and need to be localizable.

  This means:

  1. Marking the strings for translation in the script (it seems they already are)
  2. Initialize gettext in the code, using the correct translation domain
  3. Getting the build system to extract those strings and put them on a gettext translation template (.pot) file using dh_translations
  4. Add 'X-Ubuntu-Use-Langpack: yes' to debian/control's source record
  5. Get the translations loaded on the desktop at runtime.

  1 to 4 are I believe fairly trivial (although I haven't looked in
  detail at the code and the packaging). For 5. someone on the Desktop
  or Webapps team will probably have to look at how to do this, since
  I'm not very familiar with how the plumbing works in terms of
  integration between desktop and webapp JS scripts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1064576/+subscriptions


References