--%>

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 : What is UNIX Explain, what is UNIX?

    Explain, what is UNIX?

  • Q : Define Inconsistent state Inconsistent

    Inconsistent state: A state which an object must not be in. A class requires to be carefully designed in order to make sure that none of its examples can get into a conflicting state. An illustration of an inconsistent state may be a football team wit

  • Q : Describe Multiple-boot options

    Multiple-boot options: The hardware configurations of several computers are capable to run various operating system and window manager combinations. A few systems permit a user to select which combination they wish to utilize during a specific session

  • Q : Explain Imperative programming

    Imperative programming: The style of programming generally related with languages such as FORTRAN, C, Pascal and so forth. Imperative programming is differentiated from functional programming in that the previous is strongly tied to the idea of variab

  • Q : Explain Coupling Coupling : Coupling

    Coupling: Coupling occurs whenever classes are aware of each of other as their instances should interact. The linkage between two classes which might be either weak or strong. Stronger coupling occurs whenever one class has a thorough knowledge of the

  • Q : Define Final variable Final variable :

    Final variable: A variable with final reserved word in its declaration. The final might not assigned to once it has been initialized. Initialization frequently occurs as a part of its declaration. Though, the initialization of an uninitialized final f

  • Q : Define the term Dynamic type Define the

    Define the term Dynamic type: This type of an object is the name of the class employed to construct it.

  • Q : State Finalization Finalization :

    Finalization: Instantly before an object is garbage collected, its finalize method is called. This offers it the opportunity to free any resources it may be holding on to.

  • Q : Explain the term accessibility testing

    Explain the term accessibility testing.

  • Q : Level-triggering interrupt Normal 0

    Normal 0 false false