XML Format Full Guide: beautification, compression and competition

1. What to do with each of them?

Beautify（Pretty-print / Beautify）

Change the label to a nested layer and indent it to allow a readable parent-child relationship. Typical uses:

• SoAP/REST newspaper that reads the entire line of the log together
• Aligning the Code Review profile
• Check "Fixed Tags" or "Cross-Backs"

BeautifyIn principle, no semantics.: it adjusts the blanks between labels;Text Node InternalWhether meaningful spaces are touched depends on the actual realization. This station tool will be first. >…< The blanks between them are tightened and rewritten by indentation rules, suitable for the "structured text"-based message and configuration; If you rely on the exact blanks in the hybrid content (unique), you should check them in a dedicated editor.

Minify（Minify）

Removes the redundant blanks and row breaks between labels, reduces size, and allows single-line pasting to the requesting body or message queue. The compression should also not change the label name, attribute and text content itself. Note: if a paragraph of text nodeOn purpose.Include a lacuna at the end, and radical compression may affect the presentation; The configuration and API report generally do not have this problem.

Validation: a combination of the two types of data used in the data

The daily connection, 80% of the "XML is broken" is actually...The question of convergence。 Formatting tools spread structures out through indentation, which quickly expose unclosed and cross-sets; XSD rules of operation need to be used to replace IDE,xmllint or service end check. This tool may prompt a check of syntax if you enter a visible anomaly on the formatting path, but do not consider it to be complete Schema verification.

XML border with JSON/ HTML

When you get a clip like a label and a page:Data exchange/configuration, fixed by XML-style rules; If the target isBrowser renderIt's more appropriate. HTML Format。 If the interface is moved to JSON, the interface is wrong. JSON Format。

XML rules that must be carved into muscle memory

Single root element

A single combination XML can only have one root. The following are illegal:

<item>a</item>
<item>b</item>

Should be wrapped under one root, for example. <items>…</items>, or use multiple documents/outside envelopes (SOP's Envelope is this role).

Right-set. No crosses.

<!-- Legal -->
<a><b>text</b></a>

<!-- Illegal：Hand it over.叉嵌套 -->
<a><b>text</a></b>

If you have a "symmetrical" or a "level" retreat, you have to suspect a cross-sectional closure.

Empty elements and self-conclusion

<tag></tag> and <tag/> In most scenarios, the price is equal (allowance to be subject to DTD/XSD). The team should be consistent in style and avoid mixing the same file to cause diff noise.

Properties must be quoted

<!-- Legal -->
<item id="1" name='widget'/>

<!-- Illegal：None引No, no, no. -->
<item id=1/>

If the quotation marks contain the same quotation marks, another quotation sign or the entity (or entities) shall be replaced by a quotation sign." / '）。

Five predefined entities (most common rollovers)

Classic accident: URL query string a=1&b=2 Plug in the element text as it is. The solver is in &b The government has not yet made a decision on the issue. It's written correctly. a=1&b=2, or put the whole section in CDATA(See below).

CDATA: When to use, when to use

<scriptDesc><![CDATA[
  if (a < b && c > d) { ... }
]]></scriptDesc>

CDATA Keep character almost as it is (except not visible) ]]> Sequence) suitable for embedded code segments or already contained in large quantities < & .don't wantAvoiding otherwise structured fields with CDATA; Security-sensitive content remains filtered in accordance with operational rules.

Declaration, Encoding and BOM

Common declaration:

<?xml version="1.0" encoding="UTF-8"?>

The declaration must be in the file ' s best position (the lead blank is not welcome in part of the solver). If the code declaration is inconsistent with the true byte code, the Chinese text is either miscoded or directly deciphered. Windows notes save as UTF-8 with BOM, which occasionally leads to a "first line is not a declaration" type error - a check with hexadecimal or editor "Shows invisible characters".

Name space is not decoration.

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <m:GetPrice xmlns:m="urn:example">
      <m:Item>Book</m:Item>
    </m:GetPrice>
  </soap:Body>
</soap:Envelope>

Prefixes must be bound to URI; It's missing when copying paste. xmlns:, or confuses the default naming space with the prefix of the sub-element, often in the form of "local tests that pass and report unknown elements". Formatting will help you see the level, but...No automatic naming space。

3. Thousands of cells for gradual operation

tools page:XML Formatting and Compressing。 The interface is a double bar to the left (or above):Input XML / OutputResult, in between the operation and indent settings.

3.1. Beautification of a crowded paper

1. Opens the toolbar to confirm the theme comfort (the top right can be toggle light/dark).
2. Paste original text in "Input XML" Or a little. Load examples First familiar with output form (example is tape) note / items - The demonstration tree.
3. Yes. Indent Lower Larry chooses:

• 2 spacesFront-end/part open-source project habits
• 4 spaces(Default): Many Java/Enterprise Configuration and IDE Defaults
• Tab: Usage only when the warehouse explicitly requests Tab

