Re: ConcreteElement output(OutputStream) does not use codeset?
robert burrell donkin <[email protected]> Mon, 17 Mar 2003 19:17:31 +0000
| Newsgroups | gmane.comp.jakarta.ecs.user |
|---|---|
| Message-ID | <[email protected]> |
hi Abre i'm glad that you've found ECS useful. the attachment didn't seem to make it. could you try again after zipping or tarring? it would also make it a lot easier for me to evaluate your patch if you could supply a CVS diff -u (against CVS HEAD) rather than the modified source. TIA - robert On Friday, March 14, 2003, at 02:38 PM, Abre Chase wrote: > Greeting to the list. This is my first post, so please forgive me if I > ask an ignorant question. I've browsed the archives and found no posts > addressing this issue. > > I'm working on a project, which uses ECS to a great extent. We've > recently ported our database to use the UTF-8 character set. I noticed > that attribute values are getting mangled somewhere in ECS - and I > believe I've located the cause. In GenericElement, the > output(OutputStream) method uses the codeset when calling getBytes() on > String values. However, ConcreteElement does not use the codeset when > using the getBytes() method. Is there a good reason for this? > > I've modified the ConcreteElement source and attached it to this post. > Will my patch cause other problems, or is it safe? > > Thanks in advance for any advice...and thanks providing this library to > the community. > > - Abre > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected]