Skip to content

Commit 2e611c2

Browse files
authored
Update index.html
Changes has been made based on the suggestion of the issue "Remove heading for section 5 #23"
1 parent 02290c3 commit 2e611c2

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

index.html

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -816,8 +816,7 @@ <h3>Various example use cases of ABNF based Indic orthographic syllable definiti
816816
</section>
817817

818818

819-
<section id="h_requirements_for_indic_layout">
820-
<h2>Requirements for Indic Layout </h2>
819+
821820
<section id="h_text_segmentation">
822821
<h2>Text segmentation</h2>
823822
<p>A string of Unicode-encoded text often needs to be broken up into text elements programmatically. Common examples of text elements include what users think of as characters, words, lines (more precisely, where line breaks are allowed), and sentences. The precise determination of text elements may vary according to orthographic conventions for a given script or language. The goal of matching user perceptions cannot always be met exactly because the text alone does not always contain enough information to unambiguously decide boundaries. For example, the period (U+002E FULL STOP) is used ambiguously, sometimes for end-of-sentence purposes, sometimes for abbreviations, and sometimes for numbers. In most cases, however, programmatic text boundaries can match user perceptions quite closely, although sometimes the best that can be done is not to surprise the user. Word boundaries are used in a number of different contexts. The most familiar ones are selection (double-click mouse selection, or “move to next word” control-arrow keys), and “Whole Word Search” for search and replace. They are also used in database queries, to determine whether elements are within a certain number of words of one another .

0 commit comments

Comments
 (0)