Hello,

I have switched to Sun Java 1.6_26 now (which is essentially the same as the 
thing now called Oracle java) and nothing has changed. 

I think the workaround should be checked in to the main repository as long as 
the bug preventing properly localized messages to be used without compromising 
functionally is not found. My suggestion for a changed message text is as 
follows:

        <message 
key="xmlui.Submission.submit.CCLicenseStep.submit_to_creative_commons">Weiter 
zur Auswahl der Lizenz auf der Website von Creative Commons.</message>

Bye, Christian


Am 03.10.2011 um 00:48 schrieb Christian Voelker:

(…)

> The button label contains an Umlaut in the german version. This Umlaut is 
> properly stored as UTF-8 in the messages_de.xml. Changing the Umlaut in the 
> last Word "auszuwählen" to "auszuwaehlen" resolves the issue. Here comes the 
> offending line without the change:
> 
> <message 
> key="xmlui.Submission.submit.CCLicenseStep.submit_to_creative_commons">Weiter 
> zur Creative Commons Seite, um eine Lizenz auszuwählen.</message>
> 
> I guess it should work with the localized string as Claudia has entered it. 
> Changing the label is only a workaround.
> 
> This is the java version on my Debian server:
> 
> $java -version
> java version "1.6.0_18"
> OpenJDK Runtime Environment (IcedTea6 1.8.7) (6b18-1.8.7-2~squeeze1)
> OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)



------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to