Changes between Version 1 and Version 2 of loadingxmlcontentcharsetdetection

Timestamp:

Oct 7, 2011, 2:45:06 AM (13 years ago)

Author:

simonp

Comment:

--

loadingxmlcontentcharsetdetection

@@ -18 +18 @@
  * '''Module''': Jeeves
 
-=== Links ===
- * '''Documents''':
- * '''Email discussions''':
- * '''Other wiki discussions''':
-
 === Voting History ===
- * Vote proposed by X on Y, result was +/-n (m non-voting members).
+ * Vote proposed by Simon on 2011/10/07, result was +/-n (m non-voting members).
 
 ----
 
 == Motivations ==
-The current configuration is .... A change to ....
+
+GeoNetwork should be able to load and convert XML files that contain characters from character sets other than UTF-8. For example, loading a file with characters from the WINDOWS-1252 charset causes batch import to fail with a message like:
+
+
 
 == Proposal == 
-An in depth proposal can be found here : link
-...
+
+jeeves.utils.Xml - loadFile method needs to be modified to read the file as a stream of bytes, detect the character set and convert to UTF-8 as required. By default this character set detection capability is enabled by setting the java system property jeeves.filecharsetdetectandconvert.  
 
 === Backwards Compatibility Issues ===
 
+None because character set detection and conversion can be disabled on startup by setting the java system property jeeves.filecharsetdetectandconvert to disabled. eg. export JAVA_OPTS="-Djeeves.filecharsetdetectandconvert=disabled" if using tomcat or by editing bin/start-geonetwork.sh for jetty.
+
 === New libraries added ===
-Explain which and why new libraries are required for that proposal ...
+
+juniversalchardet - character set detection jar
 
 == Risks ==
 
+None known.
+
 == Participants ==
- * List of participants and role (if necessary) in current GIP 
+ * Simon Pigot