[OpenAFS-Doc] Apologies about documentation mess
renato arruda
rarruda0@gmail.com
Fri, 19 Aug 2005 10:27:11 -0300
------=_Part_6651_31417878.1124458031704
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Hi,
I guess i should apologize for the mess i probably ended up making in the=
=20
documentation project. But here is my side of the story.
A while ago i needed some documentation that was better formatted than wha=
t=20
was available from the website and i felt it needed to be updated. The=20
documentation project looked kinda dead back then, so i decided to do some=
=20
work because then i had a personal need for it.=20
Since the format that the HTML pages followed were very similar to LaTeX=
=20
and i already knew LaTeX, for me it seemed like an obvious choice to write =
a=20
parser that would convert the HTML to latex and live with that. Now if you=
=20
say that LaTeX isnt the best tool for the job, then i will have to agree.=
=20
But at the time i didnt have the time to learn a new tool and then write=20
parsers to convert the existing documentation to it. LaTeX seemed ok becaus=
e=20
it could generate both HTML and PDF for the manuals (never really thought=
=20
too much about the man page to be honest). I never thought that LaTeX would=
=20
be a final solution, but that once i got all the manual converted to latex=
=20
(which i never did), I could write another parser to some other format like=
=20
docbook (or whatever it would be felt to be the most appropriate solution).=
=20
I dont intend to start a flame war over a format either, but for an=20
official documentation format Esther should be the most adequate person to=
=20
make the call, imho. And in my opinion a single source for all the=20
documentation is a must. I=B4ve been away from the community for a while fo=
r=20
personal reasons, but now i should have a few hours here and there to work=
=20
on the project helping out on what=B4s needed.=20
I=B4m sorry if i have ended up causing disburbances on the community, I=20
_never_ intended for that to happen. At the time i just wanted something=20
that would work better for me, and if it would help others, then it would=
=20
all good too.=20
-Renato
------=_Part_6651_31417878.1124458031704
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
<div>Hi,</div>
<div> </div>
<div>I guess i should apologize for the mess i probably ended up making in =
the documentation project. But here is my side of the story.</div>
<div> </div>
<div>A while ago i needed some documentation that was better formatted than=
what was available from the website and i felt it needed to be updated. Th=
e documentation project looked kinda dead back then, so i decided to do som=
e work because then i had a personal need for it.=20
</div>
<div> </div>
<div>Since the format that the HTML pages followed were very similar to LaT=
eX and i already knew LaTeX, for me it seemed like an obvious choice to wri=
te a parser that would convert the HTML to latex and live with that. Now if=
you say that LaTeX isnt the best tool for the job, then i will have to agr=
ee. But at the time i didnt have the time to learn a new tool and then writ=
e parsers to convert the existing documentation to it. LaTeX seemed ok beca=
use it could generate both HTML and PDF for the manuals (never really thoug=
ht too much about the man page to be honest). I never thought that LaT=
eX would be a final solution, but that once i got all the manual conve=
rted to latex (which i never did), I could write another parser to som=
e other format like docbook (or whatever it would be felt to be t=
he most appropriate solution).=20
</div>
<div> </div>
<div>I dont intend to start a flame war over a format either, but for =
an official documentation format Esther should be the most adequate person =
to make the call, imho. And in my opinion a single source for all=
the documentation is a must. I=B4ve been away from the community for =
a while for personal reasons, but now i should have a few hours here and th=
ere to work on the project helping out on what=B4s needed.=20
</div>
<div> </div>
<div>I=B4m sorry if i have ended up causing disburbances on the community, =
I _never_ intended for that to happen. At the time i just wanted something =
that would work better for me, and if it would help others, then it would a=
ll good too.=20
</div>
<div> </div>
<div>-Renato</div>
------=_Part_6651_31417878.1124458031704--