Leo \costela\ Antunes writes (Re: Please don't list available translations
in the package description):
While I agree it's an issue (albeit a small one), I think we shouldn't
file bugs for it while there's no better place to put this information.
It may reduce the objectiveness of some
Bah, sorry about the previous mail, sent it before it was finished.
On pe, 2007-12-07 at 15:28 +0100, Thijs Kinkhorst wrote:
On Friday 7 December 2007 11:52, Enrico Zini wrote:
If we want to implement a feature such that we can see what packages are
localised for a given language, that
On pe, 2007-12-07 at 15:28 +0100, Thijs Kinkhorst wrote:
On Friday 7 December 2007 11:52, Enrico Zini wrote:
If we want to implement a feature such that we can see what packages are
localised for a given language, that should be done differently, most
likely by building a database scanning
On Friday 7 December 2007 11:52, Enrico Zini wrote:
If we want to implement a feature such that we can see what packages are
localised for a given language, that should be done differently, most
likely by building a database scanning what .po files are present in the
source package.
Wouldn't
On Sat, Dec 08, 2007 at 11:54:57AM +0200, Lars Wirzenius wrote:
every package is very wasteful of space. Thus, I think it should not be
done. A better way to express the information is needed.
Indeed. If anyone can tell me how comparison among locale strings is
supposed to work, I can try to
On Fri, Dec 07, 2007 at 10:52:08AM +, Enrico Zini wrote:
ldap-account-manager is not the only package doing this: a quick search
gives me [...] gperiodic
I removed that in svn.
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
On Friday 07 December 2007, Leo costela Antunes wrote:
Enrico Zini wrote:
I'm thinking of filing bugs, but I'd like to get some feedback here
first.
While I agree it's an issue (albeit a small one), I think we shouldn't
file bugs for it while there's no better place to put this
On Fri, Dec 07, 2007 at 01:40:43PM +, Stephen Gran wrote:
This one time, at band camp, Leo costela Antunes said:
Enrico Zini wrote:
I'm thinking of filing bugs, but I'd like to get some feedback here
first.
While I agree it's an issue (albeit a small one), I think we shouldn't
cobaco (aka Bart Cornelis) wrote:
Almost no packages currently do this, hence relying on the package
description to check wether a package is localized for your language is
completely unreliable.
Agreed.
For a list of localised packages check http://www.debian.org/intl/l10n/po/
for your
This one time, at band camp, Leo costela Antunes said:
Enrico Zini wrote:
I'm thinking of filing bugs, but I'd like to get some feedback here
first.
While I agree it's an issue (albeit a small one), I think we shouldn't
file bugs for it while there's no better place to put this
Stephen Gran wrote:
At the moment, I'm inclined to agree with Enrico. I don't think it's
all that helpful to have some small subset of all the programs actually
translated into a given language returned in a search for that language
string. It's both an incomplete list (since many other
Enrico Zini wrote:
I'm thinking of filing bugs, but I'd like to get some feedback here
first.
While I agree it's an issue (albeit a small one), I think we shouldn't
file bugs for it while there's no better place to put this information.
It may reduce the objectiveness of some searches, but it
Hello,
I'm reviewing tag submissions and I noticed that people added lots of
culture::* tags to a non culture specific package like
ldap-account-manager. The reason was simple: the description mentions:
LAM is translated to Catalan, Chinese (Simplified + Traditional),
Czech, Dutch, English,
On Fri, Dec 07, 2007 at 03:10:35PM +0100, Francesco P. Lovergine wrote:
On Fri, Dec 07, 2007 at 01:40:43PM +, Stephen Gran wrote:
This one time, at band camp, Leo costela Antunes said:
Enrico Zini wrote:
I'm thinking of filing bugs, but I'd like to get some feedback here
first.
On Fri, Dec 07, 2007 at 02:22:49PM +0100, Leo costela Antunes wrote:
Couldn't debtags support this sort of information in a good enough way
(not via culture::*, but something like translated-in::*)?
Or perhaps - if stricter solution is desired - implementing a new
control field that could be
Quoting Francesco P. Lovergine ([EMAIL PROTECTED]):
I'd also tend to think that generic internationalization support
sentences are quite inappropriate into package long description.
Support leve is generally subject to frequent changes, so why
polluting descriptions with those things?
16 matches
Mail list logo
