This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch,wwwdocs] Update gcc.gnu.org/fortran


On Thu, 5 Oct 2006, Tobias Burnus wrote:
> Fortraners, is this patch ok?

Given FX's review, I take that this is fine from the Fortran side, so
let me only add some feedback from the documentation side.

Index: index.html
===================================================================
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>

You can omit this part; the DOCTYPE is added automatically on the
gcc.gnu.org and www.gnu.org servers.

-<h1>Welcome to the home of<br />GNU Fortran 95</h1>
+<h1>Welcome to the home of<br />GNU Fortran</h1>

While we are at it, I recommend to drop the <br /> here.

-GCC, the GNU Compiler Collection.  Gfortran development is a part of the
+GCC, the GNU Compiler Collection.  The GNU Fortran development is a part of the

I believe this should read "GNU Fortran development" (without "The").

-<p>We expect to provide the following
-<a href="extensions.html">language extensions</a>.</p>
+<h3>Extensions in GNU Fortran</h3>
+<p>The primary goal of the GNU Fortran Project is the construction of a Fortran 95 that complies with the ISO Fortran 95 Programming Language standard [ISO/IEC 1539-1:1997(E)]. The <a href="http://gcc.gnu.org/wiki/GFortran";>gfortran wiki</a> and the <a href="../bugzilla/">Bugzilla</a> contain of features yet to be implemented for conformance.</p>

Can you format this to not exceed some 76 columns?
 
+<p>We regularly update the <a href="http://gcc.gnu.org/wiki/GFortran#news";>status of the
+front end development and of the run time library development</a>.
+For a TODO list, check <a href="../bugzilla/">Bugzilla</a> and the <a href="http://gcc.gnu.org/wiki/GFortran";>gfortran wiki</a>.</p>

Also here?  For Bugzilla, we need an absolute link, referring to 
http://gcc.gnu.org/bugzilla/, since our web pages are also used on
http://www.gnu.org/software/gcc/.

 <h2>Usage</h2>
-<p>Here is a short <a href="usage.html">explanation</a> on how to invoke and
+<p>Here is a short <a href="http://gcc.gnu.org/wiki/GFortranUsage";>explanation</a> on how to invoke and
 use the compiler once you have built it (or downloaded the binary).</p>

Shouldn't this refer to one of the online manuals?

+relevant to Fortran programmers; the <a href="http://gcc.gnu.org/wiki/GFortran#manuals";>gfortran wiki</a> contains further links.</p>
 
Would you mind splitting this line?


As for removing files, I believe we should provide redirects for those.
Would you mind proposing such redirects (perhaps all to the main GNU
Fortran page) as additions to htdocs/.htaccess in our wwwdocs CVS repo?

As far as I can see, you do not have CVS write access.  If you could
provide an updated patch, I'll be glad to apply that for you and address
any potential markup or other issues I encounter.

Thanks,
Gerald


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]