On Tue, 11 Sep 2001, Martin Quinson wrote:
On Tue, Sep 04, 2001 at 05:51:38PM -0500, Steve Langasek wrote:
Only if the implementation is poor. The accuracy of a translation can be
verified in the process of assembling the file that is to be made available
to
user machines (whether
On Tue, Sep 11, 2001 at 12:05:25PM -0500, Steve Langasek wrote:
On Tue, 11 Sep 2001, Martin Quinson wrote:
On Tue, Sep 04, 2001 at 05:51:38PM -0500, Steve Langasek wrote:
- an output mecanism, including the fallback to original if the translation
is outdated. You have either to rewrite
Hi Michael,
On Thu, 13 Sep 2001, Michael Bramer wrote:
The end-user tools would never have to deal with outdated translations if
the
.mo file is assembled ahead of time in a central location. Match up the
translations, insert them into the distilled .po file using the package
On Thu, Sep 13, 2001 at 01:26:07PM -0500, Steve Langasek wrote:
On Thu, 13 Sep 2001, Michael Bramer wrote:
The end-user tools would never have to deal with outdated translations if
the
.mo file is assembled ahead of time in a central location. Match up the
translations, insert them
On Tue, Sep 04, 2001 at 05:51:38PM -0500, Steve Langasek wrote:
On Tue, 4 Sep 2001, Michael Bramer wrote:
On Tue, Sep 04, 2001 at 02:24:41PM -0500, Steve Langasek wrote:
I don't know enough about gettext - am I assuming correctly that in
the .mo file, the English translation is
Nick Phillips [EMAIL PROTECTED] immo vero scripsit
What is the size of all this? Ok. we have now in sid/main/i386 (see
[2]) 7000 Packages and the descriptions of all this packages is
2660993 bytes big. We get a description size per package of 384 bytes.
With gzip we will get
Hello all
After I read some more mails and write some comments myself, IMHO it
is time to write a newer hopefully better proposal. Not all is new.
But I add some new thoughs and some parts from some comments.
In this proposal I have combined the decentralized translations, and
also the central
On Tue, 4 Sep 2001, Michael Bramer wrote:
After I read some more mails and write some comments myself, IMHO it
is time to write a newer hopefully better proposal. Not all is new.
But I add some new thoughs and some parts from some comments.
We can reduce the download size by 50% by letting
On Tue, Sep 04, 2001 at 02:52:40PM +0200, Simon Richter wrote:
On Tue, 4 Sep 2001, Michael Bramer wrote:
After I read some more mails and write some comments myself, IMHO it
is time to write a newer hopefully better proposal. Not all is new.
But I add some new thoughs and some parts from
Sorry to screw up the threading; thought I'd posted this already, then
deleted grisu's message before finding that I hadn't sent this :(
On Tue, Sep 04, 2001 at 01:22:16PM +0200, Michael Bramer wrote:
Not all parts are turned into stone. I need some comments and decision
on some parts. Maybe
#include hallo.h
Nick Phillips wrote on Tue Sep 04, 2001 um 03:30:08PM:
So you probably don't usually want the translations to be part of the
package sources or binaries. They're logically separate, and should usually
be physically separate (as physically as we ever get in this sense).
...
So,
On Tue, 4 Sep 2001, Martin Quinson wrote:
On Tue, Sep 04, 2001 at 02:52:40PM +0200, Simon Richter wrote:
On Tue, 4 Sep 2001, Michael Bramer wrote:
After I read some more mails and write some comments myself, IMHO it
is time to write a newer hopefully better proposal. Not all is new.
Hi Michael,
all in all, I think this sounds nice!
On Tue, Sep 04, 2001 at 01:22:16PM +0200, Michael Bramer wrote:
1.) use all the time _gettext_!
I agree, otherwise we'd just have to keep re-inventing the wheel.
2.) get the .po/.mo files on the system
[snip]
If we don't like this process
On Tue, Sep 04, 2001 at 07:59:47PM +0200, Richard Atterer wrote:
2.) get the .po/.mo files on the system
[snip]
If we don't like this process on the client all the time, we can
produce Descriptions-XX.po files and the clinet must only
download this file and save this in the
Hello Richard,
On Tue, 4 Sep 2001, Richard Atterer wrote:
On Tue, Sep 04, 2001 at 01:22:16PM +0200, Michael Bramer wrote:
1.) use all the time _gettext_!
I agree, otherwise we'd just have to keep re-inventing the wheel.
2.) get the .po/.mo files on the system
[snip]
If we don't
yOn Tue, 4 Sep 2001, Steve Langasek wrote:
Hello Richard,
On Tue, 4 Sep 2001, Richard Atterer wrote:
On Tue, Sep 04, 2001 at 01:22:16PM +0200, Michael Bramer wrote:
1.) use all the time _gettext_!
I agree, otherwise we'd just have to keep re-inventing the wheel.
2.) get the
On Tue, Sep 04, 2001 at 02:24:41PM -0500, Steve Langasek wrote:
I think it's very important to have the translations in the *source*
package.
Also agreed.
Why? Each system will usually only require one language per package.
The rest, as far as any particular system is concerned, is just
On Tue, Sep 04, 2001 at 02:24:41PM -0500, Steve Langasek wrote:
I don't know enough about gettext - am I assuming correctly that in
the .mo file, the English translation is replaced with a checksum or
similar, so you do not need to store the complete English translation?
Gettext normally
On Tue, 4 Sep 2001, Michael Bramer wrote:
On Tue, Sep 04, 2001 at 02:24:41PM -0500, Steve Langasek wrote:
I don't know enough about gettext - am I assuming correctly that in
the .mo file, the English translation is replaced with a checksum or
similar, so you do not need to store the
On Tue, Sep 04, 2001 at 08:55:32PM +0200, Michael Bramer wrote:
On Tue, Sep 04, 2001 at 07:59:47PM +0200, Richard Atterer wrote:
2.) get the .po/.mo files on the system
[snip]
If we don't like this process on the client all the time, we can
produce Descriptions-XX.po files and
On Wed, Sep 05, 2001 at 01:40:47AM +0200, Richard Atterer wrote:
On Tue, Sep 04, 2001 at 08:55:32PM +0200, Michael Bramer wrote:
On Tue, Sep 04, 2001 at 07:59:47PM +0200, Richard Atterer wrote:
2.) get the .po/.mo files on the system
[snip]
If we don't like this process on the
On Tue, Sep 04, 2001 at 05:51:38PM -0500, Steve Langasek wrote:
Gettext normally uses the entire untranslated string as the key in the .mo
file. This has many advantages when dealing with translation of strings
in
programs, where the untranslated string is actually present in the
22 matches
Mail list logo
