UserPreferences

PaceTextRules


Abstract

Tighten up rules on processing text to ensure interop between apps

Status

Open

Rationale

Plain text may be interpreted and displayed in various different ways. Similarly text in the source may be formatted in many different ways. Clear rules are required to remove the possibility of disputes between publishers to avoid disputes over how text is formatted in the source and how it is displayed.

Proposal

Add "xml:space attributes appearing on Text constructs or their parents MAY be ignored by processors" to 3.1 Text Constructs.

Replace "Thus, software MAY display it using normal text rendering techniques such as proportional fonts, white-space collapsing, and justification." with "Software displaying this text SHOULD remove white-space at the beginning and end; collapse white-space between words; and disregard line break, tab and other formatting characters." in 3.1.1 (TEXT).

Add "xml:space directives appearing on atom:content or its parents MAY be ignored by processors" to 4.15 atom:content.

Replace "Thus, software MAY display it using normal text rendering techniques such as proportional fonts, white-space collapsing, and justification." with "Software displaying this text SHOULD remove white-space at the beginning and end; collapse white-space between words; and disregard line break, tab and other formatting characters." in 4.15.3 (TEXT).

Impacts

None

Notes

Some formal definition of whitespace etc may be needed.


CategoryProposals