Re: Witango-Talk: support for @DOM encoding

[Robert Garcia]

I agree, and I consider witango 5.0 more the early days. But it isn't the early days anymore. It is virtually impossible to ignore text encoding anymore. The fact that 5.5 includes XSLT, is great, at least it allows me to output xml with a declaration that matches the encoding, cuz everything else I use will honor the declaration, and ingest with the specified encoding, and things work. Even though the rest (most) of the xml world is defaulting to UTF-8, I feel like I can get by without too many hacks. With 5.0, it was almost all a hack. I just rebuilt my templates for my devs to rebuild our webservices, and the amount of code now, and simplicity is wonderful. The only thing that I consider a bit of a hack, is the piece where i have to remove the declaration before inserting any xml into a dom. That said, there seems to be serious gaps on the parsing side. For instance, if I get xml that is coded in UTF-8, it should work most of the time, but if there are any special chars in the xml, witango may ingest it, but text will get messed up in the process. And there is NO way I can see to fix that in witango. You can't use xslt to transform, cuz XSLT only works on a dom, so it must be ingested first. The only solution I see for proper ingestion into witango, would be an external action or something, that will ingest the xml, respecting the declaration, converting the xml/text to ISO-8859-1 and then passing the newly converted xml back into witango. It would be great if Witango support could chime in and verify this, if so, I would be happy to write an external action to do this and provide to the community. But I don't want to do it, if there is another hidden tag or something that solves this. --  Robert Garcia President - BigHead Technology VP Application Development - eventpix.com 13653 West Park Dr Magalia, Ca 95954 ph: 530.645.4040 x222 fax: 530.645.4040 [EMAIL PROTECTED] - [EMAIL PROTECTED] http://bighead.net/ - http://eventpix.com/ On Sep 20, 2005, at 6:28 AM, Scott Cadillac wrote: Hi Robert, when you add the declaration with a dominsert, or  it is already in the text, witango seems to destroy or remove  it and disregard. I discovered through lots of trial-and-error that some XML parsers have a habit of consuming the instructions and not returning them on output. This problem was not limited to Tango/Witango. This appears to be a behavior issue not clearly addressed in the early days of XML and DOM usage.  Newer parsers honor the instructions and make them available again on output. ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf