--%>

How does XML maintain white-space in any documents

How does XML maintain white-space in any documents?

E

Expert

Verified

All white-space, with TAB characters, line breaks and normal spaces, until now between structural tools where no text can ever show, is passed by the parser not changed to the application (formatter, converter, browser and viewer), identifying the context wherein the white-space was determined (data content, element content or mixed content, when this information is obtainable to the parser, for example: from a DTD or Schema). It means this is the application's responsibility to make a decision what to do with space, except the parsers:

• Insignificant white-space among structural tools (space that occurs where only tool content is allowed, for example: between other tools, where text data never happens) will find as passed to the application (within SGML this white-space gets suppressed, that is why you can put all which extra space in HTML documents and not worry regarding it)

• Important white-space (space which occurs within elements which can contain text and markup mixed together, usually mixed content or PCDATA) will still get passed to the application exactly as under SGML. It is the application's responsibility to handle it correctly.

• The parser should inform the application that white-space has happened in element content, when it can detect this. SGML user will recognize that such information is not in the ESIS, but this is in the Grove.

< chapter >
< title >
My title for
Chapter 3.
< /title >
< para >
text
< /para >
< /chapter >

In the illustration above, the application will obtain all the pretty-printing linebreaks, TABs, and spaces among the elements. This is the function of the application, not the parser, to decide that type of white-space to discard and that to retain. Several XML applications have configurable options to permit programmers or users to control how that white-space is handled.

   Related Questions in Programming Languages

  • Q : Define Single line comment Single line

    Single line comment: A comment is in the form:     // this line will be avoided by the compiler.

  • Q : What is File Transfer Protocol or FTP

    File Transfer Protocol: The File Transfer Protocol (abbreviated as FTP) states a standard set of rules which make it probable to transfer a file from one file system to the other.

  • Q : Define the term Multiprogramming system

    Define the term Multiprogramming system: It is an operating system which is able to run multiple programs parallel.

  • Q : Write a program to print out ten random

    Write a program to print out ten random numbers from the following sets: a) {0, 1, 2, 3, 4, 5, ...99, 100} b) {1, 2, 3, 4, 5, 6} c) (10, 20, 30, 40, 50,...990, 1000} d) {-5, -4, -3, -2, -1, 0, 1, 2, 3, 4, 5} e) {1.5, 2.0, 2.5, 3.0, 3.5}  

  • Q : Write a program that initializes an

    Write a program that initializes an integer array a[20] with values {0, 1, 2, 3, ...18, 19 - once each} then scrambles them up and prints the values in random order. For example: 19 2 3 8 11 1 4 17 7 15 9 0 16 12 18 13 5 6 10 14    

  • Q : Distinct features of Object oriented

    Q. What are the distinct features of Object oriented programming language?  

    Q : CORBA allows high performance

    'CORBA was designed to allow high performance distributed applications to be written’. Discuss. Definitely, ’CORBA was designed to allow high performance distributed applications to be written’ because it provides:

  • Q : Explain Right shift operator Right

    Right shift operator: Right shift operator (>>) is the bit manipulation operator. It shifts the bits in its left operand zero (0) or many places to the right, according to the value of its accurate operand. The most important bit from before the

  • Q : Define Arithmetic operator Arithmetic

    Arithmetic operator: The Operators, like +, -, *, / and %, which generate a numerical outcome, as a part of an arithmetic expression.

  • Q : Property Specifications of Java

    Property Specifications: The most straightforward way to specify and check simple safety properties in JPF is to use Java assertions inside the application under analysis. This allows the specification of properties that only depend on the application