[Sugar-devel] [SoaS] Etoys translations (was: Etoys in RC4 SoaS-v7 does not start when jabber is connected.)

[Bert Freudenberg]

On 28.05.2012, at 20:29, Peter Robinson wrote:

> On Mon, May 28, 2012 at 7:15 PM, Bert Freudenberg <bert at freudenbergs.de> wrote:
>> On 28.05.2012, at 19:54, Peter Robinson wrote:
>> 
>>> symlinks don't work with the Fedora packaging language tools, I prefer
>>> that as it's what the rest of the sugar stack works with.
>> 
>> The way I imagine it is that the .mo files would be installed in /usr/share/locale as all the other packages do, too.
>> 
>> The only question is how to let Etoys know where to go look for its locale files. A symlink created by the installation script would be the simplest solution IMHO. Otherwise we would have to try to pass the directory as argument to etoys in its launcher script which to me seems overly complicated.
>> 
>>>> If we prefix all Etoys .mo files then they could be installed to the system folder.
>>> 
>>> If you use the usual flags as used by all packages for Linux distros
>>> it means you're standard and it will work with all the various linux
>>> distro options.
>>> 
>>> Peter
>> 
>> Not sure what you mean by flags. What I mean by prefixes is this:
>> 
>> Currently Etoys uses mo files named e.g. Collections.mo, Compression.mo, Connectors.mo, etc. This works fine because Etoys had the whole LC_MESSAGES directory for itself. I would propose to rename them to Etoys-Collections.mo, Etoys-Compression.mo, Etoys-Connectors.mo, etc. because if we share the same directory with other packages it would be hard to identify which mo files belong to Etoys.
> 
> As mentioned previously look at the other Activities, like TurtleArt,
> it works like the rest of the distro translation stuff, I'm not sure
> if there's other sugar bits that assist with that.


Other activities have only a single mo file. Other activities use the gettext library so they do not have to worry about where the files are.

Etoys has multiple mo files. Etoys does not use gettext, so it needs to know where to find the translation files.

It's precisely about those differences I'm asking you for clarification. See my previous message.

Until now, Etoys just did its own thing, and that worked fine. But there must be a good reason why you want the mo files in the system default directory. (What is that reason, btw?) So I'm trying to find a way to make it happen. If I know what the constraints are, we surely can find a way to make it fit.

- Bert -