1. Click Format (Beautify)。
2. The results of the inspection are at the level of "output": Use CopyResult Postes the editor, worksheet or diff tool.

If you enter empty, the tool will prompt you to enter XML first. When dealing with anomalies, you are prompted to check the syntax - and then return to the Rule and the following error table, instead of the repeated button.

3.2 Compressed before sending

1. Confirms that current input is alreadyFullContent (may be adorned by the eye, then glued back into the input or directly compressed with the already integrated text).
2. Click Minify (Minify): The blanks between labels are removed and a tighter single line/string is obtained.
3. Copy to HTTP request, message middle or scene that requires save.

The Joint Recommendations:People look at the glorified version, they upload it online.； The two-sided text should be used to avoid "A" and "B" changes.

3.3 Recommended queuing rings

Paste原始 XML
  → Format（ChooseOkay.Indent）
  → 扫One.眼Root element / Namespace / 最深One.层Yes.YesAlignment
  → IfFailedorStructure怪异：PressError表ChangeEntities、闭合、引No, no, no.
  → Again.FormatConfirm.
  → Yes.传Lose.TimeAgain.Minify
  → CopyFrontYeah.Key、Token、ID number脱Min.

3.4 Local processing of borders (incorporated in custom)

• Logical is done in the browser.No pass-over server； Do not stick unsensitized production keys around as test data.
• This tool focuses onIndentation beautification and space compression, not XSD, not XML digital signature tool, nor SOAP UI.
• Large files may be restricted by browser memory and text domain performance; Logs above trillions suggest first the relevant clips or the desktop tool.
• Formatting algorithms reset blanks by label boundary, and the error information entered for extreme malformations is less precise than the specific solver - with the "is it stabilised + the eye level" as the first objective.

4. Common errors and treatments

Principles: When formatting fails, the input is reduced to a "minimum replicable clip" (reserve root and error node), the alignment is made, and the context is restored. Don't blindly change in tens of KiloCell of lines.

5. Real work landscape

Scenario A: SOAP / Enterprise Interface Linking

Back to the end of the line Envelope, or request for local packaging was denied. Practices:

1. Plug in to the request/response tool FormatConfirmed. Header / Body Level.
2. Checks whether the namespace URI is consistent with the WSDL (prefixed variable, URL unaltered).
3. Check if Body Operations Node is overpacked/underpacked.
4. Once you've finished, if the gateway is single, then again. Minify (a) Send out; A beautified attachment to the work plan is maintained.

The scene is B: Android. strings.xml / Resources XML

Build an XML parsing error after translating or merging a branch. Practices:

1. Beautify strings.xml Or playout, see if there's any unclosed <string> / <LinearLayout>。
2. Abbreviations, unmarks,& Convert to Android resource rules (e.g. in text) '、&）。
3. Harmonized indent (recommendation 4 or in line with Android Studio), reducing meaningless diff.
4. The idea of "concentrating" the signed binary resources is not to be used as a "concentrated" illusion. What's beautiful about this place?Source XML。

C:Maven pom.xml / Spring and Log Configuration

pom.xml Reliance not effective,logback.xml Not on board. Practices:

1. And then you'll be able to confirm every one of them. dependency、appender、logger Close it in pairs.
2. See if the note is written near the label, causing semi-stop tags.
3. The difference is usually in the missing nodes or in the naming space.
4. Compression Before SubmitUsually, no need.— Source library cares more about readable diff; Compression is left to interfaces.

Scene D: RSS/Atom, SVG Script, Exported Excel XML

Content team export feed or design to drop SVG. Practices:

1. Let's go and look at the root first. rss / feed / svg Which one.
2. SVG often contains a large number of paths and properties, and is a good way to find the wrong label, but confirm before recompression whether the viewer is sensitive to the blank (most path data are in the properties, are safer).
3. Feed HTML content is often found in CDATA or entities; Don't break it when you change the description. ]]>。

7. How to select the relevant tools

Decision-making line: The data is not a tree with sharp brackets? is XML/HTML; Is it "Bracketed Object"? → JSON； Is it "indentation configuration"? → YAML。 The wrong tool is wasted half an hour on the wrong message.

8. Small habits in teamwork

1. The contract goes first.SOAP/XML API is based on XSD/WSDL instead of on a certain package-sailing result.
2. Unified Indentation: Fixed 2 or 4 spaces in the editor with CI to avoid Tab/Space.
3. I'll review the saffron.: Pr configuration XML formatted and diffed, less "whole file line" cannot be reported.
4. Example Library: prepare a minimal combination of dissensitized models, and new people run through format and fill fields.
5. Log Policy: Production logs can be cut off from XML body; The local beauty of the entire section is taken when the barrier is in place.

FAQ

Continue reading

• Do it:XML Formatting and Compressing
• Page structure is similar:HTML Format Full Guide
• Interface mainstream data:JSON Format Full Guide
• Configure indents sensitive:YAML Format Full Guide

After using the term "co-opt and then change business and compress where necessary" as a fixed technique, the XML network moved from a subject of genre to a list.