Date: Mon, 12 Mar 2001 23:13:47 +0000 From: Nik Clayton <nik@freebsd.org> To: John Baldwin <jhb@FreeBSD.org> Cc: Nik Clayton <nik@FreeBSD.org>, Chris Costello <chris@calldei.com>, Udo Erdelhoff <ue@nathan.ruhr.de>, doc@FreeBSD.org Subject: Re: Translators: Need feedback on FAQ reorganization Message-ID: <20010312231347.B75170@canyon.nothing-going-on.org> In-Reply-To: <XFMail.010312145156.jhb@FreeBSD.org>; from jhb@FreeBSD.org on Mon, Mar 12, 2001 at 02:51:56PM -0800 References: <20010312213831.A74204@canyon.nothing-going-on.org> <XFMail.010312145156.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--s/l3CgOIzMHHjg/5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Mar 12, 2001 at 02:51:56PM -0800, John Baldwin wrote:
> >> Since the FAQ shouldn't be broken, there's no reason to
> >> not just do this on HEAD. =20
> >=20
> > Not so much broken, but I expect there will be periods where it's very=
=20
> > confusing to readers as the content migrates all over the place.
>=20
> Nah. If the question isn't still in the main faq.sgml, it's in one of the
> chapter.sgml files, and the chapter name should easily help to lcoate it,=
along
> with grep -r if necessary. Heck, you'd have to use some kind of search i=
n the
> editor to get to the point in faq.sgml where the question is anyway. So =
long
> as the same question isn't in two different places (which is easy enough =
to
> achieve) then there should be no problems. Besides, the actual content m=
oving
> should probably only take a week at most. We aren't changing any markup =
or
> anything, just cut 'n' paste here.
I'll leave it up to Chris and the folks doing the work as to whether or
not they think the FAQ will be confusing to readers during the
transition.
> > It was done in the tree. We were able to do the Handbook in the tree
> > because the conversion coincided with moving the Handbook from one
> > directory in the tree to another. I just did all the work in the new
> > directory, and the handbook's old directory wasn't touched until the
> > conversion was over.
>=20
> Err, it wasn't all done in the tree. :) =20
Oh yes it was. ("Oh no it wasn't!" "Oh yes it was!"). I have the RSI to
prove it.
> You had this long itemized list of steps that you took, and those list=20
> of steps aren't present as individual commits in the logs. :)
cvs checkout doc/en/handbook
cd doc/en/handbook
cvs log README
cvs log handbook.sgml
...
> I think the bulk of the work in what Chris has done is in things like mer=
ging
> questions, rewriting, etc. and there's no reason that can't be committed =
in a
> normal fashion once the mostly mechanical operation of splitting up the b=
ig
> sgml file has been done.
Chris?
> It will be just as usable as it will be when the transition is finished. =
If
> people can't grep through the sgml files when it is in transition, how wi=
ll
> they find the questions once it is all split up? =20
I'm not concerned about the authors, it's the people reading the FAQ on
the website that I'm worried about. Is there going to a period of time
during which the FAQ is difficult for them to use? Chris is the person
best placed to answer that.
N
--=20
FreeBSD: The Power to Serve http://www.freebsd.org/
FreeBSD Documentation Project http://www.freebsd.org/docproj/
--- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 ---
--s/l3CgOIzMHHjg/5
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (FreeBSD)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjqtWAkACgkQk6gHZCw343UTKACggi8VbyENE1FjqATerNvzG/Zw
6PIAn0a0i98wZAY07m8TWaGI4wFL26TI
=avNe
-----END PGP SIGNATURE-----
--s/l3CgOIzMHHjg/5--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010312231347.B75170>