Skip to content

jami-project
jami-project

chatview i18n (design draft)

Last edited by Hugo Lefeuvre
Page history

The GNOME client's chatview lacks proper i18n support.

Related bug report: ring-client-gnome#900

first ideas:

  • i18n functions provided by separate js library
  • i18n not trivial, overhead of custom code extremely high => use existing js lib
  • library will be embedded into the client => code base should be as mature as possible
  • ideally the translation process would be exactly the same as for the C++ code

in short

(1) either

C++ tells JS code which language is currently used and JS code loads translations

(2) or

C++ loads translations and passes them to JS code together with info about currently used language

review exisiting js i18n libs

i18next

The good

  • very mature
  • huge user base
  • lots of documentation
  • No runtime dependencies

The bad

  • huge, overkill ?
  • uses own JSON format not gettext .mo

This will require translation of .po files to JSON format (using i18next-gettext-converter).

The ugly

  • keys do not have the same meaning as gettext keys (see this thread), this might be very confusing for the translators
  • i18next-gettext-converter requires nodeJS as build dependency

jed

The good

  • looks quite mature
  • good user base
  • provides gettext API (will be very intuitive to translators)
  • No runtime dependencies

The bad

  • not very active currently (but it might very well just be stable)
  • uses own JSON format not gettext .mo

This will require translation of .po files to JSON format (e.g. using po2json). po2json also requires nodeJS as dependency, but it is available as Debian package, which makes it slightly less annoying

gettext_end

Source: Internationalization in JavaScript

Polyglot

The good

  • developed by airbnb, well maintained
  • good user base

The bad

  • uses own JSON format not gettext .mo

The ugly

  • runtime dependency on nodeJS

using Jed (WiP)

  • patch draft:

https://gerrit-ring.savoirfairelinux.com/c/ring-client-gnome/+/10615

  • Strings can be retrieved using:
xgettext -o chatview.pot -L Javascript --from-code=utf-8 web/chatview.html
  • Translate strings:
mv chatview.pot en.po
cp en.po fr.po
# translate ...
  • Install po2json:
apt-get install node-po2json
  • Convert .po to JSON:
node-po2json en.po web/i18n/en.json -f jed
node-po2json fr.po web/i18n/fr.json -f jed
  • Make sure JSON files are mentioned in web/web.gresource.xml .
<?xml version="1.0" encoding="UTF-8"?>
<gresources>
    <gresource prefix="/net/jami/JamiGnome">

      <!-- HTML -->
      <file>chatview.html</file>

      <!-- JavaScript -->
      <file>linkify.js</file>
      <file>linkify-string.js</file>
      <file>linkify-html.js</file>
      <file>jed.js</file>

      <!-- CSS -->
      <file>chatview.css</file>

      <file>i18n/en.json</file>
      <file>i18n/fr.json</file>
    </gresource>
</gresources>

That's it. JSON translations are loaded as gresource. The webkitchatcontainer class calls init_i18n(), passing appropriate translation resources.