Re: [Dspace-tech] Antw: Re: DSpace 1.5.1 beta, encoding

2008-09-04 Thread Mika Stenberg
Just noticed that the encoding issues occur also when editing metadata; special (say, scandinavian accented characters), get messed up after updating edited metadata. -Mika Hi Mark, after setting the container-encoding to IS0-8859-1 the display of characters was ok, but still browsing on

Re: [Dspace-tech] Antw: Re: DSpace 1.5.1 beta, encoding

2008-09-01 Thread Claudia Jürgen
Hi Mark, after setting the container-encoding to IS0-8859-1 the display of characters was ok, but still browsing on special characters dis not work . - set the container-encoding in the web.xml to ISO-8859-1 - set the form-encoding for Browse to ISO-8859-1 in

Re: [Dspace-tech] Antw: Re: DSpace 1.5.1 beta, encoding

2008-09-01 Thread Robert Roggenbuck
Hi Mark, Mark Diggory schrieb: On Aug 29, 2008, at 7:17 AM, Michael Steck wrote: [snip] Are email addresses allowed to hold special characters? In the .de Domain it is possible to include umlauts and a lot of other special characters. See http://www.denic.de/en/domains/idns/liste.html .

Re: [Dspace-tech] Antw: Re: DSpace 1.5.1 beta, encoding

2008-09-01 Thread Claudia Jürgen
Hi all, found one more issue with encoding, the jump point in a browse index. See https://eldorado2.uni-dortmund.de/dspace151betaxmlui/browse?type=author you can jump to ä and Jürgen but not to öber, Über Furthermore the counting on browse indices which contain special characters seems too

[Dspace-tech] Antw: Re: DSpace 1.5.1 beta, encoding

2008-08-29 Thread Michael Steck
Hi, i was also trying to fix this encoding problem with the help of http://cocoon.apache.org/2.2/1366_1_1.html, but without success. my conclusion is that - setting the container-encoding in the web.xml to ISO-8859-1 fixes almost all problems, - but 2 bugs remain * simple (or

Re: [Dspace-tech] Antw: Re: DSpace 1.5.1 beta, encoding

2008-08-29 Thread Mark Diggory
On Aug 29, 2008, at 7:17 AM, Michael Steck wrote: Hi, i was also trying to fix this encoding problem with the help of http://cocoon.apache.org/2.2/1366_1_1.html, but without success. my conclusion is that - setting the container-encoding in the web.xml to ISO-8859-1 fixes almost all