[reportlab-users] pyRXP and processing instructions

[Robin Becker]

.
....
>> Robin, while looking at it next, can you find out the feasibility
>> of exposing namespace support?  I suppose there are a gazillion
>> things one could do, but the one which interests me most is
>> "parse the tree for all tags with namespace prefix x, and leave
>> all others tags as unparsed text..."
>
>But where to stick them? I guess the obvious choice is that 4th
>tuple element for the elements namespace. But for attributes, it
>would mean changing the {'attribute': 'value'} dictionary to
>something wierder (like {('namespace','attribute': 'value')} ?)
>

I don't follow this exactly, but then I'm not a fan of xml too much
vagueness. We're suggesting namespaces why do we need extra support for
the name of a tag/attribute? Why wouldn't we write the above as

        {'namespace:attribute': 'value'}?

Why would <bingo:mytag> ....</bingo:mytag> map to 
        ('bingo:mytag',.........)

>Currently 2.1.3, 'cause thats what Zope forces me to use on the
>production boxes (although I'm thinking seriously of going to 2.2.2
>anyway and damn the consequences...)
>

-- 
Robin Becker