Under Tapestry5 now, there's a filter that, effectively, executes native2ascii on the fly. Actually, what it does is read the characters into a buffer, replacing any unicode characters with a unicode escape. Then the buffer is converted to an InputStream and passed to Properties.load(). The end result is the same as running native2ascii without the extra step.
On Tue, Aug 12, 2008 at 3:33 PM, Igor Drobiazko <[EMAIL PROTECTED]> wrote: > Well, I'm aware of the purpose of native2ascii. The question is why Tap5's > resource bundles are not converted by native2ascii. > Is there any reason? If not I would like to convert them. > > On Tue, Aug 12, 2008 at 12:49 PM, Renat Zubairov > <[EMAIL PROTECTED]>wrote: > >> 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 >> > > > > -- > Best regards, > > Igor Drobiazko > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
