Tuesday, February 13, 2007, 8:02:13 PM, Graeme wrote:
GG> On 2/13/07, Michael Van Canneyt <[EMAIL PROTECTED]> wrote:
>> > Isn't such a check built into the xml or dom units so we could rather use
>> > that?
>> > A isEmptyElement() would be a handy function. :-)
>>
>> I'm sure it would be, remains the matter of having a correct definition for
>> this function :-)
GG> True, but then we would at least have only one place to fix when we
GG> finally get a definition for a empty element. Now it would be
GG> scattered in fpdoc, makeskel, lazde, etc...
This issue is a result of the improvements that I had made to xml parser.
I tried to stick to official W3 specifications which state that the
parser must report all whitespace to application, and it is up to
application to decide whether this whitespace is meaningful.
Probably the missing function is TDOMText.IsElementContentWhitespace
(DOM level 3). I hope to release it soon with the next portion of updates.
--
Best regards,
Sergei
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
