Luís Duarte

Hello, Thanks for the issue. The XsdParserCore wasn't planned to be extended. Currently I don't have much free time to do it so I'll take it in consideration in the...

Hello, The only way that I'm seeing to do that is to "pre-parse" all the required files before parsing the "original" file, because otherwise during the parsing either the file...

Hello, can you provide me the XML that you are having issues parsing in Windows so I can test it?

Thanks for the investigation, I'll try to investigate it further on future releases of the library to make it work in both MacOs and Windows.

It makes sense. We change the default behavior to improve security and keep an option for users which rather have the performance improvement than the security added by content escaping.

We currently use a very simple method, based on the calls of the dynamic method. We store cache as blocks between dynamic invocations, which have an index based on their...

> @lcduarte What do you think about it? I think the only way to make everyone happy is to add an option on `DynamicHtml.view` to receive an optional parameter `Supplier`....

Looks like the right choice. We keep the default value as it was until this change and give the possibility of customizing it from now on.

Hello Simon, Thanks for the issue and for using the library. Also thanks for the investigation, while I agree that the file paths are a mess in the library I'm...

I might be missing something but that replace alone doesn't seem to solve the problem with your sample xsd. I'm on windows if that makes any difference. I've created a...