diff DOCS/users_against_developers.html @ 7076:3275af5787e0

Applied patch by Andras Mohari <[e-mail]>, slightly modified. * Fixed <> chars (or replaced them with something else, where it was trivial). * weblint complained about <A HREF="...">here</A> being a bad form, so I replaced them with more descriptive text. * Fixed empty <A NAME="..."> tags.

--- a/DOCS/users_against_developers.html	Fri Aug 23 01:41:12 2002 +0000
+++ b/DOCS/users_against_developers.html	Fri Aug 23 10:50:19 2002 +0000
@@ -49,7 +49,7 @@
   bugs, especially since some workarounds may imply a performance penalty.</P>
 
 <P>You can read about the other side of the story
-  <A HREF="http://www.bero.org/gcc296.html">here</A>.
+  <A HREF="http://www.bero.org/gcc296.html">at this site</A>.
   GCC 2.96 does not allow | (pipe) characters in assembler comments
   because it supports Intel as well as AT&amp;T Syntax and the | character is a
   symbol in the Intel variant. The problem is that it <B>silently</B> ignores the
@@ -67,9 +67,9 @@
 
 <P>If you have problems with GCC 2.96, you can get 2.96-85 packages from the
   Red Hat <A HREF="ftp://updates.redhat.com">ftp server</A>, or just go for the
-  3.0.4 packages offered for version 7.2 and later. You can also get gcc-3.1
-  packages (unofficial, but working fine)
-  <A HREF="ftp://people.redhat.com/jakub/gcc3/3.1-1/">here</A> and you can
+  3.0.4 packages offered for version 7.2 and later. You can also get
+  <A HREF="ftp://people.redhat.com/jakub/gcc3/3.1-1/">gcc-3.1 packages</A>
+  (unofficial, but working fine) and you can
   install them along the gcc-2.96 you already have. MPlayer will detect it and
   use 3.1 instead of 2.96. If you do not want to or cannot use the binary
   packages, here is how you can compile GCC 3.1 from source:</P>