[svn-r19550] _ edited the file for language

1 files changed, 122 insertions, 124 deletions

diff --git a/release_docs/RELEASE.txt b/release_docs/RELEASE.txt
index af3d31b..3d85838 100644
--- a/release_docs/RELEASE.txt
+++ b/release_docs/RELEASE.txt
@@ -60,43 +60,41 @@ New Features
       configuration options (better similarity to configure), added more
       tests, better support for use in external cmake projects. 
       (ADB - 2010/10/07)
-    - Changed configure default setting to --disable-production (was
-      --enable-production). This affects all unoffical releases such as
-      snapshot releases. It will be set to --enable-production for all
-      official releases.  (AKC  - 2010/05/28)
-
+    - The default configuration setting for official releases is 
+      --enable-production. For unofficial releases, the default configuration 
+      setting has been --disable-production. (AKC  - 2010/05/28)
     Library
     -------
-    - Added support for threadsafety on windows using the windows threads
-      library. Use the HDF5_ENABLE_THREADSAFE option in CMake while on a 
-      windows platform to enable this functionality. This is supported on 
-      Windows Vista and newer Windows operating systems. (MAM - 2010/09/10)
-    - H5Tset_order and H5Tget_order now support all data types.  A new byte 
-      order H5T_ORDER_MIXED has been added specifically for compound datatype
-      and its derived type.  Please see bug #1934. (SLU - 2010/8/23)
-    - Improved performance of metadata I/O by changing the default algorithm
-      to perform I/O from all processes (instead of just process 0) when using
+    - Added support for thread safety on Windows using the Windows threads 
+      library. Use the HDF5_ENABLE_THREADSAFE option in CMake on a Windows 
+      platform to enable this functionality. This is supported on Windows 
+      Vista and newer Windows operating systems. (MAM - 2010/09/10)
+    - H5Tset_order and H5Tget_order now support all datatypes.  A new byte 
+      order, H5T_ORDER_MIXED, has been added specifically for a compound 
+      datatype and its derived type.  (SLU - 2010/8/23) 
+    - Improved performance of metadata I/O by changing the default algorithm 
+      to perform I/O from all processes (instead of just process 0) when using 
       parallel I/O drivers. (QAK - 2010/07/19)
-    - Improved performance of I/O on datasets with the same shape, but
+    - Improved performance of I/O on datasets with the same shape, but 
       different rank. (QAK - 2010/07/19)
-    - Improved performance of the chunk cache by avoiding unnecessary b-tree
+    - Improved performance of the chunk cache by avoiding unnecessary b-tree 
       lookups of chunks already in cache. (NAF - 2010/06/15) 
-
+      
     Parallel Library
     ----------------
     - None
  
     Tools
     -----
-    - h5diff: Add new flag --exclude-path.  The specified path to an object 
-      will be excluded when comparing two files or two groups. If a group is 
-      specified to be excluded, all member objects of that group will be 
-      excluded.  (JKM - 2010/09/16).
-    - h5ls: Add new flag --no-dangling-links.  See --help output for details.
-      (JKM - 2010/06/15)
-    - h5ls: Add new flag --follow-symlinks.  See --help output for details.
-      (JKM - 2010/05/25)
-
+    - h5diff: Added a new flag: --exclude-path.  The specified path to an 
+      object will be excluded when comparing two files or two groups. If a 
+      group is specified to be excluded, all member objects of that group 
+      will be excluded.  (JKM - 2010/09/16).
+    - h5ls: Added a new flag: --no-dangling-links.  See --help output for 
+      details. (JKM - 2010/06/15)
+    - h5ls: Added a new flag --follow-symlinks.  See --help output for 
+      details. (JKM - 2010/05/25)
+      
     High-Level APIs
     ---------------
     - None
@@ -123,10 +121,10 @@ Bug Fixes since HDF5-1.8.5
     - Removed recognition of the parallel compilers of LAM(hcc) and
       ChMPIon(cmpicc) since we have no access to these two MPI implementations
       and cannot verify their correctness. (AKC - 2010/07/14 - Bug 1921)
-    - PHDF5 changed to use "mpiexec", instead of mpirun, as the default MPI
-      applications startup command as defined in the MPI-2 definition, section
-      4.1. (AKC - 2010/06/11 - Bug 1921)
-
+    - PHDF5 was changed to use "mpiexec" instead of mpirun as the default 
+      MPI applications startup command as defined in the MPI-2 definition, 
+      section 4.1. (AKC - 2010/06/11 - Bug 1921)
+      
     Library
     -------
     - Modified library to always cache symbol table information.  Libraries
