We always use UTF-8.
We usually add a mandatory comment that contains non-ASCII characters at the
top of the file, and a unit test that verifies it. It's too common that some
developer screws up the file by opening it with wrong encoding.
Example:
*.properties:
----------------
# DO NOT REMOVE: räksmörgås
PropertiesEncodingTest.java
------------------------------------
foreach *.properties:
assertFirstLineEquals("# DO NOT REMOVE: räksmörgås")
This has save our ass many times :)
Olle Hallin
Senior Java Developer and Architect
olle.hal...@crisp.se
www.crisp.se
2009/10/21 Ulrich Stärk <u...@spielviel.de>
>
>
> Am 21.10.2009 10:02 schrieb Stephan Windmüller:
>
> Note: The issues I have is that eclipse keeps insisting that my
>>> .properties
>>> files are ISO-8859 and I have to manually switch encoding
>>> for each new property file i create or copy. Besides that's everyting
>>> works
>>> fine ....
>>>
>>
> Forgot to mention: You can change the default encoding for a file type in
> Eclipse. Under Preferences go to General -> Content Types, expand Text and
> choose Java properties file. At the bottom of the form you can now input
> your desired default encoding
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
