The trick is that when JVM reads bytes from file it assume some encoding, which is usually taken from the OS environment. Sometimes (most of the times?) environment encoding is the same as encoding used when file creation, then we don't need to use native2ascii staff, however usually it's not a good idea to rely on environment settings therefore native2ascii makes sure that wherever encoding will be used for reading files all non-ascii characters will be properly red.
2008/8/12 Igor Drobiazko <[EMAIL PROTECTED]>: > Hi, > > in Tapestry 4 resource bundles were converted by native2ascii. Recently > added support for locale de_DE is not converted and contains german letters > like ä, ö, ü. > What is the reason for not using native2ascii? > > -- > Best regards, > > Igor Drobiazko > -- Best regards, Renat Zubairov