@@ -145,8 +143,8 @@ Bug Fixes since HDF5-1.8.5
     - When a mandatory filter failed to write data chunks, the dataset
       couldn't close (bug 1260).  The fix releases all resources and closes
       the dataset but returns a failure. (SLU - 2010/09/08) 
-    - H5Eset_current_stack now also closes the error stack to be set as the
-      default.  This is to avoid a potential problem. 
+    - H5Eset_current_stack now also closes the error stack set as the 
+      default. This is to avoid a potential problem. 
       (SLU - 2010/09/07 - Bug 1799)
     - Corrected situation where 1-D chunked dataset could get created by an
       application without calling H5Pset_chunk().  H5Pset_chunk is now
@@ -173,13 +171,12 @@ Bug Fixes since HDF5-1.8.5
 
     Tools
     -----
-    - Fixed h5diff to compare member objects and groups recursively when two 
-      files or groups are specieied to be compared. 
-      (JKM - 2010/9/16 - Bug 1975)
+    - Fixed h5diff to compare member objects and groups recursively when 
+      two files or groups are compared. (JKM - 2010/9/16 - Bug 1975)
     - Fixed h5repack to be able to convert a dataset to COMPACT layout.
       (JKM - 2010/09/15 - Bug 1896)
     - Changed h5ls to not interpret special characters in object or attribute
-      name for output. (JKM - 2010/06/28 - Bug 1784)
+      names for output. (JKM - 2010/06/28 - Bug 1784)
 
 
     F90 API
@@ -385,20 +382,19 @@ Known Problems
 * H5Eset_auto can cause a seg fault for a library API call if the application
   compiles with -DH5_USE_16_API (see bug 1707).  It will be fixed in the 
   next release. SLU - 2010/10/5
