[wwwdocs,Java] java/index.html -- fix formatting on gcc.gnu.org

[wwwdocs,Java] java/index.html -- fix formatting on gcc.gnu.org

[Gerald Pfeifer]

It turns out the stricter server settings also broke the /java
page on gcc.gnu.org.

This restores showing two columns on this page (though it still
uses non-standard CSS extensions).


That said, looking at the page, and how since 2005 nearly all changes
have been maintainance ones from me, is it really worthwhile keeping
this (short of historic reasons)?

2016-04-08  Gerald Pfeifer  <gerald@pfeifer.com>

	* index.html: Replace manual style to establish two columns
	by new global CSS class "twocolumns".

Index: gcc.css
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc.css,v
retrieving revision 1.38
diff -u -r1.38 gcc.css
--- gcc.css	5 Apr 2016 16:20:29 -0000	1.38
+++ gcc.css	9 Apr 2016 16:22:40 -0000
@@ -15,6 +15,8 @@
 .highlight{ color: darkslategray; font-weight:bold; }
 .smaller  { font-size: 80%; }
 
+.twocolumns { column-counts:2; -moz-column-count:2; }
+
 td.news      { width: 50%; padding-right: 8px; }
 td.news h2   { font-size: 1.2em; margin-top: 0; margin-bottom: 2%; }
 td.news dl   { margin-top:0; }

Index: java/index.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/java/index.html,v
retrieving revision 1.177
diff -u -r1.177 index.html
--- java/index.html	27 Jun 2014 15:04:39 -0000	1.177
+++ java/index.html	9 Apr 2016 16:22:41 -0000
@@ -32,7 +33,7 @@
 
 <h2><a name="news">GCJ News</a></h2>
 
-<div style="column-count:2; -moz-column-count:2;">
+<div class="twocolumns">
 
 <!-- News entries start here -->
 

Re: [wwwdocs,Java] java/index.html -- fix formatting on gcc.gnu.org

[Andrew Hughes]

----- Original Message -----
> It turns out the stricter server settings also broke the /java
> page on gcc.gnu.org.
> 
> This restores showing two columns on this page (though it still
> uses non-standard CSS extensions).
> 
> 
> That said, looking at the page, and how since 2005 nearly all changes
> have been maintainance ones from me, is it really worthwhile keeping
> this (short of historic reasons)?
> 
> 2016-04-08  Gerald Pfeifer  <gerald@pfeifer.com>
> 
> 	* index.html: Replace manual style to establish two columns
> 	by new global CSS class "twocolumns".
> 
> Index: gcc.css
> ===================================================================
> RCS file: /cvs/gcc/wwwdocs/htdocs/gcc.css,v
> retrieving revision 1.38
> diff -u -r1.38 gcc.css
> --- gcc.css	5 Apr 2016 16:20:29 -0000	1.38
> +++ gcc.css	9 Apr 2016 16:22:40 -0000
> @@ -15,6 +15,8 @@
>  .highlight{ color: darkslategray; font-weight:bold; }
>  .smaller  { font-size: 80%; }
>  
> +.twocolumns { column-counts:2; -moz-column-count:2; }
> +
>  td.news      { width: 50%; padding-right: 8px; }
>  td.news h2   { font-size: 1.2em; margin-top: 0; margin-bottom: 2%; }
>  td.news dl   { margin-top:0; }
> 
> Index: java/index.html
> ===================================================================
> RCS file: /cvs/gcc/wwwdocs/htdocs/java/index.html,v
> retrieving revision 1.177
> diff -u -r1.177 index.html
> --- java/index.html	27 Jun 2014 15:04:39 -0000	1.177
> +++ java/index.html	9 Apr 2016 16:22:41 -0000
> @@ -32,7 +33,7 @@
>  
>  <h2><a name="news">GCJ News</a></h2>
>  
> -<div style="column-count:2; -moz-column-count:2;">
> +<div class="twocolumns">
>  
>  <!-- News entries start here -->
>  
> 

I guess the next news will be the removal of GCJ during the
GCC 7 development period, so its remaining shelf life should
be limited anyway.
-- 
Andrew :)

Senior Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)

