...
This HOWTO will give some tips and tricks to ensure your DSpace repository, user interfaces and servlet container are consistent in their handling of character encoding (and, better yet, compliant with UTF-8). It will also hopefully serve to remind developers of common pitfalls, so they can be avoided in future ;-)
In DSpace 1.5.2 and 1.6.0, many character encoding fixes were submitted to help DSpace become more compliant with UTF-8. Previous versions may find that handling of text in search forms, license text, collection and community names is inconsistent, particularly in XMLUI (Manakin). A list of relevant JIRA issues can be found at the end of this page to help you identify any possible character encoding issues with your version of DSpace.
...
Character encoding in XMLUI (Manakin)
Character encoding in Apache Tomcat
Character encoding in PostgreSQL
Still to add: Guides for other servlet containers (Glassfish, JBoss, Jetty, etc.); guide for Oracle; other DSpace webapps (SWORD, LNI, OAI, etc.)
Useful links
Reading materials / references
| Anchor | ||||
|---|---|---|---|---|
|
Related JIRA issues
- CLONE - Foreign characters broken in group names.
- UTF-8 encoding in community and collection text
- Special characters in collection license lead to parse error
- Fix configurable browse parameter encoding (XMLUI)
- Scandinavian characters break in license, group names and collection/community metadata
- XMLUI Browse by Author doesn't work for names with special characters (for example: é, è, ö, etc.)
- XMLUI overall UTF-8 encoding is inconsistent and forms do not use UTF-8
- Imporper display of Umlauts / Encoding of messages_de.xml - ID: 2413800