Garret Wilson

Feel free to close this ticket as "will not implement". I hope you found it useful or at least interesting, though. Cheers.

> If you were to publish that DurationConverter, I could point to it from the picocli user manual... The [`Durations.parseUserInput()`](https://github.com/globalmentor/globalmentor-base/blob/master/core/src/main/java/com/globalmentor/time/Durations.java) method is now released and available on Maven Central as...

@remkop I think that provides the functionality needed to hook into type conversion for all enums types. One potential problem is that it isn't very flexible. That is if someone...

One other potential confusion (not to deter you; just to mention it) is that you'll still have the per-type registration system, and if someone registers an overriding `ITypeConverterFactory` it could...

> Overall, I am having some second thoughts about this whole endeavor in the sense that it feels like a lot of infrastructure for a relatively small benefit. Whatever you...

Interestingly I can create a workaround simply by adding this method inside the test itself! ```java public static Matcher

While this bug is being fixed, does anyone have a workaround that would allow me to force the `W3CDom` class to put the DOM `Document` elements into the correct namespace?...

At least part of the problem seems to be here in `W3CDom`: ```java Element el = namespace == null && tagName.contains(":") ? doc.createElementNS("", tagName) : // doesn't have a real...

Unfortunately the following attempt at a workaround doesn't work. ☹️ ```java … jsoupDocument.attr("xmlns", "http://www.w3.org/1999/xhtml"); org.w3c.dom.Document domDocument = new W3CDom().fromJsoup(jsoupDocument); … ```

Ah, here's a workaround. The workaround above didn't work because even though jsoup considers the `org.jsoup.nodes.Document` an `org.jsoup.nodes.Element` (which is confusing because that's different from the W3C model), `W3CDom` skips...