-* The library's test dt_arith.c showed a compiler's rounding problem on
-  Cygwin when converting from unsigned long long to long double.  The 
-  library's own conversion works fine.  We defined a macro for Cygwin to
-  skip this test until we can solve the problem.  Please see bug #1813.
-  SLU - 2010/5/5 
-* All the VFL drivers aren't backward compatible.  In H5FDpublic.h, the
-  structure H5FD_class_t changed in 1.8.  There is new parameter added to
-  get_eoa and set_eoa callback functions.  A new callback function
-  get_type_map was added in.  The public function H5FDrealloc was taken
-  out in 1.8.  The problem only happens when users define their own driver
-  for 1.6 and try to plug in 1.8 library.  Because there's only one user 
-  complaining about it, we (Elena, Quincey, and I) decided to leave it as 
-  it is (see bug report #1279).  Quincey will make a plan for 1.10.
-  SLU - 2010/2/2
+  
+* The library's test dt_arith.c showed a compiler's rounding problem on 
+  Cygwin when converting an unsigned long long to a long double.  The 
+  library's own conversion works fine.  We defined a macro for Cygwin to 
+  skip this test until we can solve the problem.  Please see bug #1813. 
+  SLU - 2010/5/5
+  
+* All the VFL drivers aren't backwardly compatible.  In H5FDpublic.h, the 
+  structure H5FD_class_t changed in 1.8.  A new parameter was added to the 
+  get_eoa and set_eoa callback functions, and a new callback function 
+  get_type_map was added. The public function H5FDrealloc was taken out in 
+  1.8.  The problem only happens when users define their own driver for 1.6 
+  and try to plug in a 1.8 library. This will be fixed in 1.10. SLU - 2010/2/2
 * MinGW has a missing libstdc++.dll.a library file and will not successfully link
   C++ applications/tests. Do not use the enable-cxx configure option. Read all of
   the INSTALL_MINGW.txt file for all restrictions. ADB - 2009/11/11
@@ -410,32 +406,31 @@ Known Problems
      LDR_CNTRL=MAXDATA=0x20000000@DSA
   AKC - 2009/10/31
 
-* The PathScale MPI implementation, accessing a Panasas file system, would
-  cause H5Fcreate() with H5F_ACC_EXCL to fail even when the file is not
-  existing. This is due to the MPI_File_open() call failing if the amode has
+* The PathScale MPI implementation, accessing a Panasas file system, would 
+  cause H5Fcreate() with H5F_ACC_EXCL to fail even when the file does not 
+  exist. This is due to the MPI_File_open() call failing if the amode has 
   the MPI_MODE_EXCL bit set. (See bug 1468 for details.) AKC - 2009/8/11
- 
+
 * Parallel tests failed with 16 processes with data inconsistency at testphdf5
   / dataset_readAll. Parallel tests also failed with 32 and 64 processes with
   collective abort of all ranks at t_posix_compliant / allwrite_allread_blocks
   with MPI IO. CMC - 2009/04/28
 
-* For gcc v4.3 and v4.4, with production mode, if -O3 is used, H5Tinit.c
-  would fail to compile. Actually bad H5Tinit.c is produced.  If -O (same
-  as -O1) is used, H5Tinit.c compiled okay but test/dt_arith would fail.
-  When -O0 (no optimizatio) is used, H5Tinit.c compilete okay and all
-  tests passed. Therefore, -O0 is imposed for v4.3 and v4.4 of gcc.
-  AKC - 2009/04/20
-
-* For Red Storm, a Cray XT3 system, the tools/h5ls/testh5ls.sh and
-  tools/h5copy/testh5copy.sh will fail some of its sub-tests. These sub-tests
-  are expected to fail and should exit with a non-zero code but the yod
-  command does not propagate the exit code of the executables. Yod always
-  returns 0 if it can launch the executable.  The test suite shell expects
-  a non-zero for this particular test, therefore it concludes the test has
-  failed when it receives 0 from yod.  Skip all the "failing" test for now
-  by changing them as following.
-
+* For gcc v4.3 and v4.4 with production mode, if -O3 is used, H5Tinit.c will 
+  fail to compile. A corrupted H5Tinit.c is produced.  If -O (same as -O1) is 
+  used, H5Tinit.c compiled okay but test/dt_arith would fail. When -O0 (no 
+  optimization) is used, H5Tinit.c compiles okay and all tests passed. 
+  Therefore, -O0 is imposed for v4.3 and v4.4 of gcc. AKC - 2009/04/20
+  
+* For Red Storm, a Cray XT3 system, the tools/h5ls/testh5ls.sh and 
+  tools/h5copy/testh5copy.sh will fail some of their sub-tests. These 
+  sub-tests are expected to fail and should exit with a non-zero code but 
+  the yod command does not propagate the exit code of the executables. Yod 
+  always returns 0 if it can launch the executable.  The test suite shell 
+  expects a non-zero for this particular test. Therefore, it concludes the 
+  test has failed when it receives 0 from yod.  To skip all the "failing" 
+  tests for now, change them as shown below.
+  
   ======== Original tools/h5ls/testh5ls.sh =========
   TOOLTEST tgroup-1.ls 1 -w80 -r -g tgroup.h5
   ======== Change to ===============================
@@ -457,59 +452,62 @@ Known Problems
   ==================================================
   AKC - 2008/11/10
 
-* For Red Storm, a Cray XT3 system, the yod command sometimes gives the
-  message,  "yod allocation delayed for node recovery".  This interferes with
-  test suites that do not expect seeing this message.  See the section of "Red
-  Storm" in file INSTALL_parallel for a way to deal with this problem.
+* For Red Storm, a Cray XT3 system, the yod command sometimes gives the 
+  message  "yod allocation delayed for node recovery."  This interferes 
+  with test suites that do not expect to see this message.  See the "Red Storm" 
+  section in file INSTALL_parallel for a way to deal with this problem. 
   AKC - 2008/05/28
-
-* On Intel 64 Linux cluster (RH 4, Linux 2.6.9) with Intel 10.0 compilers, 
-  use -mp -O1 compilation flags to build the libraries. A higher level of 
-  optimization causes failures in several HDF5 library tests. 
-
-* On mpich 1.2.5 and 1.2.6, if more than two processes contribute no IO and 
-  the application asks to do collective IO, we have found that when using 4 
-  processors, a simple collective write will sometimes be hung. This can be 
-  verified with t_mpi test under testpar.
-
-* A dataset created or rewritten with a v1.6.3 library or after cannot be read 
-  with the v1.6.2 library or before when the Fletcher32 EDC filter is enabled.
-  There was a bug in the calculation of the Fletcher32 checksum in the 
-  library before v1.6.3; the checksum value was not consistent between big-
-  endian and little-endian systems.  This bug was fixed in Release 1.6.3.  
-  However, after fixing the bug, the checksum value was no longer the same as 
-  before on little-endian system.  Library releases after 1.6.4 can still read 
-  datasets created or rewritten with an HDF5 library of v1.6.2 or before.  
-  SLU - 2005/6/30
-
-* On IBM AIX systems, parallel HDF5 mode will fail some tests with error
-  messages like "INFO: 0031-XXX ...".  This is from the command `poe'.
-  Set the environment variable MP_INFOLEVEL to 0 to minimize the messages
-  and run the tests again.
-
-  The tests may fail with messages like "The socket name is already in use",  
-  but HDF5 does not use sockets.  This failure is due to problems with the 
-  poe command trying to set up the debug socket.  To resolve this problem, 
-  check to see whether there are many old /tmp/s.pedb.* files staying around.  
-  These are sockets used by the poe command and left behind due to failed 
-  commands.  First, ask your system administrator to clean them out.  
-  Lastly, request IBM to provide a means to run poe without the debug socket.
-
-* The --enable-static-exec configure flag will only statically link libraries
-  if the static version of that library is present. If only the shared version
-  of a library exists (i.e., most system libraries on Solaris, AIX, and Mac,
-  for example, only have shared versions), the flag should still result in a 
-  successful compilation, but note that the installed executables will not be 
-  fully static. Thus, the only guarantee on these systems is that the 
-  executable is statically linked with just the HDF5 library.
-
-* There is also a configure error on Altix machines that incorrectly reports 
+  
+* On an Intel 64 Linux cluster (RH 4, Linux 2.6.9) with Intel 10.0 compilers, 
+  use the -mp -O1 compilation flags to build the libraries. A higher level 
+  of optimization causes failures in several HDF5 library tests.
+  
+* On mpich 1.2.5 and 1.2.6 on a system using four processors, if more than 
+  two processes contribute no I/O and the application asks to do collective 
+  I/O, we have found that a simple collective write will sometimes hang. This 
+  can be verified with the t_mpi test under testpar.
+  
+* A dataset created or rewritten with a v1.6.3 or later library cannot be 
+  read with the v1.6.2 or earlier library when the Fletcher32 EDC filter 
+  is enabled. There was a bug in the calculation of the Fletcher32 checksum 
+  in the library before v1.6.3; the checksum value was not consistent 
+  between big-endian and little-endian systems.  This bug was fixed in 
+  Release 1.6.3. However, after fixing the bug, the checksum value was no 
+  longer the same as before on little-endian system.  Library releases after 
+  1.6.4 can still read datasets created or rewritten with an HDF5 library of 
+  v1.6.2 or earlier. SLU - 2005/6/30
+  
+* On IBM AIX systems, parallel HDF5 mode will fail some tests with error 
+  messages like "INFO: 0031-XXX ...".  This is from the command `poe'. To 
+  work around this, set the environment variable MP_INFOLEVEL to 0 to 
+  minimize the messages and run the tests again. The tests may fail with 
+  messages like "The socket name is already in use", but HDF5 does not use 
+  sockets. This failure is due to problems with the poe command trying to 
+  set up the debug socket.  To resolve this problem, check to see whether 
+  there are any old /tmp/s.pedb.* files around. These are sockets used by 
+  the poe command and left behind if the command failed at some point. To 
+  resolve this, ask your system administrator to remove the 
+  old/tmp/s.pedb.* files, and then ask IBM to provide a means to run poe 
+  without the debug socket.
+
+* The --enable-static-exec configure flag will only statically link 
+  libraries if the static version of that library is present. If only the 
+  shared version of a library exists (i.e., most system libraries on 
+  Solaris, AIX, and Mac, for example, only have shared versions), the flag 
+  should still result in a successful compilation, but note that the 
+  installed executables will not be fully static. Thus, the only guarantee 
+  on these systems is that the executable is statically linked with just 
+  the HDF5 library.
+  
+* There is a configure error on Altix machines that incorrectly reports 
   when a version of Szip without an encoder is being used.
-
-* On cobalt, an SGI Altix SMP ia64 system, Intel compiler version 10.1 (which
-  is the default on that system) does not work properly, and results in
-  failures during make check (in a static build) and make installcheck (during
-  a shared build). This appears to be a compiler optimization problem.
-  Reducing optimization by setting CFLAGS to -O1 or below resolves the issue.
-  Alternatively, using a newer version of the compiler (11.0) also works as
-  intended. MAM - 2010/06/01
+  
+* On an SGI Altix SMP ia64 system, the Intel compiler version 10.1 (which 
+  is the default on that system) does not work properly and results in 
+  failures during the make check (in a static build) and the make 
+  installcheck (in a shared build). This appears to be a compiler 
+  optimization problem. Reducing the optimization by setting CFLAGS to 
+  -O1 or below resolves the issue. Using a newer version of the compiler 
+  (11.0) avoids the issue. MAM - 2010/06/01
+  
+  
\ No newline at end of file