[Solved] German Umlaute

2004-09-19 Thread Philipp Roethl
Thanks to all for your help. I finally found the problem: one of the tiles
had set its encoding to UTF-8 *argh*. After I removed that, everything
worked perfect.

Philipp

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Re[2]: German Umlaute

2004-09-17 Thread Martin_Schaefer

Since you see to experience your problem in request processing, may be
set the encoding with the VM: -Dfile.encoding="ISO-8859-1" or UTF-8 if
you like. Also the locale of your operating system might play a role.
If  its a UNIX/Linux box, do you have the german locale installed?

Regards
Martin

Carl-Eric Menzel <[EMAIL PROTECTED]> schrieb am 17.09.2004,
09:38:30:
> Christoph Kutzinski wrote:
> 
> > ISO-8859-1 should be no problem since it contains all german umlauts.
> 
> True. But I have standardized on UTF-8 for all text output in my
> applications, since I sometimes also have to deal with cyrillic stuff,
> and I don't want to adjust my encodings and the input filter all the
> time. Going directly to UTF-8 solves all that. Is there any good
> reason not to use UTF-8 by default?
> 
> -- 
> Carl-Eric Menzel * OpenPGP KeyID 808F4A8E * Encrypted Messages Preferred
> "Der Beginn aller Wissenschaften ist das Erstaunen, daß die Dinge   
>  sind, wie sie sind."  - Aristoteles
-- 
Martin Schaefer
NAXOS Software Solutions GmbH i.G.
Herrenstr. 1
69502 Hemsbach
Germany
 
Phone:+49 (0) 6201 49298-2
Mobile: +49 (0) 172 6269246
Fax: +49 (0) 6201 49298-1
Mail: [EMAIL PROTECTED]

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: German Umlaute

2004-09-17 Thread Christoph Kutzinski
Carl-Eric Menzel wrote:
Christoph Kutzinski wrote:

ISO-8859-1 should be no problem since it contains all german umlauts.

True. But I have standardized on UTF-8 for all text output in my
applications, since I sometimes also have to deal with cyrillic stuff,
and I don't want to adjust my encodings and the input filter all the
time. Going directly to UTF-8 solves all that. Is there any good
reason not to use UTF-8 by default?
AFAIK not.
Maybe there are still some very old browsers around which doesn#t 
support UTF-8.

In our case we have a DB in which all texts are stored as ISO-8859-1, so 
it is easier for us to display the pages in ISO-8859-1, too.

So generally there are only legacy reasons not to use UTF-8

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re[2]: German Umlaute

2004-09-17 Thread Carl-Eric Menzel
Christoph Kutzinski wrote:

> ISO-8859-1 should be no problem since it contains all german umlauts.

True. But I have standardized on UTF-8 for all text output in my
applications, since I sometimes also have to deal with cyrillic stuff,
and I don't want to adjust my encodings and the input filter all the
time. Going directly to UTF-8 solves all that. Is there any good
reason not to use UTF-8 by default?

-- 
Carl-Eric Menzel * OpenPGP KeyID 808F4A8E * Encrypted Messages Preferred
"Der Beginn aller Wissenschaften ist das Erstaunen, daß die Dinge   
 sind, wie sie sind."  - Aristoteles


Re: German Umlaute

2004-09-17 Thread Christoph Kutzinski
Carl-Eric Menzel wrote:
Hi,

I.m currently facing a weired problem.

I use a form to provide a search function. When I do not use any special
character in this form everything is fine. As soon as I enter e.g. "Rö" the
corresponding form value is set to "Rö" If an umlaut appears in the search
result it is display correctly. So, the problem seems to occur only in the
request.

What browser are you using? I had the same problem, and I more or less
solved it by outputting only UTF-8 pages, with the proper header set.
This causes most browsers to respond in UTF-8. The default encoding
that the servlet classes use is ISO-8859-1, however, so I also use a
filter to force the servlet to treat the incoming request as UTF-8. So
far this has worked nicely. With Struts 1.2 you can now also use the
acceptCharset attribute of the  tag. I don't know how well
this is supported by the current crop of browsers, but it should give
them another hint what you want them to do.
ISO-8859-1 should be no problem since it contains all german umlauts.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: German Umlaute

2004-09-16 Thread Henrique VIECILI
I don´t think it worth the effort but you can encode the string in base64 and it will 
work for sure!!

Henrique Viecili
  - Original Message - 
  From: Philipp Roethl 
  To: [EMAIL PROTECTED] 
  Sent: Thursday, September 16, 2004 5:01 PM
  Subject: German Umlaute


  Hi,

  I.m currently facing a weired problem.

  I use a form to provide a search function. When I do not use any special
  character in this form everything is fine. As soon as I enter e.g. "Rö" the
  corresponding form value is set to "Rö" If an umlaut appears in the search
  result it is display correctly. So, the problem seems to occur only in the
  request.

  I've search through the mailing list archive and implemented an "Encoding
  Filter" as described here:
  http://www.javaworld.com/javaworld/jw-05-2004/jw-0524-i18n_p.html. I've
  tried to use UTF-8 as well as ISO-8859-1 but nothing helped.

  Does anybody have any hints?

  TIA,
  Philipp


  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]


Re: German Umlaute

2004-09-16 Thread Carl-Eric Menzel
> Hi,

> I.m currently facing a weired problem.

> I use a form to provide a search function. When I do not use any special
> character in this form everything is fine. As soon as I enter e.g. "Rö" the
> corresponding form value is set to "Rö" If an umlaut appears in the search
> result it is display correctly. So, the problem seems to occur only in the
> request.

