From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org
Subject: [wwwdocs] Use regular <h2> markup for java/projects.html
Date: Sat, 30 Apr 2011 12:11:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1104262224010.3044@gerinyyl.fvgr> (raw)
If really desired, we can reinstate the original look via CSS, though
I'd like to keep things consistent across all GCC pages.
Gerald
2011-04-26 Gerald Pfeifer <gerald@pfeifer.com>
* projects.html: Use regular <h2> markup for section headers
instead of fake tables.
Index: java/projects.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/java/projects.html,v
retrieving revision 1.33
diff -u -r1.33 projects.html
--- java/projects.html 25 Oct 2008 17:44:03 -0000 1.33
+++ java/projects.html 26 Apr 2011 20:24:01 -0000
@@ -18,30 +18,16 @@
href="mailto:java-patches@gcc.gnu.org">java-patches</a> list.
</p>
-<br />
-<table border="0" cellpadding="4" width="95%">
-<tr bgcolor="#b0d0ff">
- <th align="left">
-jar support
- </th>
-</tr>
-</table>
-<br />
+
+<h2>jar support</h2>
<p>
Modify gcj to obey the constraints layed out by the jar file
manifest file.
</p>
-<br />
-<table border="0" cellpadding="4" width="95%">
-<tr bgcolor="#b0d0ff">
- <th align="left">
-Plugin for Mozilla
- </th>
-</tr>
-</table>
-<br />
+
+<h2>Plugin for Mozilla</h2>
<p>
<a href="http://www.mozilla.org/">Mozilla</a> is open-source web browser,
@@ -52,15 +38,8 @@
(gijzilla?).
</p>
-<br />
-<table border="0" cellpadding="4" width="95%">
-<tr bgcolor="#b0d0ff">
- <th align="left">
-Benchmark infrastructure
- </th>
-</tr>
-</table>
-<br />
+
+<h2>Benchmark infrastructure</h2>
<p>
Measuring performance is tricky business. We currently do all our
@@ -75,18 +54,12 @@
Building some infrastructure around these would be incredibly useful.
</p>
-<br />
-<table border="0" cellpadding="4" width="95%">
-<tr bgcolor="#b0d0ff">
- <th align="left">
-Performance improvements
- </th>
-</tr>
-</table>
-<br />
-There are a few concrete performance improvements that we already know
-we want:
+<h2>Performance improvements</h2>
+
+<p>There are a few concrete performance improvements that we already know
+we want:</p>
+
<ul>
<li><p>If an object or array is allocated in static code that is
executed at most once (i.e. not in a loop or in a non-private
@@ -120,15 +93,8 @@
</p></li>
</ul>
-<br />
-<table border="0" cellpadding="4" width="95%">
-<tr bgcolor="#b0d0ff">
- <th align="left">
-Compiler improvements
- </th>
-</tr>
-</table>
-<br />
+
+<h2>Compiler improvements</h2>
<ul>
<li>We'd like gcj to do tree-level inlining like the C++
@@ -187,15 +153,9 @@
second one is higher priority.)</li>
</ul>
-<br />
-<table border="0" cellpadding="4" width="95%">
-<tr bgcolor="#b0d0ff">
- <th align="left">
-Runtime improvements
- </th>
-</tr>
-</table>
-<br />
+
+<h2>Runtime improvements</h2>
+
<ul>
<li>Write a program to convert existing locale data into a
format we can use.</li>
next reply other threads:[~2011-04-30 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 12:11 Gerald Pfeifer [this message]
2011-04-30 14:05 ` Steven Bosscher
2011-05-08 23:01 ` Gerald Pfeifer
2011-05-13 10:28 ` Gerald Pfeifer
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.1104262224010.3044@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).