From 68d7f1007661cb19cac2f9b0f6c3d180601a2e13 Mon Sep 17 00:00:00 2001 From: Patricia O Connor Date: Tue, 10 Dec 2024 21:19:06 +0000 Subject: [PATCH] Replace break with beginning --- .../en/CH-LanguagesCharacterSets.xml | 2 +- P5/Source/Guidelines/en/CO-CoreElements.xml | 24 +++++++++---------- .../Guidelines/en/DI-PrintDictionaries.xml | 4 ++-- .../Guidelines/en/DS-DefaultTextStructure.xml | 6 ++--- .../en/FT-TablesFormulaeGraphics.xml | 2 +- P5/Source/Guidelines/en/HD-Header.xml | 4 ++-- .../Guidelines/en/NH-Non-hierarchical.xml | 2 +- P5/Source/Guidelines/en/PH-PrimarySources.xml | 4 ++-- .../Guidelines/en/SG-GentleIntroduction.xml | 6 ++--- .../en/WD-NonStandardCharacters.xml | 4 ++-- 10 files changed, 29 insertions(+), 29 deletions(-) diff --git a/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml b/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml index 97931191b0..2400b0218e 100644 --- a/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml +++ b/P5/Source/Guidelines/en/CH-LanguagesCharacterSets.xml @@ -426,7 +426,7 @@ dates, and predefined value lists.

individual characters, the overall typesetting process also follows specific rules of how to calculate the distance between characters, how much whitespace occurs between words, at which - points line breaks might occur and so forth.

+ points line beginnings might occur and so forth.

If we concern ourselves only with the rendering process of the characters themselves, leaving out all these other parameters, we will realize that of all the information required for this process, only a small diff --git a/P5/Source/Guidelines/en/CO-CoreElements.xml b/P5/Source/Guidelines/en/CO-CoreElements.xml index 7df83faa4f..974aadb202 100644 --- a/P5/Source/Guidelines/en/CO-CoreElements.xml +++ b/P5/Source/Guidelines/en/CO-CoreElements.xml @@ -329,7 +329,7 @@ problem for text encoders. Suppose, for example, that we wish to investigate a diachronic English corpus for occurrences of tea-pot and teapot, to find evidence for the point at which this compound becomes -lexicalized. Any case where the word is hyphenated across a linebreak, +lexicalized. Any case where the word is hyphenated across a line beginning, like this: is ambiguous: there is no simple way of deciding which of the two @@ -381,11 +381,11 @@ whitespace.

The lb, pb, and cb elements are notable exceptions to this general rule, since their function is precisely to -represent (or replace) line, page, or column breaks, which, as noted +represent (or replace) line, page, or column beginnings, which, as noted above, are generally considered to be equivalent to whitespace. These elements provide a more reliable way of preserving the lineation, pagination, etc of a source document, since the encoder should not -assume that (untagged) line breaks etc. in an XML source file will +assume that (untagged) line beginnings etc. in an XML source file will necessarily be preserved.

To control the intended tokenization, the encoder may use the @@ -3492,11 +3492,11 @@ section and in section .

When a text has no pre-existing associated reference system of any kind, these Guidelines recommend as a minimum that at least the page boundaries of the source text be marked using one of the methods -outlined in this section. Retaining page breaks in the markup is also +outlined in this section. Retaining page beginnings in the markup is also recommended for texts which have a detailed reference system of their -own. Line breaks in prose texts may be, but need not be, tagged.Many encoders find it convenient to retain the line -breaks of the original during data entry, to simplify proofreading, -but this may be done without inserting a tag for each line break of +own. Line beginnings in prose texts may be, but need not be, tagged.Many encoders find it convenient to retain the line + beginnings of the original during data entry, to simplify proofreading, + but this may be done without inserting a tag for each line beginning of the original.

Using the xml:id and n Attributes

When traditional reference schemes represent a hierarchical @@ -3900,7 +3900,7 @@ treated as a single word, a tagging such as the following is recommended: ...sed imperator dixit... -Where hyphenation appears before a line or page break, the encoder may + Where hyphenation appears before a line or page beginning, the encoder may or may not choose to record the fact, either explicitly using an appropriate Unicode character, or descriptively for example by means of the rend attribute; see further .

