From: Xavier Neys <neysx@gentoo.org>
To: gentoo-doc@lists.gentoo.org
Subject: Re: [gentoo-doc] [RFC] Marking unmaintained documents
Date: Fri, 16 Sep 2005 17:24:46 +0200 [thread overview]
Message-ID: <432AE3BE.7060105@gentoo.org> (raw)
In-Reply-To: <432AC379.1070801@gentoo.org>
Jan Kundrát wrote:
> Xavier Neys wrote:
>
>>Some doc dev complained that comparing the dates would not work if two
>>updates occurred in the same day. True. Comparing the versions is a bit
>>more complex and involves two extra scans of the handbooks (the original
>>and the translated one). It's fast enough IMO. My <300Mhz test box still
>>delivers handbook chapters under the second. Note that it is still not
>>100% fool-proof. If a chapter disappears from the original, the mention
>>of a more recent original would not appear on the translations because
>>the xsl scans the original and compares the version with the version of
>>the file that is included at the same position (part/chapter-wise) in
>>the translation. That has not happened yet.
>>
>>I'm not going to parse the version strings to try to quantify the amount
>>of changes that occurred because 1) versions are not structured 2) a
>>single bump could mean a small or a big change, and vice-versa for more
>>bumps. Displaying the date of the original should be a good indication.
>
>
> Thanks, I like this idea. Am I correct when I assume that it will check
> both handbook-$ARCH.xml and hb-$foo-$bar.xml when displaying only one
> chapter and all files for current $ARCH when doing ?full=1 ?
Almost.
Full handbook: all files are checked
TOC (part and/or chap = 0), master file is checked
Chapter, hb-$foo-$bar.xml is checked, checking the master files as well would
be trivial, but why should they be checked?
Cheers,
--
/ Xavier Neys
\_ Gentoo Documentation Project
/ French & Internationalisation Lead
\ http://www.gentoo.org/doc/en
/\
--
gentoo-doc@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-16 15:25 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
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 [this message]
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=432AE3BE.7060105@gentoo.org \
--to=neysx@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