From: "Jan Kundrát" <jkt@gentoo.org>
To: gentoo-doc@lists.gentoo.org
Subject: Re: [gentoo-doc] [RFC] Marking unmaintained documents
Date: Fri, 09 Sep 2005 15:08:04 +0200 [thread overview]
Message-ID: <43218934.6050406@gentoo.org> (raw)
In-Reply-To: <20050909041321.3e93f7eb@pingviinilohhari>
[-- Attachment #1: Type: text/plain, Size: 1922 bytes --]
Flammie Pirinen wrote:
> I really think that these could be done with static note inserted in
> the code, because whatever program logic you could be thinking for
> them it will always be multiple order more complex than needed. If you
> want something easily automagically translatable you could introduce
> something like <thirdparty/> and <obsolete/> empty (replaced) elements
> in style of <license/>, no?
Seems reasonable. And I vote for that extra tag and not yet another
<warn>...</warn>.
>>c) Translation in language which is not officially supported
>
>
> I wouldn't do anything with this, unless it intersects with d). I mean,
> why would we need to tell our users that otherwise up-to-date document
> should not be trusted to, just because the related translation team is
> not organized with proper bureaucratic structure.
Well, current practice is that neysx commits every translation if it
seems to be ok from the XML point of view, but I'm not sure if it is a
good think to say that such docs are "official" - purely technically,
they were contributed by non-Gentoo person and we have no guarantee that
they are correct.
Just my 2 cents, of course - I'm not aware of any troubles caused by
this approach, so maybe I'm just too paranoic :-).
>>d) Outdated translation
>
>
> This is one really required improvement of this proposal, but it
> relates to bigger part of desperately needed accessibility improvements
> in whole translation system anyways.
[...]
I asked for the same while ago and was told that it is "not possible" or
at least "not so easy". BTW, see GLEP 10 [1].
[...]
> After these basics are in order, we might want to start looking in to
> peeking original versions of document to see how up to date it is.
[...]
This raises a problem about "what is outdated"?
Cheers,
-jkt
[1] - http://www.gentoo.org/proj/en/glep/glep-0010.html
--
cd /local/pub && more beer > /dev/mouth
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-09-09 13:08 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 16:56 [gentoo-doc] [RFC] Marking unmaintained documents Jan Kundrát
2005-09-08 17:07 ` Xavier Neys
2005-09-08 17:36 ` Jan Kundrát
2005-09-08 17:54 ` Xavier Neys
2005-09-08 18:12 ` Jan Kundrát
2005-09-08 19:04 ` Shyam Mani
2005-09-09 17:00 ` Sven Vermeulen
2005-09-09 16:57 ` Sven Vermeulen
2005-09-10 13:10 ` Jan Kundrát
2005-09-10 18:22 ` Sven Vermeulen
2005-09-10 20:26 ` Jan Kundrát
2005-09-14 16:55 ` Sven Vermeulen
2005-09-14 18:20 ` Jan Kundrát
2005-09-08 21:00 ` Alexey Chumakov
2005-09-08 21:10 ` Jan Kundrát
2005-09-08 21:11 ` Łukasz Damentko
2005-09-09 1:13 ` Flammie Pirinen
2005-09-09 6:50 ` Alexey Chumakov
2005-09-09 13:10 ` Jan Kundrát
2005-09-09 13:08 ` Jan Kundrát [this message]
2005-09-09 15:49 ` Flammie Pirinen
2005-09-09 16:26 ` Łukasz Damentko
2005-09-10 13:11 ` Jan Kundrát
2005-09-09 16:50 ` Sven Vermeulen
2005-09-10 12:35 ` Jan Kundrát
2005-09-15 11:51 ` Xavier Neys
2005-09-15 11:55 ` [gentoo-doc] " Xavier Neys
2005-09-16 13:01 ` Jan Kundrát
2005-09-17 12:06 ` Sven Vermeulen
2005-09-19 7:51 ` Alexey Chumakov
2005-09-16 9:01 ` [gentoo-doc] " Xavier Neys
2005-09-16 13:07 ` Jan Kundrát
2005-09-16 15:24 ` Xavier Neys
2005-09-16 18:51 ` Jan Kundrát
2005-09-29 15:41 ` Xavier Neys
1980-01-03 20:09 ` Alexey Chumakov
2005-09-29 16:49 ` Jose Luis Rivero
2005-09-29 22:57 ` Łukasz Damentko
2005-09-30 7:20 ` Shyam Mani
2005-09-30 8:59 ` Flammie Pirinen
2005-09-30 16:29 ` Sven Vermeulen
2005-10-02 13:11 ` Jan Kundrát
2005-10-09 10:21 ` Xavier Neys
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43218934.6050406@gentoo.org \
--to=jkt@gentoo.org \
--cc=gentoo-doc@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox