Date: Mon, 12 Mar 2001 09:35:52 +0000 From: Nik Clayton <nik@freebsd.org> To: Chris Costello <chris@calldei.com> Cc: Udo Erdelhoff <ue@nathan.ruhr.de>, doc@FreeBSD.ORG Subject: Re: Translators: Need feedback on FAQ reorganization Message-ID: <20010312093551.A3114@canyon.nothing-going-on.org> In-Reply-To: <20010311174633.F31751@holly.calldei.com>; from chris@calldei.com on Sun, Mar 11, 2001 at 05:46:34PM -0600 References: <20010311125040.E31751@holly.calldei.com> <20010312003518.A77178@nathan.ruhr.de> <20010311174633.F31751@holly.calldei.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--W/nzBZO5zC0uMSeA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Mar 11, 2001 at 05:46:34PM -0600, Chris Costello wrote: > > 2) Please do not use the <name>/chapter.sgml structure of the handbook. > > make is perfectly capable of handling more than one source file in a > > directory. We don't need all those additional subdirectories and they > > make it easier to become lost in the sources. Imaging having 5 or 6 > > editor windows (or screens, in my case), all editing "chapter.sgml". >=20 > Anybody else have any opinion on this? Nik? I was following > the Handbook's structure for the sake of continuity. The Handbook has that structure because I envisage more illustrations going in, in per-chapter directories. Also (at some point) we will have the infrastructure to allow people to build the thing at a chapter at a time, which can vastly speed up the editing/reading process. The FAQ does not necessarily have those same constraints -- I don't expect it to be too image heavy, for example. > > Now you can start editing/rewording questions. Group your changes into > > logical blocks, modify only one file at a time, and commit each block > > seperately. >=20 > Sounds good to me. I'm still interested in what everybody > else thinks, too, though. But that sounds pretty logical. That's basically how I converted the Handbook from LinuxDoc to DocBook. > > [0] It might be possible to use the "our" repository (i.e. that of the > > FreeBSD German Documentation Project) for this purpose. I'll talk to > > Alexander Langer (alex@big.endidan.de) about it, it's his box. >=20 > Not a problem. Either a separate branch for the FAQ[0] in the > FreeBSD CVS repo itself, or a separate repository on > usw4.FreeBSD.org (I already have an account) should also do just > nicely. I like the idea of a branch in the FAQ, because then no one has to do anything different to get it -- supfiles will still work, and so on. When the work is finished, and committed to HEAD, it might be possible to= =20 excise this branch from the repo if it's considered bloat. Otherwise we can live with it. 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 --- --W/nzBZO5zC0uMSeA 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 iEYEARECAAYFAjqsmHcACgkQk6gHZCw343WwkwCfQyvGNsE9lAlBifGX2WVLUz6l 5xwAoIosBkhpHO3QPfgsu1lWaH1CO0Xt =ylYa -----END PGP SIGNATURE----- --W/nzBZO5zC0uMSeA-- 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?20010312093551.A3114>