I'm working with a simple XML file, after editing it with Liquid XML Studio its seems to have added some random chars () to the beginning of the file. Whats going on?
Liquid XML writes odd chars  on the front of the file my xml file
203 Views Asked by Sprotty At
1
There are 1 best solutions below
Related Questions in XML
- Two different numbers in an array which their sum equals to a given value
- how to fill out the table with next values in array with one button
- How to sort a multi-dimensional array by the second array in descending order?
- Looping over defined array elements in Fortran
- Array appending after each onclick and loop in javascript
- PHP : How can I check Array in array?
- store numpy array in mysql
- Java Assign a Value to an array cell
- Saving FileSystemInfo Array to File
- Notice: Undefined offset: 1, but there is such offset
Related Questions in LIQUID-XML
- Two different numbers in an array which their sum equals to a given value
- how to fill out the table with next values in array with one button
- How to sort a multi-dimensional array by the second array in descending order?
- Looping over defined array elements in Fortran
- Array appending after each onclick and loop in javascript
- PHP : How can I check Array in array?
- store numpy array in mysql
- Java Assign a Value to an array cell
- Saving FileSystemInfo Array to File
- Notice: Undefined offset: 1, but there is such offset
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular # Hahtags
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
Byte Order Marker (BOM) and Document Encoding
For further information about the Byte Order Marker (BOM) please see Byte Order Marker.
When Liquid XML Studio loads a document it uses the BOM (if present) to determine the encoding, and uses this to decode the document into an internal Unicode format. The encoding attribute from the XML (if present), is used to refine the decoding of the data to its Unicode form.
If the BOM and encoding attribute conflict then a best guess is made (typically relying on the BOM).
The XML document is stored and manipulated internally as Unicode, and it keeps the encoding provided by the encoding attribute (or BOM) as a property of the document.
Whenever you paste data into the document, it is dealt with as Unicode.
When you save the document the document is written out using the encoding property associated with the document (this may be changed by the user in the properties window). So you should have no issues with encoding.
Issues when using a BOM with UTF-8 Encoded Documents
Unicode files must have a BOM to identify them. The only time the BOM becomes an issue is UTF-8. For UTF-8 there is no standard that says whether the BOM should be written or not. Most Microsoft applications and newer applications write the BOM, some older applications do not write the BOM and worse still don’t understand it when a document is read in that contains a BOM. They may just see the characters EF BB BF or  at the start of the document and assume the document is invalid.
In order to accommodate this we write the BOM by default, but there is a global option to turn it off for UTF-8.
In Liquid XML Studio you can stop the BOM from getting written by changing the setting in:
Tools->Options->Environment->Write Byte Order Marker (BOM)