We Keep Coding

Building not valid XML Document (Name cannot begin with the '0' character) [duplicate]

This question already has answers here:
How to parse invalid (bad / not well-formed) XML?
(4 answers)
Closed last year.
I am trying to decode a custom xml config file in C#, but I am having troubles to create this file from the string I was able to get after my decode step.
After trying to build the xml, I got this error:
System.Xml.XmlException : 'Name cannot begin with the '0' character, hexadecimal value 0x30. Line 1, position 2.'
I know my xml is not a valid xml file because of its bad formatting but I would like to know is there is a way to build it anyways.
Format of the "xml file" :
<01_config.xml>
<name dataType="String">some_name</name>
<description dataType="String">some_description</description>
</01_config.xml>
If I replace 01_config.xml by config during debug, everything will work fine since it will become a valid xml file. But it will not be the good format for my config.
I guess I can still build the file without using the C# Xml building tools, but I would like to know if it's possible to do it with it in the first place.

XML component (element and attribute) names may not begin with a number.
Strictly speaking, this is a matter of the rules for being an XML document – well-formedness, not validity.
Reasons to correct this mistake
You want your document to be XML.
You want users of your document to be able to use the XML ecosystem of editors, parsers, validators, databases, transformation/selection languages, and libraries available in many languages.
You want the interoperability benefits of using a standard.
You want to participate in a community of users – tapping into, and contribute to, a collective body of knowledge to the community's mutual benefit.
Reasons to proceed with bad "XML"
You like the aesthetics of your "XML" variant because it's a "good format for my config".
Recommendation
Fix the mistake and work with standard XML.
See also
How to have an XML tag start with a number?
How to parse invalid (bad / not well-formed) XML?

I know my xml is not a valid xml file because of its bad formatting but I would like to know is there is a way to build it anyways.
Sure, you can build files that aren't well-formed XML, but then you won't be able to read them using XML tools.

How to read XML document which is fixed width?

I got an XML file to load. The problem is that it is physically saved as a fixed width file. This means that the whole is written in lines with a fixed width, with exceptions, i.e. there may be fewer characters in the line.
There are errors when using XmlDocument.Load ().
How to correctly load such an XML file?
This is how the file looks:

Use the file helpers-library from C#
It's free and should solve your problem: https://www.filehelpers.net/
Edit: If you're doing that already it would be good to know the error message you are getting.

My guess is that you have to fix the file into the proper format. To be honest, I've seen these particular xmls and I've never seen such occurence. When you download the XML it is already in such format?
I guess, you're creating an XML out of the given XML schema (XSD), at least that's what I was doing with "JPK". What error are you receiving from XmlDocument.Load()?

Wrong characters for accents in one Windows-1252 encoded XML

In the XML i need to read in C#, i find characters such as
é, É.
As far as i know , i should not find those characters in a windows-1252 encoded XML. Can i fix that problem in C# or the XML itself must be updated?
Thanks in advance.

It does look like the XML needs to be updated.
You could certainly write something that reads it in as the UTF-8 it really is and writes it back out as the Windows-1252 it claimed to be, but why bother? XML in Windows-1252 is like someone using their smart-phone while dressed ye olde knight at a Renaissance Faire anyway. Just drop the incorrect declaration from the first line and away you go.

The simple answer is: you're probably using the wrong encoding. From this I'd say you should be using UTF-8. You can force it by downloading the document before parsing it.
I should note that downloading URL's is tricky: web servers often report the wrong encoding. That is also the reason why the HTML5 standard includes a section on encoding detection. I'm afraid there's no easy generic solution for this -- we ended up implementing our own encoding detection algorithms for our web crawlers.

XML file generated in windows not loading in linux environment

We are generating an xml file in C# using xmlseralizer and UTF8 encoding. We check the output and the xml is well formed and passes XSD validation.
We send this xml to customer who load this in UNIX environment. They keep on telling us that xml is not valid and has invalid characters. We don't have UNIX environment to test.
The question being, is there any difference when loading xml files in UNIX?
What can we ask the customer to provide to better understand this situation?

You might have a UTF-8 BOM as the first three bytes of your file:
<?xml version="1.0" encoding="utf-8"?>
It is not part of the XML document so a file reader should not pass it on to be interpreted by the XML parser. If you have it, you could try to remove it and see if your users have the same complaint. Most editors will not show it to you so you might have use a hex editor. (Hex: EF BB BF).
If the problem remains, you'd need to know at what byte offset the purported invalid characters are and which section of the XML specification they violate. Which program and version they are use and what feedback it gives might be helpful, too.
You might also consider that the file is getting damaged in delivery. A round trip transmission might help detect that.

XmlException: Text node cannot appear in this state

I'm getting sometimes the error "Text node cannot appear in this state" in my application after editing a xml in MonoDevelop and loading it with dotNET.
This error is really annoying, because i have to copy the XML-file to windows and try to fix it there with VS.
The xml file is absolutly correct, must be something with the encoding.
Is there any quick way to fix this in MonoDevelop?
And of course, it would be interesting why this error appears.
Edit ( Short XML example on request )
<?xml version="1.0" encoding="UTF-8"?>
<Data>
</Data>

I was trying to reproduce this problem and I found that (given my contrived reproduction) that all I had to do was edit the first line of the xaml
<?xml version="1.0" encoding="UTF-8"?>
It appears as though, when the encoding changed, that there was a single space before the <?xml node in the file. I used TextWrangler to open the file and saw the space. Simply editing the file in Xamarin Studio resolved the issue. In further investigation it looked as though there were 2 BOMs in the header of the file.
fe ff fe ff
I'd love to hear back if anyone can pinpoint how the encoding changed though.

I found only one workaround for this error when using monodevelop only( There are other ways to solve this issue by using another editor ):
Saving the file with another encoding ( UTF-16 ). This is not going to solve it permanently, if you edit the file again it may occur again.

I think the problem is that the Byte Order Mark appears as the first 2 bytes, and a parser that doesn't expect a byte order mark will interpret it as a short text node. Re-encoding without the BOM should fix it.