On 06/07/2018 01:55 PM, Nick Wellnhofer wrote:
> On 07/06/2018 00:00, Stefan Sauer wrote:
Another idea is to stop loading external DTDs for XIncludes without an
XPointer expression. This would still change the behavior for some
users but it's much less likely to cause problems.
>> ch
On 08/06/2018 03:45, Eric S. Eberhard wrote:
Some very simple things to do: 1) put the DTD hosts into the /etc/hosts file
(or another if you like and substitute an IP) 2) set /etc/resolv.conf to
first look in the hosts file (before DNS)
The discussion is not about caching DTDs loaded over
On 07/06/2018 00:00, Stefan Sauer wrote:
Another idea is to stop loading external DTDs for XIncludes without an
XPointer expression. This would still change the behavior for some
users but it's much less likely to cause problems.
change the behaviour, as in we would not catch validation errors?
On 05/17/2018 04:18 PM, Nick Wellnhofer wrote:
> On 16/05/2018 21:51, Stefan Sauer wrote:
>> So one solution could be another flag to enable this?
>
> Yes, but it would be rather ugly.
>
>> Thanks, reading the code. Need to figure where we could cache external
>> subsets and what a suitable keys is
On 06/07/2018 12:54 AM, Eric S. Eberhard wrote:
> I know I am the oddball here but -- why use DTDs at all?
I gave reasons above. I am working on a tool. How people using the tool
is not under my control. Maybe we can focus on the opportunity to
improve libxml2 a bit here.
> I supply software to
On 05/17/2018 06:01 PM, Stefan Sauer wrote:
> On 05/17/2018 04:18 PM, Nick Wellnhofer wrote:
>> On 16/05/2018 21:51, Stefan Sauer wrote:
>>> So one solution could be another flag to enable this?
>> Yes, but it would be rather ugly.
> In which sense? I guess because it is something that noone should
On 05/17/2018 04:18 PM, Nick Wellnhofer wrote:
> On 16/05/2018 21:51, Stefan Sauer wrote:
>> So one solution could be another flag to enable this?
>
> Yes, but it would be rather ugly.
In which sense? I guess because it is something that noone should need
to know about or have to care about?
>
>> T
On 16/05/2018 21:51, Stefan Sauer wrote:
So one solution could be another flag to enable this?
Yes, but it would be rather ugly.
Thanks, reading the code. Need to figure where we could cache external
subsets and what a suitable keys is (ExternalID ?).
Note that I'm currently not planning to
On 05/17/2018 01:40 AM, Eric S. Eberhard wrote:
> So again, the first time, put it on your machine and use an IP (or
> localhost if you can which goes straight to the TCP/IP stack -- never
> goes to the network). Also, you can do one other tacky thing I do ...
> sometimes when I see things like th
On 05/16/2018 12:41 AM, Nick Wellnhofer wrote:
> On May 15, 2018, at 21:56 , Stefan Sauer wrote:
>> On 05/15/2018 08:40 PM, Stefan Sauer wrote:
>>> On 05/15/2018 12:42 PM, Nick Wellnhofer wrote:
Can you try to change the line to
xmlCtxtUseOptions(pctxt, ctxt->parseFlags);
>
On May 15, 2018, at 21:56 , Stefan Sauer wrote:
>
> On 05/15/2018 08:40 PM, Stefan Sauer wrote:
>> On 05/15/2018 12:42 PM, Nick Wellnhofer wrote:
>>> Can you try to change the line to
>>>
>>> xmlCtxtUseOptions(pctxt, ctxt->parseFlags);
>>>
>>> and see if it helps?
>>>
>> It does not help.
On 05/15/2018 08:40 PM, Stefan Sauer wrote:
> On 05/15/2018 12:42 PM, Nick Wellnhofer wrote:
>> On 14/05/2018 21:48, Stefan Sauer wrote:
>>> This part looks suspicious:
>>>
>>> |--22.98%--0xc2160
>>> | xmlFreeDoc
>>> | |
>>>
On 05/15/2018 12:42 PM, Nick Wellnhofer wrote:
> On 14/05/2018 21:48, Stefan Sauer wrote:
>> This part looks suspicious:
>>
>> |--22.98%--0xc2160
>> | xmlFreeDoc
>> | |
>> | --22.42%--xmlFreeDtd
>
>> Can I t
On 14/05/2018 21:48, Stefan Sauer wrote:
This part looks suspicious:
|--22.98%--0xc2160
| xmlFreeDoc
| |
| --22.42%--xmlFreeDtd
Can I tell it to not load dtds in the first place? Is it loading the dtd
On 05/14/2018 09:48 PM, Stefan Sauer wrote:
> On 05/14/2018 12:19 PM, Nick Wellnhofer wrote:
>> On 13/05/2018 20:54, Stefan Sauer wrote:
>>> Lets look at some numbers using glib
>>> (https://gitlab.gnome.org/GNOME/glib)
>>>
>>> cd glib/docs/reference/glib
>>> xmllint --timing --xinclude --noout gli
On 05/14/2018 12:19 PM, Nick Wellnhofer wrote:
> On 13/05/2018 20:54, Stefan Sauer wrote:
>> Lets look at some numbers using glib
>> (https://gitlab.gnome.org/GNOME/glib)
>>
>> cd glib/docs/reference/glib
>> xmllint --timing --xinclude --noout glib-docs.xml
>> Parsing took 0 ms
>> Xinclude processi
Seems that the list does not like attachements, so resensing with links
On 05/14/2018 12:19 PM, Nick Wellnhofer wrote:
> On 13/05/2018 20:54, Stefan Sauer wrote:
>> Lets look at some numbers using glib
>> (https://gitlab.gnome.org/GNOME/glib)
>>
>> cd glib/docs/reference/glib
>> xmllint --timing -
On 13/05/2018 20:54, Stefan Sauer wrote:
Lets look at some numbers using glib (https://gitlab.gnome.org/GNOME/glib)
cd glib/docs/reference/glib
xmllint --timing --xinclude --noout glib-docs.xml
Parsing took 0 ms
Xinclude processing took 4560 ms
Freeing took 91 ms
Any idea how I can get more bre
hi,
I am the maintainer of gtk-doc. One biggest complaint I get is the
performance. gtk-doc is scanning sources and combining the extracted
comments with handwritten docbook into a signle docbook document. The
docbook document uses xinclude for its parts. As a next step we were
using the docbook-s
19 matches
Mail list logo
