Hello, Am 29.04.2012 um 17:01 schrieb Christian Völker:
> just found this:
>
> dspace/config/modules/curate.cfg
>
> needs to be stored with ISO-Latin-1 Encoding to display properly,
> as opposed to all other files which are stored as UTF-8 nowadays.
>
> You may try to localize ui.tasknames which requires the use of
> umlauts in german language to understand what I mean. You cant
> write the words as they should be displayed just like you do in
> messages.xml. The get displayed as two weird glyphs. You cant
> use UTF-8 hex encoding which gets displayed as is where it
> should be interpreted. I finally found storing it using the
> encoding mentioned above works.
>
> This is on Debian, Java 1.6, Tomcat 6 if that would be of any
> relevance.
I just found that this does not work either.
As a short workaround for the lengthy and errorprone buildprocess
introduced with maven, I tested by placing the reencoded file
directly into the directory where the server runs from. At the
same time, I changed the file in the source directory (with
placeholders like taskqueue.dir = ${dspace.dir}/ctqueues not
yet replaced).
curate.cfg.iso-latin-1
Description: Binary data
After running another cycle of mvn package and ant update I found that the display was broken again, be it in a slightly different manner. ant update worked properly, however mvn package did not copy the file to the target directory as is, but change the encoding at the same time. No stop, it did not just tinker with the encoding, it replaced all Umlauts wit a "Replacement Character" as of Code page "Halfwidth and Fullwidth Forms", Unicode Codeposition U+FFFD, Hex Notation ef bf bd. This is displayed as a lower Letter i with two dots on it, followed by spanish inversed Question mark and a 1/2 sign in the browser and as a white Question mark in a diamond sign in UTF-8 compliant text editors such as vi.
curate.cfg.mvn
Description: Binary data
Apache Maven 2.2.1 (rdebian-4) Java version: 1.6.0_26 Java home: /usr/lib/jvm/java-6-sun-1.6.0.26/jre I intentionally switched back to Maven 2.2 after running in the problems documented with Maven 3 last fall when working on the 1.7 Update. I am not willing to dig into configuring mvn to not touch file encodings. If that is a required step and cannot be done within pom.xml project files I ask you to document how it has to be done in the Installation prerequisite software section. mvn not changing files in unexpected ways would strenghten confidence, though it might not be in line with the way this tool ist meant to behave (id est strenghten confidence). Finding a way to localize DSpace modules without changing config files (and thus tieing the interface to one language) remains a welcome change to be seen in the future. Bye, Christian
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
