Comments (5)
Thank you,
I have been able to workaround with the following approach:
var remove = new List<XmlNode>();
XmlDocument doc = this.Instance.ToXmlDocument();
// Identify nodes incompatible with ATO
foreach (XmlNode node in doc)
{
if (node.NodeType == XmlNodeType.XmlDeclaration || node.NodeType == XmlNodeType.ProcessingInstruction)
{
remove.Add(node);
}
}
// Remove nodes incompatible with ATO
foreach (XmlNode node in remove)
{
doc.RemoveChild(node);
}
var settings = new XmlWriterSettings();
settings.OmitXmlDeclaration = true;
settings.Indent = true;
settings.IndentChars = "\t";
settings.NamespaceHandling = NamespaceHandling.OmitDuplicates;
settings.Encoding = Encoding.UTF8;
// Output refined XML
using (XmlWriter writer = XmlWriter.Create(output, settings))
{
doc.WriteTo(writer);
}
from xoxo.
from xoxo.
This is now fixed in 3.3.0.
You can control specific bits of the metadata with report properties:
report.OutputInstanceGenerator = false;
report.OutputTaxonomyVersion = false;
report.OutputXmlDeclaration = false;
report.OutputComments = false;
https://www.nuget.org/packages/Diwen.Xbrl/3.3.0
from xoxo.
Wow. That was fast.
Thank you,
from xoxo.
Well it was a pretty straightforward fix, let's just hope it does what you need.
from xoxo.
Related Issues (20)
- Allow string formatting of reported differences for data points etc.
- Fails to parse ExplicitMember with whitespace in value HOT 8
- Unit.Measure should be XmlQualifiedName instead of string HOT 1
- No support for Inline XBRL HOT 1
- No way to validate inline xbrl HOT 1
- Drop support for .NET Framework 4.5.2 HOT 1
- [Question] how to add an explicit member with namespace specified HOT 5
- Support for XBRL-CSV HOT 4
- Unused namespace 'xbrldi' for instance with no explicit or typed members
- ScenarioComparisonMessage has extra set of parentheses HOT 1
- Bug with namespaces used in the value field of a segment explicit member HOT 3
- Use System.Text.Json instead of string handling
- xBRL-JSON support HOT 1
- Missing conversion from xBRL-JSON to xBRL-XML
- No API documentation
- ESEF validations don't belong in the library
- Xml/Fact Equals does not consider contextRef HOT 3
- Xml/Report FromXml does not provide an overload for additional parameters. HOT 4
- Context comparison throws in certain cases when one Scenario is null
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from xoxo.