SOX is an alternative（1）for XML.It is useful for reading and creating XML content in a（2）.editor.It is then easily transformed into proper XML.SOX was created because developers can spend a great deal oftime with raw XML.For many ofus,thepopular XML（3）have not reached a point where their tree views,tables and forms can completely substitute for the underlying（4）languagE.This is not surprising when one considers that developers still use a text view,albeit enhanced,for editing other languages such as Java）SOX uses（5）to represent the structure of an XML document,which eliminates the need for closing tags and a number of quoting devices.The result is surprisingly clear.

A:graphic B:program C:command D:text

SOX is an alternative（1）for XML. It is useful for reading and creating XML content in a（2）editor. It is then easily transformed into proper XML. SOX was created because developers can spend a great deal of time with raw XML. For many of us, the popular XML（3）have not reached a point where their tree views, tables and forms can completely substitute for the underlying（4）language. This is not surprising when one considers that developers still use a text view, albeit enhanced, for editing other languages such as Java. SOX uses（5）to represent the structure ofan XML document, which eliminates the need for closing tags and a number of quoting devices. The result is surprisingly clear.

A:graphic B:program C:command D:text

SOX is an alternative syntax for (71) . It is useful for reading and creating XML content in a text editor. It is then easily transformed into proper XML. SOX was created because developers can spend a great deal of time with raw XML. For many of us, the popular XML (72) have not reached a point where their tree views, tables and forms can completely substitute for the underlying. (73) language. This is not surprising when one considers that developers still use a (74) view, albeit enhanced, for editing other languages such as Java. SOX uses (75) to represent the structure of an XML document, which eliminates the need for closing tags and a number of quoting devices. The result is surprisingly clear.

A:tree B:text C:program D:graphic

SOX is an alternative syntax for (3) . It is useful for reading and creating XML content in a text editor. It is then easily transformed into proper XML. SOX was created because developers can spend a great deal of time with raw XML. For many of us, the popular XML (4) have not reached a point where their tree views, tables and forms can completely substitute for the underlying. (5) language. This is not surprising when one considers that developers still use a (6) view, albeit enhanced, for editing other languages such as Java. SOX uses (7) to represent the structure of an XML document, which eliminates the need for closing tags and a number of quoting devices. The result is surprisingly clear.

A:tree B:text C:program D:graphic

SOX is an alternative (66) for XML. It is useful for reading and creating XML content in a (67) editor. It is then easily transformed into proper XML. SOX was created because developers can spend a great deal of time with raw XML. For many of us, the popular XML (68) have not reached a point where their tree views, tables and forms can completely substitute for the underlying (69) language. This is not surprising when one considers that developers still use a text view, albeit enhanced, for editing other languages such as Java. SOX uses (70) to represent the structure of an XML document, which eliminates the need for closing tags and a number of quoting devices. The result is surprisingly clear.

A:command B:program C:graphic D:text

SOX is an alternative (71) for XML. It is useful for reading and creating XML content in a (72) editor. It is then easily transformed into proper XML. SOX was created because developers can spend a great deal of time with raw XML. For many of us, the popular XML (73) have not reached a point where their tree views, tables and forms can completely substitute for the underlying (74) language. This is not surprising when one considers that developers still use a text view, albeit enhanced, for editing other languages such as Java. SOX uses (75) to represent the structure of an XML document, which eliminates the need for closing tags and a number of quoting devices. The result is surprisingly clear.

A:command B:program C:graphic D:text

SOX is an alternative (156) for XML. It is useful for reading and creating XML content in a (157) editor. It is then easily transformed into proper XML. SOX was created because developers can spend a great deal of time with raw XML. For many of us, the popular XML (158) have not reached a point where their tree views, tables and forms can completely substitute for the underlying (159) language. This is not surprising when one considers that developers still use a text view, albeit enhanced, for editing other languages such as Java. SOX uses (160) to represent the structure of an XML document, which eliminates the need for closing tags and a number of quoting devices. The result is surprisingly clear.

A:graphic B:program C:command D:text

SOX is an alternative (156) for XML. It is useful for reading and creating XML content in a (157) editor. It is then easily transformed into proper XML. SOX was created because developers can spend a great deal of time with raw XML. For many of us, the popular XML (158) have not reached a point where their tree views, tables and forms can completely substitute for the underlying (159) language. This is not surprising when one considers that developers still use a text view, albeit enhanced, for editing other languages such as Java. SOX uses (160) to represent the structure of an XML document, which eliminates the need for closing tags and a number of quoting devices. The result is surprisingly clear.

A:graphic B:program C:command D:text

SOX is an alternative（）for XML. It is useful for reading and creating XML content in a（）editor. It is then easily transformed into proper XML. SOX was created because developers can spend a great deal of time with raw XML. For many of us, the popular XML（）have not reached a point where their tree views, tables and forms can completely substitute for the underlying（）language. This is not surprising when one considers that developers still use a text view, albeit enhanced, for editing other languages such as Java. SOX uses（）to represent the structure of an XML document, which eliminates the need for closing tags and a number of quoting devices. The result is surprisingly clear.

A:graphic B:program C:command D:text