From: Alexey Chumakov <achumakov@gmail.com>
To: gentoo-doc@lists.gentoo.org
Subject: Re: [gentoo-doc] [RFC] Marking unmaintained documents
Date: Fri, 09 Sep 2005 10:50:58 +0400 [thread overview]
Message-ID: <432130D2.5010806@gmail.com> (raw)
In-Reply-To: <20050909041321.3e93f7eb@pingviinilohhari>
Flammie Pirinen пишет:
> 2005-09-08, Jan Kundrát sanoi, jotta:
>>d) Outdated translation
[...]
> 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. By
> the way, why can't this be done same way as in overview.xml? Because
> AFAICS metadoc.xml in Finnish, for example, has only link to either
> English or Finnish version, so the xslt must use some logic to fetch
> english versions here, no? And if the logic is to pull the stuff from
> English metadoc by matching id, shouldn't we then just resolve this by
> adding a matching id to the root elements of the documents, which is
> something that from semantic pov should've been done from beginning on
> already. Of course this'd add overhead of loading (document()ing?) the
> metadoc for all pageloads...
>
Using the link in the document itself ls like any decentralized way:
+ efficiency -- no need to parse metadoc for each page
+ reliability -- no broken links on metadoc failure
+ flexibility -- works with non-metadoc project docs
- human factor -- document maintainer is responsible for the link
- need to update path in several places if source moves
To deal with '-', we need to:
maintain personal responsibility for maintainers (actually
self-maintained in our case, isn't it?)
simply accept the need to update path -- it's already there :-)
Using metadoc, the pros are:
+ clearness for the lead translator (...or actually not?)
+ simplicity of batch update (isn't often?
Cons are the opposite.
Are we centralized or not? :-)
Wkr,
Alexey
--
gentoo-doc@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-09 6:50 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 [this message]
2005-09-09 13:10 ` Jan Kundrát
2005-09-09 13:08 ` Jan Kundrát
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=432130D2.5010806@gmail.com \
--to=achumakov@gmail.com \
--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