Russ Allbery r...@debian.org writes:
After reading the thread, I propose the following reduced version of
this patch. It omits some of the more specific instructions (as
discussed), which can be covered in the devref, and it also avoids the
assumption that the original man page is in
On Fri, Aug 7, 2009 at 13:37:39 -0700, Russ Allbery wrote:
The following wording has received one second and needs an additional
second to be committed to the next revision of Policy. Is everyone happy
with it?
--- a/policy.sgml
+++ b/policy.sgml
@@ -8885,6 +8885,15 @@ name
Julien Cristau jcris...@debian.org writes:
On Fri, Aug 7, 2009 at 13:37:39 -0700, Russ Allbery wrote:
The following wording has received one second and needs an additional
second to be committed to the next revision of Policy. Is everyone happy
with it?
Seconded.
Thanks, committed for
Currently it is not possible to (reliably) decide, whether an
translated man page is up to date or not. In fact quite a few
translations are outdated (missing newer parameters and other
information) or not a translation at all but a rewrite for a previous
version. While this is an upstream
Hello Russ,
On Fri, Jun 19, 2009 at 11:19:50PM -0700, Russ Allbery wrote:
After reading the thread, I propose the following reduced version of
this patch. It omits some of the more specific instructions (as
discussed), which can be covered in the devref, and it also avoids the
assumption that
Manoj Srivastava sriva...@debian.org writes:
This is a new rule being introduced as a SHOULD level, meaning
that any packages that are shipping out-of-date alternate language man
pages are instantly buggy. Are we happy with that?
Personally, I think all such packages are already
clone 493007
reassign -1 developers-reference
retitle -1 suggest to use po4a for man page translations
block -1 by 493007
thanks
Hello Christian,
On Thu, Jul 31, 2008 at 07:37:15AM +0200, Christian Perrier wrote:
Quoting Helge Kreutzmann ([EMAIL PROTECTED]):
+If a loclized man page for a
On Thu, Jul 31, 2008 at 07:37:15AM +0200, Christian Perrier wrote:
Quoting Helge Kreutzmann ([EMAIL PROTECTED]):
+If a loclized man page for a certain command is provided, it should
s/loclized/localized
+either be up to date or it should be clearly visible that this version
+
Quoting Bill Allombert ([EMAIL PROTECTED]):
That latter part probably belongs more to the Developer's
Reference. Indeed, a section about po4a and a simple way to setup a
framework for localized manpages would be a great addition to it.
Frankly, I do not like po4a for manpages. I think we
Quoting Helge Kreutzmann ([EMAIL PROTECTED]):
+If a loclized man page for a certain command is provided, it should
s/loclized/localized
+either be up to date or it should be clearly visible that this version
+is outdated (either by a note in the beginning or by showing the
+
Package: debian-policy
Version: 3.8.0.1
Severity: wishlist
Tags: patch l10n
X-Debbugs-CC: [EMAIL PROTECTED]
Currently it is not possible to (reliably) decide, whether an
translated man page is up to date or not. In fact quite a few
translations are outdated (missing newer parameters and other
11 matches
Mail list logo
