I need a xml library which support document entity or xinclude.
The xml may like this:


<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE doc [
    <!ENTITY data SYSTEM "data.xml">
]>
<root xmlns:xi="http://www.w3.org/2001/XInclude">
    &data;
    <xi:include href="table.xml"/>
</root>

On Wednesday, 1 May 2019 at 13:54:08 UTC, Domain wrote:
> I need a xml library which support document entity or xinclude.
> The xml may like this:
>
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE doc [
>     <!ENTITY data SYSTEM "data.xml">
> ]>
> <root xmlns:xi="http://www.w3.org/2001/XInclude">
>     &data;
>     <xi:include href="table.xml"/>
> </root>

Have you looked at this?

https://github.com/jmdavis/dxml

On Wednesday, 1 May 2019 at 13:57:04 UTC, bachmeier wrote:
> On Wednesday, 1 May 2019 at 13:54:08 UTC, Domain wrote:
>> I need a xml library which support document entity or xinclude.
>> The xml may like this:
>>
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <!DOCTYPE doc [
>>     <!ENTITY data SYSTEM "data.xml">
>> ]>
>> <root xmlns:xi="http://www.w3.org/2001/XInclude">
>>     &data;
>>     <xi:include href="table.xml"/>
>> </root>
>
> Have you looked at this?
>
> https://github.com/jmdavis/dxml

Yes, but I don't think dxml support these features.

On 02/05/2019 2:04 AM, Domain wrote:
> On Wednesday, 1 May 2019 at 13:57:04 UTC, bachmeier wrote:
>> On Wednesday, 1 May 2019 at 13:54:08 UTC, Domain wrote:
>>> I need a xml library which support document entity or xinclude.
>>> The xml may like this:
>>>
>>>
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <!DOCTYPE doc [
>>>     <!ENTITY data SYSTEM "data.xml">
>>> ]>
>>> <root xmlns:xi="http://www.w3.org/2001/XInclude">
>>>     &data;
>>>     <xi:include href="table.xml"/>
>>> </root>
>>
>> Have you looked at this?
>>
>> https://github.com/jmdavis/dxml
> 
> Yes, but I don't think dxml support these features.

It does not. Those features come under the big bad guys feature list.

Gonna have to go to C for it.

On Thu, 2019-05-02 at 02:11 +1200, rikki cattermole via Digitalmars-d-
learn wrote:
[…]
> 
> It does not. Those features come under the big bad guys feature list.
> 
> Gonna have to go to C for it.

Surely that means you can use Python, Rust, C++, or D rather than having to descend to using C?

libxml2 is definitely usable from Python, it must be usable from D. Of course, I am assuming libxml2 has the facilities required.

-- 
Russel.
===========================================
Dr Russel Winder      t: +44 20 7585 2200
41 Buckmaster Road    m: +44 7770 465 077
London SW11 1EN, UK   w: www.russel.org.uk

On 03/05/2019 3:36 AM, Russel Winder wrote:
> On Thu, 2019-05-02 at 02:11 +1200, rikki cattermole via Digitalmars-d-
> learn wrote:
> […]
>>
>> It does not. Those features come under the big bad guys feature list.
>>
>> Gonna have to go to C for it.
> 
> Surely that means you can use Python, Rust, C++, or D rather than
> having to descend to using C?
> 
> libxml2 is definitely usable from Python, it must be usable from D. Of
> course, I am assuming libxml2 has the facilities required.

libxml2 is precisely what I meant.

We just don't have the libraries written in D at this point.

On Fri, 2019-05-03 at 03:50 +1200, rikki cattermole via Digitalmars-d- learn wrote:
> On 03/05/2019 3:36 AM, Russel Winder wrote:
> > 
[…]
> > libxml2 is definitely usable from Python, it must be usable from D.
> > Of
> > course, I am assuming libxml2 has the facilities required.
> 
> libxml2 is precisely what I meant.
> 
> We just don't have the libraries written in D at this point.

There are situations where you create a binding in preference to writing something from scratch. cf. gtk, gstreamer, etc. so why not libxml2?

-- 
Russel.
===========================================
Dr Russel Winder      t: +44 20 7585 2200
41 Buckmaster Road    m: +44 7770 465 077
London SW11 1EN, UK   w: www.russel.org.uk

On Thu, May 02, 2019 at 05:23:29PM +0100, Russel Winder via Digitalmars-d-learn wrote: [...]
> There are situations where you create a binding in preference to writing something from scratch. cf. gtk, gstreamer, etc. so why not libxml2?
[...]

No particular reason, except nobody has taken up the task yet. Would you?


T

-- 
Once bitten, twice cry...

On Thursday, 2 May 2019 at 15:50:53 UTC, rikki cattermole wrote:
> On 03/05/2019 3:36 AM, Russel Winder wrote:
>> On Thu, 2019-05-02 at 02:11 +1200, rikki cattermole via Digitalmars-d-
>> learn wrote:
>> […]
>>>
>>> It does not. Those features come under the big bad guys feature list.
>>>
>>> Gonna have to go to C for it.
>> 
>> Surely that means you can use Python, Rust, C++, or D rather than
>> having to descend to using C?
>> 
>> libxml2 is definitely usable from Python, it must be usable from D. Of
>> course, I am assuming libxml2 has the facilities required.
>
> libxml2 is precisely what I meant.
>
> We just don't have the libraries written in D at this point.

Apparently, bindings to libxml2 existed back in 2008. http://www.dsource.org/projects/bcd/

Bastiaan

On 03/05/2019 4:23 AM, Russel Winder wrote:
> On Fri, 2019-05-03 at 03:50 +1200, rikki cattermole via Digitalmars-d-
> learn wrote:
>> On 03/05/2019 3:36 AM, Russel Winder wrote:
>>>
> […]
>>> libxml2 is definitely usable from Python, it must be usable from D.
>>> Of
>>> course, I am assuming libxml2 has the facilities required.
>>
>> libxml2 is precisely what I meant.
>>
>> We just don't have the libraries written in D at this point.
> 
> There are situations where you create a binding in preference to
> writing something from scratch. cf. gtk, gstreamer, etc. so why not
> libxml2?

I am suggesting a binding. I think we have our wires crossed on this.