saxxonpike / nextlevelseven Goto Github PK

I'm evaluating your library for performance and wow it's good. One issue I've encountered however is handling of escape characters. For instance \T\ should evaluate to &. I was thinking this should happen in the converter but I don't see how yet. Can you point me in the right direction? Or if you don't handle this, could you offer a suggestion on the best way to do so?

Here's a link to some of the accepted escapes https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=EHL72_escape_sequences It doesn't appear as if there are too many.

Hi, it would be great if Nuget package is published.

Thanks

Hey,

Question - I'd like to add NetStandard support for your library. I've already done all the work to add multi-targeting to your library. Would you be ok with that pull request? The actual change is simple, I did have to reconfigure the test project but all tests are passing in both full .NET Framework and .NET Core now.

Now that we're targeting .NET Standard 2.0, it will greatly simplify things if we also bump the .NET Framework to at least 4.6.1, according to Microsoft:
https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/cross-platform-targeting

Thoughts?