@@ -5645,8 +5645,8 @@ metrical rather than typographic lines. In some modern or free verse, it may be hard to decide whether the typographic line is to be regarded as a verse line or not, but the distinction is quite clear for verse following regular metrical patterns. Where a metrical line is -interrupted by a typographic line break, the encoder may choose to -ignore the fact entirely or to use the empty lb (line break) +interrupted by a typographic line beginning, the encoder may choose to +ignore the fact entirely or to use the empty lb (line beginning) element discussed in . By convention, the start of a metrical line implies the start of a typographic line; hence there is no need to introduce an lb tag at the start of every @@ -5664,13 +5664,13 @@ starts within a metrical line, as in the following example: In the original copy text, the presence of an ornamental capital at the start of the poem means that the measure is not wide enough to print the first four lines on four lines; instead each metrical line occupies -two typographic lines, with a break at the point indicated. Note that +two typographic lines, with a beginning at the point indicated. Note that this encoding makes no attempt to preserve information about the whitespace or indentation associated with either kind of line; if regarded as essential, this information would be recorded using the rend or rendition attributes discussed in .

The l element should not be used to represent typographic -lines in non-verse materials: if the line-breaking points in a prose + lines in non-verse materials: if the line-beginninging points in a prose text are considered important for analysis, they should be marked with the lb element. Alternatively, a neutral segmentation element such as seg or ab may be used; see further diff --git a/P5/Source/Guidelines/en/DI-PrintDictionaries.xml b/P5/Source/Guidelines/en/DI-PrintDictionaries.xml index 984ad248ef..592c27433a 100644 --- a/P5/Source/Guidelines/en/DI-PrintDictionaries.xml +++ b/P5/Source/Guidelines/en/DI-PrintDictionaries.xml @@ -2227,7 +2227,7 @@ following three, which help to clarify some issues raised with particular urgenc dictionaries, on account of the complexity of both their typography and their information structure. (a) the typographic view—the -two-dimensional printed page, including information about line and page breaks + two-dimensional printed page, including information about line and page beginnings and other features of layout (b) the editorial view—the one-dimensional sequence of tokens which can be seen as the input to the typesetting process; the wording and @@ -2243,7 +2243,7 @@ therefore hyphenated (naut- ical); the typographic view of the dictionary preserves this information. In a purely editorial view, the particular form in which the domain name is given in the particular dictionary (as nautical, rather than naut., Naut., etc.) -would be preserved, but the fact of the line break would not. Font shifts might + would be preserved, but the fact of the line beginning would not. Font shifts might plausibly be included in either a strictly typographic or an editorial view. In the lexical view, the only information preserved concerning domain would be some standard symbol or string representing the nautical domain (e.g. naut.) regardless of the diff --git a/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml b/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml index 727a2d6729..f3e14eba2f 100644 --- a/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml +++ b/P5/Source/Guidelines/en/DS-DefaultTextStructure.xml @@ -1506,7 +1506,7 @@ the div elements containing chapters of the text itself. (For the

-Alternatively, the pointers in the index might link to the page breaks + Alternatively, the pointers in the index might link to the page beginnings at which a chapter begins, assuming that these have been included in the markup: @@ -1629,7 +1629,7 @@ the work discussed earlier in this section: @@ -1731,7 +1731,7 @@ transcription): -Note that if the page breaks in the original source have also been + Note that if the page beginnings in the original source have also been explicitly encoded, and given identifiers, the references to them in the above index can more usefully be recorded as links. For example, assuming that the encoding of page 461 of the original source starts diff --git a/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml b/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml index 2d7ba565fa..5090a7ddd6 100644 --- a/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml +++ b/P5/Source/Guidelines/en/FT-TablesFormulaeGraphics.xml @@ -255,7 +255,7 @@ this is rarely if ever done in practice.

The content of table elements is not limited to head and row. Milestone elements such as cb and lb - allow breaks to be signalled inside tables; figure provides an + allow beginnings to be signalled inside tables; figure provides an option for including data which is not amenable to normal row and cell analysis; and other elements such as epigraph and trailer provide options for including text which is clearly diff --git a/P5/Source/Guidelines/en/HD-Header.xml b/P5/Source/Guidelines/en/HD-Header.xml index 5fa66dc927..abb789f103 100644 --- a/P5/Source/Guidelines/en/HD-Header.xml +++ b/P5/Source/Guidelines/en/HD-Header.xml @@ -1410,7 +1410,7 @@ it to mark italicised English words only.

The withId attribute may optionally be used to specify how many of the occurrences of the element in question bear a value for the global xml:id attribute, as in the following -example: Marks page breaks in the York + example: Marks page beginnings in the York (1734) edition only This indicates that the pb element occurs 321 times, on each of which an identifier is provided.

@@ -1518,7 +1518,7 @@ not recommended for automatic processing.

text. The n attribute on each div1 and div2 contains the canonical reference for each such division, in the form 'XX.yyy', where XX is the book number in Roman - numerals, and yyy the section number in arabic. Line breaks are + numerals, and yyy the section number in arabic. Line beginnings are marked by empty lb elements, each of which includes the through line number in Casaubon's edition as the value of its n attribute.

