← Back to team overview

ubuntu-webapps-bugs team mailing list archive

[Bug 1269786] Re: Implement oxide::ContentClient::GetLocalizedString(int message_id)

 

This was implemented with http://bazaar.launchpad.net/~oxide-
developers/oxide/oxide.trunk/revision/481, using chrome’s pak files,
which was deemed good enough for now. We can revisit later if we want to
use gettext to integrate better with ubuntu’s translation tools.

** Changed in: oxide
       Status: In Progress => Fix Released

** Changed in: oxide
     Assignee: Olivier Tilloy (osomon) => Chris Coulson (chrisccoulson)

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1269786

Title:
  Implement oxide::ContentClient::GetLocalizedString(int message_id)

Status in Oxide Webview:
  Fix Released

Bug description:
  Chromium needs to access localized strings for some UI elements (one
  example is the text displayed next to an <input type="file"> widget
  when there are multiple files selected, which is of the form "$1
  files").

  To get those strings, it calls ContentClient::GetLocalizedString(…)
  with a message_id, which by default returns an empty string. We need
  to override this default implementation in oxide to return the actual
  localized string.

  We should avoid using chrome’s pak file format, as those files aren’t
  easily translatable by our existing tools. Using gettext is the
  preferred solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1269786/+subscriptions