libdom.git - Document Object Model library

	Commit message (Collapse)	Author	Age	Files	Lines
*	Rationalise dom_string (some consideration is required as to what happens ↵	John Mark Bell	2009-03-03	1	-38/+0
\| \| \| \| \| \| \| \| \|	wrt interning -- lwc_strings should probably be used) Purge charset handling -- a) documents are always converted to utf-8 b) use parserutils for utf-8 handling Fix Hubbub binding to compile. svn path=/trunk/dom/; revision=6682
*	DOM Strings are now capable of containing either UTF-8 or UTF-16 encoded data.	John Mark Bell	2007-09-30	1	-0/+38
	The charset used for strings within a document is specified at document creation time. Whilst it is possible to mix charsets within a document, it's not recommended. Things that need fixing: + dom_string_get_data() doesn't return the charset. Better would be to permit the client to request a charset for the data to be returned in. + Interned node name strings will break if the document is UTF-16 (dom_document_create()). In fact, these could quite happily be globals, rather than allocating a set for each document. + Other usage of dom string constructors need checking for sanity + DOM Strings need to gain more utility APIs (such as getting the character length of a string, string concatenation etc). svn path=/trunk/dom/; revision=3614