diff --git a/P5/Source/Guidelines/en/NH-Non-hierarchical.xml b/P5/Source/Guidelines/en/NH-Non-hierarchical.xml index 589dfb8977..f4f74e3a5c 100644 --- a/P5/Source/Guidelines/en/NH-Non-hierarchical.xml +++ b/P5/Source/Guidelines/en/NH-Non-hierarchical.xml @@ -220,7 +220,7 @@ wound.

 typographical and metrical line divisions correspond, lb does not itself make a metrical claim: in encoding verse from sources, such as Old English manuscripts, where - physical line breaks are not used to indicate metrical + physical line beginnings are not used to indicate metrical lineation, the correspondence would break down entirely.

diff --git a/P5/Source/Guidelines/en/PH-PrimarySources.xml b/P5/Source/Guidelines/en/PH-PrimarySources.xml index 77bf99e7f4..ba46321e3f 100644 --- a/P5/Source/Guidelines/en/PH-PrimarySources.xml +++ b/P5/Source/Guidelines/en/PH-PrimarySources.xml @@ -750,7 +750,7 @@ used to define a polygon of any shape using this coordinate system:--> methods of recording editorial or other alterations to the text, such as expansion of abbreviations, corrections, conjectures, etc. (section ) methods of describing important extra-linguistic phenomena in the source: unusual - spaces, lines, page and line breaks, changes of manuscript hand, etc. (section ) + spaces, lines, page and line beginnings, changes of manuscript hand, etc. (section ) methods of representing aspects of layout such as spacing or lines methods of representing material such as running heads, catch-words, and the like @@ -2550,7 +2550,7 @@ referring to the zone marked in purple on the right

This approach assumes that the transcription will primarily be organized in the same way as the physical layout of the source, using embedded transcription elements. Alternatively, where the a non-embedded transcription has been provided, using the text element, - it is still possible to record gathering breaks, page breaks, column breaks, line breaks + it is still possible to record gathering beginnings, page beginnings, column beginnings, line beginnings etc in the source, using the elements described in section . Detailed metadata about the physical make-up of a source will usually be summarized by the physDesc component of an msDesc element discussed in .

diff --git a/P5/Source/Guidelines/en/SG-GentleIntroduction.xml b/P5/Source/Guidelines/en/SG-GentleIntroduction.xml index 89421b1d60..9d8e9faec5 100644 --- a/P5/Source/Guidelines/en/SG-GentleIntroduction.xml +++ b/P5/Source/Guidelines/en/SG-GentleIntroduction.xml @@ -229,7 +229,7 @@ forth. And for certain types of analysis (most notably textual criticism) the physical appearance of one particular printed or manuscript source may be of importance: paradoxically, one may wish to use descriptive markup to describe presentational features such as -typeface, line breaks, use of whitespace and so forth.

+typeface, line beginnings, use of whitespace and so forth.

These textual structures overlap with one another in complex and unpredictable ways. Particularly when dealing with texts as @@ -346,7 +346,7 @@ document.The element names here have been chosen for clarity of exposition; there is, however, a TEI element corresponding to each. It will, however, serve as an introduction to the basic notions of XML. -Whitespace and line breaks have been added to the example for the + Whitespace and line beginnings have been added to the example for the sake of visual clarity only; they have no particular significance in the XML encoding itself. Also, the line ]]> @@ -1256,7 +1256,7 @@ only so that it can be clearly distinguished from the structure of the document. As suggested above, one common example is the need, when processing an XML document for printed output, to include a suggestion that the formatting processor might use to -determine where to begin a new page of output. Page-breaking decisions +determine where to begin a new page of output. Page-beginning decisions are usually best made by the formatting engine alone, but there will always be occasions when it may be necessary to override these. An XML processing instruction inserted into the document is one very simple diff --git a/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml b/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml index c6c7c38b0e..d673231382 100644 --- a/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml +++ b/P5/Source/Guidelines/en/WD-NonStandardCharacters.xml @@ -1250,11 +1250,11 @@ precinct at Dodona. (L.H. Jeffery Archive) is reversed, and so is their individual orientation (in fact, we see them from the back, as it were). seg elements have been used here because these are clearly not lines - in the sense of poetic lines; the text is continuous prose, and linebreaks + in the sense of poetic lines; the text is continuous prose, and line beginnings are incidental.

There are obviously some unsatisfactory aspects of this manner of encoding - boustrophedon. In the inscription above, some words run across linebreaks, + boustrophedon. In the inscription above, some words run across line beginnings, so if we wished to tag both words and the right-to-left phenomena, one hierarchy would have to be privileged over the other. By using a transform function rather than a writing mode property, we are apparently suggesting