axunonb

Is it verified already that we don't follow [the definition Text in the XML specification](http://www.w3.org/TR/xml/#dt-text)? "Control characters" seems to be a too general description?

Fully agree, @binki, thanks. Currently, illegal characters throw e.g. `System.ArgumentException : '\ufffe', hexadecimal value 0xFFFE, is an invalid character.` in `YAXSerializer` ```csharp public string Serialize(object obj) { // System.Xml.Linq.XNode.ToString() return...

@304NotModified Looks like there's a rather simple way to de/serialize `string` fields/properties as `CData` or `Base64`-encoded. I'm considering a `YAXStringEmbeddingAttribute` which allows for `StringEmbedding.None` | `StringEmbedding.CData` | `StringEmbedding.Base64`. What do...

> there should be way to just **remove** the illegal characters like \u0003 Agree. In it's simplest form all values would have to undergo a `RegEx.Replace` or maybe better stripped...

Implementing `YAXTextEmbeddingAttribute` is done. `YAXTextEmbedding.CData` will always strip invalid chars. If this is undesired, the alternative `YAXTextEmbedding.Base64` is there. Will post a new PR after #203 is merged.

Resolved with release [v4.0.0](https://github.com/YAXLib/YAXLib/releases/tag/v4.0.0)

Hey, **very** cool! Must admit I never came across covariance and contravariance before, so I first had to understand what's behind ;-) "multi-state" in `IYAXMultiStateDeserializer` expresses what is called "multi-stage"...

Hm, I still like this...

Hi, this has been a while ago, sorry. We're currently about revitalizing this project, and we're going through open issues. > I'm using VS 2019, and apparently you're 2015 Meanwhile...

To resolve this issue, it looks like 2 things were to be modified: 1. Remove the general test, whether a member can write. Only these members are used in the...