[Padre-dev] rev 879 - menu text change, translation issues

[Heiko Jansen]

> -----Ursprüngliche Nachricht-----
> Von: "Adam Kennedy" <adamkennedybackup at gmail.com>
> Gesendet: 11.11.08 12:16:22
> An: "Padre development discussion list" <padre-dev at perlide.org>
> Betreff: Re: [Padre-dev] rev 879 - menu text change, translation issues


> I should note this doesn't reflect on Window *users*, just on Win32
> *developers*.
> 
> The problem is that we really should be seeing every user as a
> potential developer, and it should be trivial to "upgrade" from one to
> the other.
> 
> Adam K
> 
> 2008/11/11 Gabor Szabo <szabgab at gmail.com>:
> > On Tue, Nov 11, 2008 at 12:50 PM, Heiko Jansen <heiko_jansen at web.de> wrote:
> >> As far as I understand it, the gettext function used now comes with Wx.
> >> So switching to Locale::Maketext would add another dependency, wouldn't it?
> >> If that's the case we should probably wait and see if we run into any shortcomings of the current solution before deciding about abandoning it.
> >
> > The only shortcomings I saw so far is that we have to generate the .mo files.
> > I don't want to add them to version control but then every developer
> > needs to generate those files
> > and Adam does not have it on Windows.
> >
> > I wonder if we could use the .po files directly and what is the price if any?

I don't think that'd be possible.
However, since it's Wx that handles the messages it should indeed be possible to distribute the generated .mo files and while it is perhaps not a completely clean solution I don't see a major problem with adding them to the repository?!
Regarding editing / generating these files: www.poedit.net seems helpful here (not for maketext).
Regarding ease of use: The gettext()-way is what you find if you look for i18n solutions with Wx so other people already familiar with Wx might find it easier to grasp this way round. 
Same is of course true in the opposite direction if somebody already familiar with Locale::Maketext gets involved.

In the end I don't really mind which tool is used. I simply chose the current solution because that's what I found when reading up on the i18n/l10n topic with wxWidgets. I don't know if Locale::Maketext will fit in as easily but if it does and also eases other peoples pain: use it.

Heiko

_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066