Well, my reasoning was simple: if we drop a language, then the only
solution for users is installing in English, right?
Think of a user who speaks some minority language well and a major
language other than english reasonablly but thier knowlage of english is
very poor/nonexistant.
Such a
Quoting Frans Pop ([EMAIL PROTECTED]):
> Yes, add a comment to indicate the level and then msggrep -C on that
Probably "msggrep -X" would be the key here (I found this after more
than 30 minutes trying to understand msggrep(1) ...).
signature.asc
Description: Digital signature
Quoting Frans Pop ([EMAIL PROTECTED]):
(good convergence of ideas, even if there are points where we probably
still disagree)
> > I like your suggestion of "early warning" for incomplete
> > languages. For now, I can think of it as an hardcoded list in
> > localechooser, for simplicity. We would
On Sunday 04 November 2007, Frans Pop wrote:
> Yes, add a comment to indicate the level and then msggrep -C on that
> comment, first for the lowest level and then for the higher levels. Any
> strings that are left over are sublevel 1.
Hmm. That would not work at all. Needs a bit more thought.
si
On Sunday 04 November 2007, Christian Perrier wrote:
> I like your suggestion of "early warning" for incomplete
> languages. For now, I can think of it as an hardcoded list in
> localechooser, for simplicity. We would then releae localechooser at
> the last minute, with a hardcoded list of language
Quoting Frans Pop ([EMAIL PROTECTED]):
> So the problem here is: what do you do when you're preparing an RC release
> and a translation has slowly drifted downwards (but not below your limits)
> and is missing translations for several key strings.
Just what I always did: nag the translator/tran
On Saturday 03 November 2007, Frans Pop wrote:
> - sublevel 4: specific to less-popular arches (powerpc, mips, sparc?) or
> used in experimental features
s/mips/arm/
signature.asc
Description: This is a digitally signed message part.
On Monday 29 October 2007, Christian Perrier wrote:
> I know we may have many corner cases here and I agree partly on your
> rationale, though I think that we anyway know that modifying the most
> "common" strings is something we don't do without thinking deeply.
At least not shortly before RC rel
(h, I was aiting for your followup, Frans..:-))
Quoting Frans Pop ([EMAIL PROTECTED]):
> On Wednesday 24 October 2007, Christian Perrier wrote:
> > - criterion for downgrading to prospective:
> > - below 98% for sublevel 1
>
> It probably won't surprise you that I have a problem with th
On Wednesday 24 October 2007, Christian Perrier wrote:
> - criterion for downgrading to prospective:
> - below 98% for sublevel 1
It probably won't surprise you that I have a problem with this 98%
criterium. My main argument is of course that having 2% of your strings
untranslated can make
As one may have noticed, no new language has been activated as of now
in D-I since etch.
Indeed, given the tremendous number of languages we support
(http://d-i.alioth.debian.org/doc/i18n/languages.html), it becomes
harder and harder to find and motivate people for the remaining
ones. Most of the
11 matches
Mail list logo