Hi Gary, There haven't been any plans for UTF-32 support. It seems you're the first [1] (and only) one who has asked about it on the project lists.
Is this just an academic question or do you have an actual need for it? I must say I've never seen a UTF-32 encoded document in the wild. In my opinion it's a very inefficient encoding. Always uses 32-bits to represent a character when the largest Unicode code point only requires 21-bits. UTF-8 and UTF-16 only ever use that much space for supplementary characters (i.e. code points greater than U+FFFF). Thanks. [1] http://xerces-j.markmail.org/search/?q=UTF-32 Michael Glavassevich XML Technologies and WAS Development IBM Toronto Lab E-mail: mrgla...@ca.ibm.com E-mail: mrgla...@apache.org Gary Gregory <garydgreg...@gmail.com> wrote on 13/08/2012 01:49:46 PM: > Hi All: > > Any plans to support UTF-32 BOM? > > Currently, if I parse a UTF-32 document I get 'content not expected > in prolog" error. > > Thank you, > Gary > > -- > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org > JUnit in Action, 2nd Ed: http://bit.ly/ECvg0 > Spring Batch in Action: http://bit.ly/bqpbCK > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory
