Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 15 Nov 1998 22:26:15 +0000
From:      Nik Clayton <nik@nothing-going-on.demon.co.uk>
To:        Malartre <malartre@aei.ca>, doc@FreeBSD.ORG
Subject:   Re: Debian (french page!) and GTML.
Message-ID:  <19981115222615.18414@nothing-going-on.org>
In-Reply-To: <364BA59B.A403C81F@aei.ca>; from Malartre on Thu, Nov 12, 1998 at 10:20:59PM -0500
References:  <364BA59B.A403C81F@aei.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 12, 1998 at 10:20:59PM -0500, Malartre wrote:
> I just checked www.debian.org. Since one year, that site changed a lot.
> First, I was surprised to see that site in French! (I "accidentaly"
> setted the "languages" preference in Netscape to French(fr), without
> knowing what it would do). Surprise! debian.org use that cool feature.
> see (http://www.debian.org/intro/cn.html.en)
> It's near FreeBSD quality :-)
> see (http://www.debian.org/~elphick/ddp/)

Don't know -- I've noted this for further investigation in a couple of
weeks, if no one else has got to it by then.

> On another topic:
> I would like to allow many peoples to work on TFUG, since I think it's a
> viable project. I don't know what solutions I could use.
> 
> First: should I port it to SGML? 

If it all possible. Although you won't be porting it to SGML, you'll be
porting it to DocBook.

OK, I'm being pedantic. DocBook and HTML share the same relationship to
SGML -- they're both languages defined using SGML.

> I never used SGML. The main problem (if
> you see it) is that it's not really portable to anything else than HTML
> I think. It use a lot of <table> tag, special colors... I use "GTML" to
> generate style/colors and the NEXT HOME BACK link at the top and bottom.
> Now it's simple for me to respect the style of it since all is automated
> when I generate the script. I could even automate <TABLE> tag.

Most of that looks like it's stuff to specify commands, examples, and
the like. DocBook doesn't need these, since it has element like

    <userinput>
    <command>
    <example>
    <screen>

and so on. These, in conjunction with a stylesheet, determine what the
output looks like.

See, for example, the Handbook converted from DocBook to HTML, at

    <URL:http://www.freebsd.org/~nik/handbook/index.html>;

As you can see, userinput is clearly defined, navigation links are 
present, and so on.

See also my introduction to the Doc. Proj., at

    <URL:http://www.freebsd.org/~nik/primer/index.html>;

which has a lot of information about DocBook, the tags you want to use,
and so on. The primer is incomplete, I should be uploading a more
complete version tomorrow (Monday) evening.

> Second: How could I let people adding text to it but respecting the
> style of it. What are the tools available to share it and let them
> submit new work and corrections?

The simplest way is to let people download the source from you, and 
include instructions explaining how they can send you the diff. 
Alternatively, if and when this becomes a part of the core FreeBSD 
doc set, people can receive it in the same ways they can receive
the other FreeBSD core docs.

You don't need to worry about the 'style' of it, because the style is
dictated by the stylesheet. As long as people submitting content to you
use the same elements to mean the same thing, it will look the same.
This is one of the reasons I've written the primer listed above.

Incidentally, have you considered getting a lot of this content 
integrated into the FAQ? A lot of it looks like FAQ material.

N
-- 
	    C.R.F. Consulting -- we're run to make me richer. . .

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?19981115222615.18414>