What browser are you using? I had the same problem, and I more or less
solved it by outputting only UTF-8 pages, with the proper header set.
This causes most browsers to respond in UTF-8. The default encoding
that the servlet classes use is ISO-8859-1, however, so I also use a
filter to force the servlet to treat the incoming request as UTF-8. So
far this has worked nicely. With Struts 1.2 you can now also use the
acceptCharset attribute of the  tag. I don't know how well
this is supported by the current crop of browsers, but it should give
them another hint what you want them to do.

HTH
Carl-Eric
-- 
Carl-Eric Menzel * OpenPGP KeyID 808F4A8E * Encrypted Messages Preferred
"It is seldom that liberty of any kind is lost all at once."
- David Hume


German Umlaute

2004-09-16 Thread Philipp Roethl
Hi,

I.m currently facing a weired problem.

I use a form to provide a search function. When I do not use any special
character in this form everything is fine. As soon as I enter e.g. "Rö" the
corresponding form value is set to "Rö" If an umlaut appears in the search
result it is display correctly. So, the problem seems to occur only in the
request.

I've search through the mailing list archive and implemented an "Encoding
Filter" as described here:
http://www.javaworld.com/javaworld/jw-05-2004/jw-0524-i18n_p.html. I've
tried to use UTF-8 as well as ISO-8859-1 but nothing helped.

Does anybody have any hints?

TIA,
Philipp


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Special Characters (german Umlaute)

2004-05-04 Thread Kransen, J.
This is something I've been wondering: is it absolutely necessary to convert
text files using this tool? I use UTF-8 encoding for the
ApplicationResources.properties_?? files, I indicate that UTF-8 is the
encoding of my web pages, with the tag 



and it works just fine. Is this just coincidence and should I not count on
this to work anytime, anywhere?

On my website under
http://jeroen.kransen.nl:8080/belbin/form/introductie.jsp 
I'm making a small personality test and use different languages, it's still
under construction and only complete in NL and EN so far, but the characters
such as Umlauts (or the NL trema's which is basically the same thing) and
the Cyrillic alphabet work on all browsers I tried so far. 
This way we can just edit the texts of any character set as we do with plain
ASCII and don't have to perform the additional step. Generally the tendency
seems to be that using different character encodings is becoming more and
more transparent.

> -Oorspronkelijk bericht-
> Van: Ralf Schneider [mailto:[EMAIL PROTECTED]
> Verzonden: dinsdag 4 mei 2004 10:34
> Aan: Struts Users Mailing List
> Onderwerp: Re: Special Characters (german Umlaute)
> 
> Am Montag, 3. Mai 2004 21:57 schrieb Ruth, Brice:
> > You can use the native2ascii application that is bundled with your JDK
> to
> > automatically convert your native-encoded file with umlauts to \u
> > format encodings.
> 
> Thanks, works fine!
> 
> The only thing I have to manage now is to automate this task within
> Eclipse
> 3.0M8. At the moment, there is no build.xml file in my project. So,
> Eclipse
> must somehow know what to do with the resource files as they are copied
> automatically from the source to the classes directory when they are
> saved.
> How can I tell Eclipe not only to copy them but to run native2ascii?
> 
> Ralf.
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Special Characters (german Umlaute)

2004-05-04 Thread Ralf Schneider
Am Montag, 3. Mai 2004 21:57 schrieb Ruth, Brice:
> You can use the native2ascii application that is bundled with your JDK to
> automatically convert your native-encoded file with umlauts to \u
> format encodings.

Thanks, works fine! 

The only thing I have to manage now is to automate this task within Eclipse 
3.0M8. At the moment, there is no build.xml file in my project. So, Eclipse 
must somehow know what to do with the resource files as they are copied 
automatically from the source to the classes directory when they are saved. 
How can I tell Eclipe not only to copy them but to run native2ascii?

Ralf.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Special Characters (german Umlaute)

2004-05-03 Thread Ruth, Brice
You can use the native2ascii application that is bundled with your JDK to 
automatically convert your native-encoded file with umlauts to \u format encodings.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Monday, May 03, 2004 2:50 PM
To: Struts Users Mailing List
Subject: Re: Special Characters (german Umlaute)


Hi Ralf,

use unicode in the resource bundle.

\u00c4 = Ä
\u00e4 = ä 

and so on.

A complete chart is available here:

http://www.unicode.org/charts/PDF/U0080.pdf

greetings 
mattes

-- 
Mattes Balser | [EMAIL PROTECTED]
High-End Services GmbH | www.nervmich.net



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Special Characters (german Umlaute)

2004-05-03 Thread mattes
Hi Ralf,

use unicode in the resource bundle.

\u00c4 = Ä
\u00e4 = ä 

and so on.

A complete chart is available here:

http://www.unicode.org/charts/PDF/U0080.pdf

greetings 
mattes

-- 
Mattes Balser | [EMAIL PROTECTED]
High-End Services GmbH | www.nervmich.net



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Special Characters (german Umlaute)

2004-05-03 Thread Ralf Schneider
Hi,

my web application loads german strings from a resource bundle. Unfortunately, 
the special characters (german Umlaute like Ã, Ã, Ã) are displayed 
incorrectly if they come from the resource bundle. When I write them directly 
into the HTML code they are displayed correctly.

At the beginning of my JSP file I have this line:
<%@ page contentType="text/html; charset=UTF-8" %>

And the HTML block is opened with this line:


What do I have to change to get the special characters displayed as they were 
written in the resource bundle?

Ralf.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]