I found this thread after having the same problem - setting content-type
to utf-8 in my HTML's http-equiv headers caused an error in IE (doesn't
affect firefox): it expects '/' character somewhere around line #25246 (if
i remember correctly) of qooxdoo.js (if you need better details just ask).
So anyways, calling qooxdoo.js like you suggested fixes the problem,
thanks Sebastian.
If that's the only issue caused by the hard-coded encoding, perhaps it
should be common practice to call qooxdoo.js in this fashion everywhere in
the docs and examples so that people aren't confused when renderer is
released. Otherwise, perhaps there is a need for a better solution?
Izaak
On Wed, 04 Jan 2006 06:01:31 -0500, Sebastian Werner
<[EMAIL PROTECTED]> wrote:
could you please try it again and include the qooxdoo.js with the
following line:
<script type="text/javascript" charset="ISO-8859-15"
src="qooxdoo.js"></script>
Please tell us if this helps in your case. Thanks.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
