Could we please have some standardization of file formats and file names
used in translation bug reports? I'm getting text files, gzipped files,
bzip2 files, even links to Web pages. The file names sometimes fail to
include the two-letter language code, requiring me to look it up. This
makes the
On Mon, Sep 06, 2004 at 11:48:24AM -0500, John Hasler wrote:
> Could we please have some standardization of file formats and file names
> used in translation bug reports? I'm getting text files, gzipped files,
> bzip2 files, even links to Web pages. The file names sometimes fail to
> include the
Bartosz Fenski aka fEnIo writes:
> Any propositions?
I'd just like to see consistency.
> What names do you suggest?
Ones that encode the package name, the language code, and the fact that the
file is a .po.
--
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI
On ÎÎÏ 06 ÎÎÏ 2004 20:56, John Hasler wrote:
> Bartosz Fenski aka fEnIo writes:
> > Any propositions?
>
> I'd just like to see consistency.
>
> > What names do you suggest?
>
> Ones that encode the package name, the language code, and the fact
> that the file is a .po.
You need the filename as wel
On Mon, Sep 06, 2004 at 09:28:41PM +0300, Konstantinos Margaritis wrote:
> > > Any propositions?
> >
> > I'd just like to see consistency.
> >
> > > What names do you suggest?
> >
> > Ones that encode the package name, the language code, and the fact
> > that the file is a .po.
>
> You need the fi
Bartosz Fenski aka fEnIo writes:
> Ok and what about compressing? Should be allowed or shouldn't?
It should be required or forbidden, I don't care which. If it is required
you should standardize on one type.
> And the most important part... how to ensure that translators will use
> this conventi
On Mon, Sep 06, 2004 at 02:32:28PM -0500, John Hasler wrote:
> Bartosz Fenski aka fEnIo writes:
> > Ok and what about compressing? Should be allowed or shouldn't?
>
> It should be required or forbidden, I don't care which. If it is required
> you should standardize on one type.
As long as transl
FYI
Regards,
Joey
- Forwarded message from SteX <[EMAIL PROTECTED]> -
Date: Sat, 4 Sep 2004 10:38:22 +0200
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: Debian Translation Party 2
From: SteX <[EMAIL PROTECTED]>
X-Folder: [EMAI
On Mon, Sep 06, 2004 at 02:32:28PM -0500, John Hasler wrote:
> > Ok and what about compressing? Should be allowed or shouldn't?
>
> It should be required or forbidden, I don't care which. If it is required
> you should standardize on one type.
As Denis said. There is no standard for patches in B
Bartosz Fenski aka fEnIo writes:
> There is no standard for patches in BTS.
I thought it might be to the advantage all of us to have some degree of
standardization specifically for translations, which are a special kind of
bug report. This would make it easier for me to process them, and should
a
Konstantinos Margaritis wrote:
> You need the filename as well, as Bartosz said. it's very common to
> find packages with more than one translated po file.
>
> This scheme is quite used throughout d-i:
>
> {package}_{path with s/\//_ }_{lang}.po
>
> so the tasksel files:
>
> po/pl.po
> debian/
11 matches
Mail list logo
