Hi,
On Tue, Jan 22, 2002 at 08:54:26AM +0100, mh wrote:
> It wasn't my intention to complain about your work. If that's the solution,
> it's okay. On the other hand, sane-frontend.html lists more than a dozen
> frontends (btw, some are still missing, e.g. Kooka) .
If you (or someone else) prov
Henning Meier-Geinitz, Montag, 21. Januar 2002 18:26:
> Hi,
>
> On Mon, Jan 21, 2002 at 04:06:37PM +0100, mh wrote:
...
> The only thing that may change is the way the files are generated and
> installed (because of the Makefile incompatibilities mentioned on
> sane-devel elsewhere). But this will
Hi,
On Mon, Jan 21, 2002 at 04:06:37PM +0100, mh wrote:
> But that wasn't my problem. I just like to know, whether the translation
> framework will stay the way it is, i.e. one translation file for every
> backend/language, or whether I should expect changes.
I don't intend to change anything c
Oliver Rauch, Montag, 21. Januar 2002 14:12:
> mh wrote:
> > Hi,
> > just a short question:
> > As far as I can see, the backend translation is merged with the saneopts
> > translation. Since this isn't necessary (a frontend could load two
> > translations, i.e. sane-.mo and sane-opts.mo), I'd lik
mh wrote:
>
> Hi,
> just a short question:
> As far as I can see, the backend translation is merged with the saneopts
> translation. Since this isn't necessary (a frontend could load two
> translations, i.e. sane-.mo and sane-opts.mo), I'd like to know,
> whether there are any plans to change thi
Hi,
just a short question:
As far as I can see, the backend translation is merged with the saneopts
translation. Since this isn't necessary (a frontend could load two
translations, i.e. sane-.mo and sane-opts.mo), I'd like to know,
whether there are any plans to change this. Or will it stay the