PGP Key: ed25519/35964222 (hkp://keys.gnupg.net)
Fingerprint = 5132 579D D154 0ED2 3E04  C5A0 CFDA 0F9B 3596 4222

Re: [wwwdocs,Java] java/index.html -- fix formatting on gcc.gnu.org

[Gerald Pfeifer]

On Sun, 10 Apr 2016, Andrew Hughes wrote:
>> That said, looking at the page, and how since 2005 nearly all changes
>> have been maintainance ones from me, is it really worthwhile keeping
>> this (short of historic reasons)?
> I guess the next news will be the removal of GCJ during the
> GCC 7 development period, so its remaining shelf life should
> be limited anyway.

Soo, GCC 6 has branched -- would it make sense for you guys to
start this removal?

Somewhat related, any concerns if I were to remove
https://gcc.gnu.org/java/status.html now?

("Status of GCJ as of GCC 3.2" _really_ is rather old.)

Gerald

Re: [wwwdocs,Java] java/index.html -- fix formatting on gcc.gnu.org

[Andrew Haley]

On 16/04/16 21:31, Gerald Pfeifer wrote:
> On Sun, 10 Apr 2016, Andrew Hughes wrote:
>>> That said, looking at the page, and how since 2005 nearly all changes
>>> have been maintainance ones from me, is it really worthwhile keeping
>>> this (short of historic reasons)?
>> I guess the next news will be the removal of GCJ during the
>> GCC 7 development period, so its remaining shelf life should
>> be limited anyway.
> 
> Soo, GCC 6 has branched -- would it make sense for you guys to
> start this removal?

Sounds good.  OTOH, I don't think there's any great hurry.

> Somewhat related, any concerns if I were to remove
> https://gcc.gnu.org/java/status.html now?
> 
> ("Status of GCJ as of GCC 3.2" _really_ is rather old.)

It's so old that I don't think it's of any use.  However, I wonder if
it might make more sense to at least have a page saying that GCJ is
gone.

Andrew.

[wwwdocs,Java] Remove java/status.html

[Gerald Pfeifer]

On Sun, 17 Apr 2016, Andrew Haley wrote:
>> Somewhat related, any concerns if I were to remove
>> https://gcc.gnu.org/java/status.html now?
>> 
>> ("Status of GCJ as of GCC 3.2" _really_ is rather old.)
> It's so old that I don't think it's of any use.  However, I wonder 
> if it might make more sense to at least have a page saying that GCJ 
> is gone.

My recommendation is to handle that via java/index, which is the
main page, and redirect other GCJ pages to that one as we remove
them.

Like in the following, for java/status.html.

Are you fine with that?

Gerald

Index: .htaccess
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/.htaccess,v
retrieving revision 1.36
diff -u -r1.36 .htaccess
--- .htaccess	29 Oct 2015 10:13:08 -0000	1.36
+++ .htaccess	17 Apr 2016 16:00:58 -0000
@@ -51,6 +51,7 @@
 Redirect permanent /java/gcj.html		https://gcc.gnu.org/java/
 Redirect permanent /java/libgcj.html		https://gcc.gnu.org/java/
 Redirect permanent /java/about.html		https://gcc.gnu.org/about.html
+Redirect permanent /java/status.html		https://gcc.gnu.org/java/
 
 Redirect permanent /bugs.html			https://gcc.gnu.org/bugs/
 Redirect permanent /c9xstatus.html		https://gcc.gnu.org/c99status.html
Index: style.mhtml
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/style.mhtml,v
retrieving revision 1.128
diff -u -r1.128 style.mhtml
--- style.mhtml	16 Apr 2016 21:57:06 -0000	1.128
+++ style.mhtml	17 Apr 2016 16:00:58 -0000
@@ -124,7 +124,6 @@
     <p>
     <a href="index.html">GCJ Home</a><br />
     <a href="../">GCC Home</a><br />
-    <a href="status.html">Status</a><br />
     <a href="faq.html">FAQ</a><br />
     <a href="docs.html">Documentation</a><br />
     <a href="contrib.html">Contributing</a><br />


2016-04-17  Gerald Pfeifer  <gerald@pfeifer.com>

	* status.html: Remove.

Index: java/status.html
===================================================================
RCS file: java/status.html
diff -N java/status.html
--- java/status.html	2 Jul 2014 15:40:11 -0000	1.33
+++ /dev/null	1 Jan 1970 00:00:00 -0000
@@ -1,154 +0,0 @@
-<html>
-
-<head>
-<title>GCJ - Status</title>
-
-<style type="text/css">
-dt.package { font-weight: bold; font-family: monospace }
-dt.target { font-weight: bold }
-</style>
-
-</head>
-
-<body>
-
-<h1>GCJ Status</h1>
-
-<p>Status of GCJ as of GCC 3.2.  Improvements that are only
-in current development versions are marked as "in CVS".</p>
-
-<h2 id="features">Core Features</h2>
-
-<ul>
-<li>Compile Java source code ("ahead-of-time") to native (machine) code,</li>
-<li>Compile Java bytecode (<code>.class</code> files) to native (machine) code,</li>
-<li>Compile Java source code to <code>.class</code> files (<code>javac</code> replacement).</li>
-<li>A byte-code interpreter, allowing support for <code>ClassLoader</code>s,
-and dynamically loaded classes. Corresponds to JDK's <code>java</code> command.</li>
-<li>Support for JNI, as well as CNI, a more efficient and easier-to-use
-(though non-standard) API for writing Java methods in C++.</li>
-<li> Verification, both at compile time (compiling classes to
-native) and run-time (loading classes).  Both miss some tests, and
-you should not (yet) rely on their correctness for security.</li>
-<li>A "conservative" garbage collector.</li>
-<li>Replacements for the <code>jar</code>, <code>javah</code>,
-<code>rmic</code>, and <code>rmiregistry</code> programs.</li>
-<li>An extensive class library - see below.</li>
-</ul>
-
-
-<h2 id="packages">Implemented Packages</h2>
-
-<dl>
-<dt class="package">java.applet</dt>
-<dd>Believed to be complete, but note that without a functional AWT
-it isn't very useful.</dd>
-<dt class="package">java.awt</dt>
-<dd>A lot of code exists, but not enough for use in real applications.</dd>
-<dt class="package">java.beans</dt>
-<dd>Believed to be functional and complete, should be compatible with JDK 1.4.</dd>
-<dt class="package">java.io</dt>
-<dd>Ok.</dd>
-<dt class="package">java.lang</dt>
-<dd>Ok.</dd>
-<dt class="package">java.lang.ref</dt>
-<dd>Ok.</dd>
-<dt class="package">java.lang.reflect</dt>
-<dd>Ok.  Does not check access permissions.</dd>
-<dt class="package">java.math</dt>
-<dd>Ok.</dd>
-<dt class="package">java.net</dt>
-<dd>Ok.</dd>
-<dt class="package">java.nio</dt>
-<dd>The public interface is ready, but the implementation is not working yet.</dd>
-<dt class="package">java.rmi</dt>
-<dd>Ok.</dd>
-<dt class="package">java.security</dt>
-<dd>Code exist; completeness unknown.</dd>
-<dt class="package">java.sql</dt>
-<dd>Ok, should be compatible with JDK 1.4.</dd>
-<dt class="package">java.util</dt>
-<dd>Ok.</dd>
-<dt class="package">java.util.jar</dt>
-<dd>Ok.</dd>
-<dt class="package">java.util.regex</dt>
-<dd>Ok.</dd>
-<dt class="package">java.util.zip</dt>
-<dd>Ok.</dd>
-<dt class="package">java.text</dt>
-<dd>Ok, but most localization data not available.</dd>
-<dt class="package">javax.accessibility</dt>
-<dd>Some code; status unknown.</dd>
-<dt class="package">javax.crypto</dt>
-<dd>We recommend using <a
-href="http://www.gnu.org/software/gnu-crypto/">GNU Crypto</a>.</dd>
-<dt class="package">javax.naming</dt>
-<dd>Complete, but no providers written.</dd>
-<dt class="package">javax.sql</dt>
-<dd>Some code; status unknown.</dd>
-<dt class="package">javax.swing</dt>
-<dd>Some code, but not enough for real applications.</dd>
-<dt class="package">javax.transaction</dt>
-<dd>Complete, but no providers written.</dd>
-</dl>
-
-<p>You can also see <a
-href="libgcj-classpath-compare.html">a
-comparison of our classes with Classpath's</a>.  Differences here are
-merged from time to time.  You can also see
-<a href="gui-compare/libgcj-classpath-compare.html">
-a comparison of the GUI branch with Classpath</a>.
-</p>
-
-
-<h2 id="targets">Supported Targets</h2>
-
-<dl>
-<dt class="target">GNU/Linux on the Pentium-compatible PCs
-  (<code>i[56]86-pc-linux-gnu</code>)</dt>
-<dd>Ok.</dd>
-<dt class="target">FreeBSD on the Pentium-compatible PCs
-  (<code>i[56]86-pc-freebsd*</code>)</dt>
-<dd>Ok.</dd>
-<dt class="target">GNU/Linux on Alpha
-  (<code>alpha*-*-linux-gnu</code>)</dt>
-<dd>Ok.</dd>
-<dt class="target">GNU/Linux on the Itanium (ia64) architecture
-  (<code>ia64-*-linux-gnu</code>)</dt>
-<dd>Ok.</dd>
-<dt class="target">GNU/Linux on PowerPC</dt>
-<dd>Ok.</dd>
-<dt class="target">GNU/Linux on AMD x86-64 ("Hammer") architecture 
-(<code>x86_64-*-linux-gnu</code>)</dt>
-<dd>Ok, in CVS (but building with multilibs enabled needs libtool patch).</dd>
-<dt class="target">Solaris 2.5.1, 2.6, 2.7, 2.8 on SPARC
-  (<code>sparc*-sun-solaris2.[5678]</code>)</dt>
-<dd>Ok for 32- and 64-bit ABIs.  Byte-code interpreter not currently
-supported.</dd>
-<dt class="target">SGI Irix 6.5 on Mips
-  (<code>mips-sgi-irix6.5</code>)</dt>
-<dd>Some tricks required to build.  Byte-code interpreter not
-currently supported.  No SEGV handler available.</dd>
-<dt class="target">Windows on the Intel PC platform, using the MingW32 compiler
-  (<code>i[56]86-pc-mingw32</code>)</dt>
-<dd>Works for target; works for host (in CVS).  Is incomplete.</dd>
-<dt class="target">PPC Darwin (including MacOS X)</dt>
-<dd>Some kludges needed.</dd>
-<dt class="target">DEC OSF 4.0f and OSF 5.1 on Alpha
-  (<code>alpha-dec-osf4.0f</code>, <code>alpha-dec-osf5.1</code>)</dt>
-<dd>Ok.</dd>
-<dt class="target">Bare metal ARM ELF using newlib
-  (<code>arm-elf</code>)</dt>
-<dd>Ok, in CVS.  No threads, file I/O or networking.</dd>
-<dt class="target">Bare metal XScale ELF using newlib
-  (<code>xscale-elf</code>)</dt>
-<dd>Ok.  No threads, file I/O or networking.</dd>
-<dt class="target">IBM s390x</dt>
-<dd>Ok, in CVS.</dd>
-<dt class="target">GNU/Linux on Hitachi SH-3/4 micro-controller
-  (<code>sh[34]-*-linux</code>)</dt>
-<dd>Ok, in CVS.</dd>
-</dl>
-
-</body>
-</html>

Re: [wwwdocs,Java] Remove java/status.html

[Andrew Haley]

On 17/04/16 17:09, Gerald Pfeifer wrote:
> My recommendation is to handle that via java/index, which is the
> main page, and redirect other GCJ pages to that one as we remove
> them.
> 
> Like in the following, for java/status.html.
> 
> Are you fine with that?

OK, thanks.

Andrew.

Re: [wwwdocs,Java] java/index.html -- fix formatting on gcc.gnu.org

[Mike Stump]

> On Apr 16, 2016, at 1:31 PM, Gerald Pfeifer <gerald@pfeifer.com> wrote:
> Soo, GCC 6 has branched -- would it make sense for you guys to
> start this removal?

No, the home page says:

  Status: 2016-03-10 (regression fixes & docs only).

for gcc 7 (aka trunk).  Technically, that should update to say all fixes, _before_ any change goes in.  :-)

I must admit, I’m not sure why trunk is listed that way now.  I did expect branching to have switched that.