Implement i18n in all components

Bug #697456 reported by tanktarta on 2011-01-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome15
Wishlist
Unassigned

Bug Description

Gnome15 should be internationalised. This will involve the following areas being given i18n support :-

1. Desktop Lanchers.

This is of course easy enough. Just add the required elements to the .desktop files.

2. "Core" GTK components.

I.e. g15-config. This should *not* include plugin configuration, which should be stored separately (see below). Most, although not all, of the user interface is built using Glade. I presume this has some kind built-in i18n support, this will need to be investigated.

3. "Core" SVG theme files.

I.e. the default theme files for menus and other common components. There may not be anything to do here yet but the framework should be in place for if and when it is required.

There are two ways that come to mind in dealing with the SVG files.

a) Either have *all* text in theme files come from ${variables}, and have the Python side of the plugin populate these with the localised text. This would no additional maintenance of the theme files, but of course means Python changes would be required when adding new text elements.

b) Alternatively, each theme file could exist multiple times, one for each language. However, not all text displayed by plugins is fixed so the Python side would have to use a separate mechanism.

c) Add a new type of pattern that can be used for localisable in the SVG files. Say instead of ${variable}, $[localisable]. These values get replaced with the values in the data files. For any text generated Python side, these are read directly from the data files.

I think option c) is the way to go as it involves the least maintenance of the theme files.

4. "Plugin" GTK components

I.e. plugin "Preferences" glade files. The same mechanisms used for 2 should be used, except the data files should be stored along with the plugin itself (maybe in the "default" theme subdirectory)

5. "Plugin" SVG theme files

I.e. plugin specific theme files. Should be implemented in the same way as 3.

Also ...

6. "man" files. Do these get localised? Gnome15's man files are tiny and not very thorough, but I am not sure what is expected here. Investigate.

7. Other UI components such as the indicator and applet. Some visible text may already be handled by GNOME here, investigate.

tanktarta (tanktarta) on 2011-01-07
Changed in gnome15:
status: New → Confirmed
tanktarta (tanktarta) wrote :

This is mostly done, and will be released in the first 0.8.0 "unstable" build for translators.

The only points from above that need completing are 6 and 7, and well as a final sweep to make sure all strings are translatable. There have been offers of an Italian translation (balta iirc), so that will likely be first.

I also need to work out some kind of procedure for the translators to follow. Whether this will use the Launchpad translation facilities I am not sure yet.

Changed in gnome15:
status: Confirmed → In Progress
milestone: none → 0.8.0
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers