What would be required to make this happen?

@summychou Thanks, noted, but please see https://golang.org/wiki/NoPlusOne . Can you answer the question I asked above?

@ianlancetaylor https://www.w3.org/TR/xml11/#sec-xml11
changes in xml 1.1

@ianlancetaylor Processing XML 1.1 documents with XML Schema 1.0 processors

Is there any alternative to parse a 1.1 XML document?

Haven't get a change to go through the XML 1.1 spec yet, but the seems to be mainly on extending further Unicode support.

"XML 1.1 improves on some of the short comings of XML 1.0, notably recognizing end of line. There currently exists a misalignment between what XML and Unicode defines as end of line, this affects particularly IBM machines, as well as systems communicating with them .

XML 1.1 also adds 2 new important characters NEL and a line separator. NEL 0x85 is used to mark the end of line and for completeness 0x2028 is used to mark the separation of line, this is extremely helpful in normalizing linefeed in text which plagues XML 1.0."

According to this post:
http://echmondprojects.com/general/tutorials/xml/xml_a/whats-in-xml-1-1/

More reading from the official XML spec:
https://www.w3.org/TR/xml11schema10/

使用的go 1.17 需要对jenkins的xml进行解析 but Jenkins xml version is 1.1 ？How to deal with?

不明白为什么提了问题你们给关了？倒是给个解决的方案啊？说是和这个重复，那这个也都几年了还是没进度！感觉go是只关心核心进展

@zhongsdjn This issue tracker is primarily in English.

This issue is not closed. But as far as I know nobody is working on it. Go is an open source project. Would you like to send in patches for XML 1.1 support? Thanks.

使用的go 1.17 需要对jenkins的xml进行解析 but Jenkins xml version is 1.1 ？How to deal with?

Can you show more detail of Jenkins' xml file as an example?

the error:
xml: unsupported version "1.1"; only version 1.0 is supported

but jenkins config file both xml 1.1
like flow:
<?xml version='1.1' encoding='UTF-8'?>
<hudson.util.DescribableList>
<hudson.node__monitors.ArchitectureMonitor>
false
</hudson.node__monitors.ArchitectureMonitor>
<hudson.node__monitors.ClockMonitor>
false
</hudson.node__monitors.ClockMonitor>
<hudson.node__monitors.DiskSpaceMonitor>
false
1GB
</hudson.node__monitors.DiskSpaceMonitor>
<hudson.node__monitors.SwapSpaceMonitor>
false
</hudson.node__monitors.SwapSpaceMonitor>
<hudson.node__monitors.TemporarySpaceMonitor>
false
1GB
</hudson.node__monitors.TemporarySpaceMonitor>
<hudson.node__monitors.ResponseTimeMonitor>
false
</hudson.node__monitors.ResponseTimeMonitor>
</hudson.util.DescribableList>

jenkinsci/jenkins#3185 for the record. If you are using some Golang-based tool to manipulate Jenkins XML configurations (which?), pending this fix I suppose it would suffice to start by just stripping out any version='1.1' or version="1.1" from the first line of its input (should be fine to emit nothing or version='1.0' in output), and documenting that the tool will break in the rare case that control characters are present in text managed by the config file.

Any update for xml 1.1!

Change https://go.dev/cl/452235 mentions this issue: encoding/xml: parser should not fail on XML version check in non-strict mode

the error: xml: unsupported version "1.1"; only version 1.0 is supported

but jenkins config file both xml 1.1 like flow: <hudson.util.DescribableList> <hudson.node__monitors.ArchitectureMonitor> false </hudson.node__monitors.ArchitectureMonitor> <hudson.node__monitors.ClockMonitor> false </hudson.node__monitors.ClockMonitor> <hudson.node__monitors.DiskSpaceMonitor> false 1GB </hudson.node__monitors.DiskSpaceMonitor> <hudson.node__monitors.SwapSpaceMonitor> false </hudson.node__monitors.SwapSpaceMonitor> <hudson.node__monitors.TemporarySpaceMonitor> false 1GB </hudson.node__monitors.TemporarySpaceMonitor> <hudson.node__monitors.ResponseTimeMonitor> false </hudson.node__monitors.ResponseTimeMonitor> </hudson.util.DescribableList>

I also had this problem.
My solution is as follows:

1. First replace version='1.1' with version='1.0'
2. After the operation, replace version='1.0' with verison=1.1'

We need to support 1.1