I'd personally prefer `licence' when referring to the document(s).
>
> http://dict.leo.org says:
> US: the license, to license
> GB: the licence, to licence
That is definitely incorrect, and I'm surprised at dict.leo.org for
making such a basic mistake.
--
Colin Watson [EMAIL PROTECTED]
fixed or
> removed.
Using this as an example of why outdated translations shouldn't be
removed implies that you think it's a good thing that packages with RC
bugs (sometimes) aren't fixed or removed ...
--
Colin Watson [EMAIL PROTECTED]
r.
I wonder if more time is wasted for the translators who sometimes have
to resurrect content, or for the users who turn up on #debian-boot
having wasted hours of effort because five translations still link to
the broken sarge CD images from fsn.hu ...
(Possibly a bad example since the Englis
there is a problem"; sometimes the problem may not affect
everyone, and people may not have seen it before.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
policy I can't file bugs against them ;)
You can file bugs; they just don't get to be release-critical.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
e ago
>
> I think it would be good idea to use capitalized code names *everywhere*,
> not only in German translation.
The English codenames should be lower-case. Think Unix.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
it still correct
> to use "them"? I'm sorry to bother you with this, it's just that I've never
> seen or heard such sentences.
That sentence doesn't feel at all unusual to me.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
gs to exactly 'moreinfo' and 'unreproducible'
tags 123456 = moreinfo unreproducible
So, 'tags 269115 +patch +upstream' as you tried is a syntax error: you
should use 'tags 269115 + patch upstream' instead.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
> I think your changes improve both pages, but I suggest to remove
> all typos you introduced (in a few lines of code!), this includes
> s/Grossteil/Großteil/
Isn't this simply new orthography versus old orthography?
--
Colin Watson [EMAIL PROTECTED]
ly recent version of
groff?
Also, have you looked at the (very hackish, but surprisingly effective)
way w3mman works?
Cheers,
--
Colin Watson [EMAIL PROTECTED]
ges under /Bugs/ are derivative works of pages originally written
as part of debbugs, and they're still maintained in loose sync (there
are various differences in HTML style) with the pages in debbugs CVS.
It's appropriate for them to have the same copyright notice as debbugs.
--
Colin Wats
it to thread and vice versa
In that case, it seems like a possible compromise might be to keep the
old files in place to avoid breaking links from elsewhere, but no longer
list them from the index?
--
Colin Watson (he/him) [cjwat...@debian.org]
101 - 112 of 112 matches
Mail list logo
