From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org
Subject: [wwwdocs] Use regular markup for java/status.html
Date: Tue, 01 Nov 2011 14:13:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1111011503450.3250@gerinyyl.fvgr> (raw)
That does not fix the fact that the status is not up-to-date, but
makes things more consistent and easier to carry along in case of
future updates.
Applied.
Gerald
2011-11-01 Gerald Pfeifer <gerald@pfeifer.com>
* status.html: Use <h2> instead of fake tables.
Index: status.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/java/status.html,v
retrieving revision 1.30
diff -u -r1.30 status.html
--- status.html 27 Jul 2004 23:59:38 -0000 1.30
+++ status.html 1 Nov 2011 14:03:45 -0000
@@ -17,14 +17,7 @@
<p>Status of GCJ as of GCC 3.2. Improvements that are only
in current development versions are marked as "in CVS".</p>
-<table id="features" border="0" cellpadding="4" width="95%">
-<tr bgcolor="#b0d0ff">
- <th align="left">
- Core Features
- </th>
-</tr>
-</table>
-<br />
+<h2 id="features">Core Features</h2>
<ul>
<li>Compile Java source code ("ahead-of-time") to native (machine) code,</li>
@@ -43,14 +36,8 @@
<li>An extensive class library - see below.</li>
</ul>
-<table id="packages" border="0" cellpadding="4" width="95%">
-<tr bgcolor="#b0d0ff">
- <th align="left">
- Implemented Packages
- </th>
-</tr>
-</table>
+<h2 id="packages">Implemented Packages</h2>
<p>You can also see <a href="http://www.kaffe.org/~stuart/japi/">a
comparison of libgcj with the JDK</a>. This is updated nightly. It
@@ -118,13 +105,8 @@
a comparison of the GUI branch with Classpath</a>.
</p>
-<table id="targets" border="0" cellpadding="4" width="95%">
-<tr bgcolor="#b0d0ff">
- <th align="left">
- Supported Targets
- </th>
-</tr>
-</table>
+
+<h2 id="targets">Supported Targets</h2>
<dl>
<dt class="target">GNU/Linux on the Pentium-compatible PCs
reply other threads:[~2011-11-01 14:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.00.1111011503450.3250@gerinyyl.fvgr \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).