[Thinlet-development] Problems with enconding, maxlength and DTD
Brought to you by:
bajzat
From: Michael N. S. <mis...@ho...> - 2004-06-11 05:16:45
|
Hi folks, Besides some "comestic" changes we did for our project - enter triggers action for any button, the cursor is drawn with 2 pixels instead of 1 etc. -, there is at least one issue with Thinlet right now and one feature I'd like to implement in the core. It's not possible to show Latin characters properly if they are part of a XML document - and I'm pretty sure it aplies to lots of other charsets as well -, since using a Reader without specifying an encoding uses the default platform encoding, which may not be appropriate (that's the case for most Linux distributions, for example). The right behaviour would be to use the value of the xml encoding property when building the Reader. This attribute is ignored right now and processing it before reading the rest of the document isn't trivial. I intend to provide support for that if no one has a patch already. Apart from that, a key missing feature for widgets that accept text entry is a maxlength attribute. Has anyone done it? Would it be ok to include it in the main Thinlet? A final issue: has the java.net DTD been updated to support the last changes (resizable/sortable column headers, etc.)? If it's not even ready, I'd be glad to update it, although I don't have commit permissions in java.net. Regards, Michael Nascimento Santos JSR 207 Expert Group Member http://www.javablogs.com.br/blogs/page/soujavamisterm http://today.java.net/pub/au/80 Sun Certified Programmer for the Java 2 Platform Sun Certified Mobile Application Developer Sun Certified Web Component Developer for J2EE Moderador SouJava - http://www.soujava.org.br |