--%>

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 : Networking Homework Assignment : A

    Homework Assignment : A Barbershop Problem Due: November 20, 2012 In this assignment, you are asked to write a multithreading problem to simulate the barbershop problem, which is a classical synchronization problem. The problem is taken from William Stallings's Operating Systems: Internals and D

  • Q : Explain Edit-compile-run cycle

    Edit-compile-run cycle: A common portion of the program development procedure. The source file is made initially and compiled. The syntax errors should be corrected in the editor before compiling it again. Once the program has been productively compil

  • Q : Different services provided by DLR to

    Give details about the different services that are provided by DLR to CLR?

  • Q : Properties exposed through ActiveX

    Write down the properties exposed through ActiveX controls?

  • Q : Program for Linux operating system that

    Write a program for Linux operating system that uses Posix threads to sort a large array.  Specifically, you should write a program to generate random numbers. Then create at least two threads, each of which sorts a portion of the array. After the thr

  • 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 : Define Unions Unions: Unions in C and

    Unions: Unions in C and C++ are object overlays—aggregate quantities such as structs, except that each element of the union consists offset 0, and the total size of union is only as large as is required to hold its largest member (Kernighan and

  • Q : State the term LDAP State the term LDAP

    State the term LDAP?

  • Q : Differences between primary storage and

    What are the differences between primary storage and secondary storage?

  • Q : Explain Information hiding Information

    Information hiding: The practice of making sure that only as much information is exposed regarding the implementation of a class as is strictly needed. Hiding needless knowledge of implementation makes it not as much of likely that other classes will