1 Mar 2010 21:27
2 Mar 2010 07:30
5 Mar 2010 19:26
Removal of incomplete NetBSD Guide translations
Daniel Sieger <dsieger <at> techfak.uni-bielefeld.de>
2010-03-05 18:26:52 GMT
2010-03-05 18:26:52 GMT
Hello, as you may have noticed, we removed all non-english content from our website some time ago (see [1] for a detailed descriptoin of our reasons). Up until now, some incomplete translations of the NetBSD Guide still have been in our htdocs repository. These translations will be moved to the CVS Attic during the next couple of days. Regards, Daniel Sieger [1]: http://mail-index.nebsd.org/netbsd-docs/2009/12/26/msg000125.html -- -- Daniel Sieger Computer Graphics & Geometry Processing Group Bielefeld University http://graphics.uni-bielefeld.de
6 Mar 2010 22:54
Re: style(9)?
Hubert Feyrer <hubert <at> feyrer.de>
2010-03-06 21:54:02 GMT
2010-03-06 21:54:02 GMT
Am 06.03.2010 um Sa. 06.03.2010 21:26 schrieb Jukka Ruohonen: ISTM that getting the roff formatting to be exactly right is probably >> not worth the (likely substantial) trouble, and then it'd have to be >> maintained too. Maybe a stub page that points to the text file would >> be an adequate compromise? > > Well, I am already in about halfway of the page... > > I haven't experienced major problems with markup (yet). This is probably > because I am trying to "write it out" a little, instead of basically copying > the file like was apparently done in the other BSDs. The content remains the > same, of course. > > It shouldn't be noticeable harder to maintain than a text file. FWIW, > generally manual pages also appear to suffer less from bitrot than random > files. But maybe this is just circular reasoning. In HTML lingo, I'd say wrap it in <pre> and call it good. No idea what you mean by "write it out"... maybe discuss before you do unneccessary work? - Hubert
7 Mar 2010 10:39
Re: style(9)?
Daniel Sieger <dsieger <at> techfak.uni-bielefeld.de>
2010-03-07 09:39:54 GMT
2010-03-07 09:39:54 GMT
On Sat, Mar 06, 2010 at 08:01:48PM +0000, David Holland wrote: > On Tue, Mar 02, 2010 at 08:30:42AM +0200, Jukka Ruohonen wrote: > > All other BSDs have a manual page for KNF. But NetBSD has only > > '/usr/share/misc/style'. Does NetBSD want a style(9)? I am willing to do the > > work. > > ISTM that getting the roff formatting to be exactly right is probably > not worth the (likely substantial) trouble, and then it'd have to be > maintained too. Maybe a stub page that points to the text file would > be an adequate compromise? Personally, I'd prefer to have a style(9) man page at hand. I think the corresponding man pages from FreeBSD and OpenBSD are much more comfortable to read than our current /usr/share/misc/style. So, if Jukka is willing to do the work, I'd be all for it. - Daniel -- -- Daniel Sieger Computer Graphics & Geometry Processing Group Bielefeld University http://graphics.uni-bielefeld.de
7 Mar 2010 05:25
Re: style(9)?
Jukka Ruohonen <jruohonen <at> iki.fi>
2010-03-07 04:25:45 GMT
2010-03-07 04:25:45 GMT
On Sat, Mar 06, 2010 at 10:54:02PM +0100, Hubert Feyrer wrote: In HTML > lingo, I'd say wrap it in <pre> and call it good. No idea what you mean by > "write it out"... maybe discuss before you do unneccessary work? Meaning exactly that I am not wrapping it around <pre>. Meaning that it uses real paragraphs, has a structure and titles, like any document is supposed to do. - Jukka.
6 Mar 2010 21:26
Re: style(9)?
Jukka Ruohonen <jruohonen <at> iki.fi>
2010-03-06 20:26:09 GMT
2010-03-06 20:26:09 GMT
On Sat, Mar 06, 2010 at 08:01:48PM +0000, David Holland wrote: > ISTM that getting the roff formatting to be exactly right is probably > not worth the (likely substantial) trouble, and then it'd have to be > maintained too. Maybe a stub page that points to the text file would > be an adequate compromise? Well, I am already in about halfway of the page... I haven't experienced major problems with markup (yet). This is probably because I am trying to "write it out" a little, instead of basically copying the file like was apparently done in the other BSDs. The content remains the same, of course. It shouldn't be noticeable harder to maintain than a text file. FWIW, generally manual pages also appear to suffer less from bitrot than random files. But maybe this is just circular reasoning
6 Mar 2010 21:01
Re: style(9)?
David Holland <dholland-docs <at> netbsd.org>
2010-03-06 20:01:48 GMT
2010-03-06 20:01:48 GMT
On Tue, Mar 02, 2010 at 08:30:42AM +0200, Jukka Ruohonen wrote: > All other BSDs have a manual page for KNF. But NetBSD has only > '/usr/share/misc/style'. Does NetBSD want a style(9)? I am willing to do the > work. ISTM that getting the roff formatting to be exactly right is probably not worth the (likely substantial) trouble, and then it'd have to be maintained too. Maybe a stub page that points to the text file would be an adequate compromise? -- -- David A. Holland dholland <at> netbsd.org
23 Mar 2010 07:15
mk.conf(5)
Jukka Ruohonen <jruohonen <at> iki.fi>
2010-03-23 06:15:37 GMT
2010-03-23 06:15:37 GMT
Hello. The mk.conf(5) is one of those manual pages that are systematically behind. It is generally a nightmare to maintain and the information is duplicated in bsd.README. Possible solutions: (a) Document the MKx and USEx variables in mk.conf(5) instead of bsd.README. (b) Write a script that parses bsd.README and outputs the information to mk.conf; cf. the idea in iic(4). (c) Make a mk.conf(5) a generic page that points to the corresponding files and related information, maybe with a small example. As I see it, (a) is not probably desirable and (b) is prone to errors. So I would propose (c). Objections? - Jukka.
23 Mar 2010 20:24
Re: mk.conf(5)
David Holland <dholland-docs <at> netbsd.org>
2010-03-23 19:24:39 GMT
2010-03-23 19:24:39 GMT
On Tue, Mar 23, 2010 at 08:15:37AM +0200, Jukka Ruohonen wrote: > The mk.conf(5) is one of those manual pages that are systematically behind. > It is generally a nightmare to maintain and the information is duplicated in > bsd.README. bsd.README should go away and be replaced with real documentation. IMO. -- -- David A. Holland dholland <at> netbsd.org
RSS Feed