Skip to content

<foreign> clarifications and more alternatives #2814

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
raffazizzi wants to merge 4 commits into
base: dev
Choose a base branch
from
Draft

<foreign> clarifications and more alternatives #2814

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
dcba32d
Adjusted remarks and other language to offer more alternatives to <fo…
raffazizzi Sep 16, 2025
74c4a28
fixed typo
raffazizzi Sep 16, 2025
43d1e8e
slightl improvement to prose
raffazizzi Sep 17, 2025
62a116b
Change foreign words to words in another language for consistency wit…
trishaoconnor Sep 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions P5/Source/Guidelines/en/BIB-Bibliography.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -595,6 +595,36 @@
<editor>Guerard, Françoise</editor>. <title>Le Dictionnaire de Notre Temps</title>, ed.
<pubPlace>Paris</pubPlace>: <publisher>Hachette</publisher>, <date>1990</date>
</bibl>
<biblStruct xml:id="COHQHF-eg-kbl">
<analytic>
<editor>
<forename>Olivia</forename>
<surname>DeBarnard</surname>
</editor>
<editor>
<forename>Emma</forename>
<surname>Bilski</surname>
</editor>
<editor>
<forename>Leila</forename>
<surname>Blackbird</surname>
</editor>
<editor>
<forename>Jessica Marie</forename>
<surname>Johnson</surname>
</editor>
<title level="a">Guillermo, Catalina, and Her Children</title>
<title level="a">Kinship &amp; Longing: Keywords for Black Louisiana</title>
<idno type="DOI">10.55520/YSF9HQNH</idno>
</analytic>
<monogr>
<title level="j">Scholarly Editing</title>
<imprint>
<biblScope unit="vol">41</biblScope>
<date>2024</date>
</imprint>
</monogr>
</biblStruct>

<!--H-->

Expand Down
36 changes: 27 additions & 9 deletions P5/Source/Guidelines/en/CO-CoreElements.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -428,7 +428,7 @@ phenomenon and alternate approaches to encoding it, this section
describes ways of encoding the following textual features, all
of which are conventionally rendered using some kind of highlighting:
<list rend="bulleted">
<item>emphasis, foreign words and other linguistically distinct uses
<item>emphasis, words in other languages or other linguistically distinct uses
of highlighting</item>
<item>representation of speech and thought, quotation, etc.</item>
<item>technical terms, glosses, etc.</item></list>
Expand Down Expand Up @@ -467,7 +467,7 @@ places in older texts, editorial corrections or additions, etc.</item></list>
</p>
<p>The textual functions indicated by highlighting may not be rendered
consistently in different parts of a text or in different texts. (For
example, a foreign word may appear in italics if the surrounding text is
example, a word in another language may appear in italics if the surrounding text is
in roman, but in roman if the surrounding text is in italics.) For this
reason, these Guidelines distinguish between the encoding of rendering
itself and the encoding of the underlying feature expressed by it.
Expand Down Expand Up @@ -543,11 +543,11 @@ which are not discussed in this section include <gi>title</gi>
(discussed in section <ptr target="#COBI"/>) and <gi>name</gi> (discussed
in section <ptr target="#CONARS"/>).
</p></div>
<div type="div3" xml:id="COHQH"><head>Emphasis, Foreign Words, and Unusual Language</head>
<div type="div3" xml:id="COHQH"><head>Emphasis, Words in Other Languages, and Unusual Language</head>
<p>This subsection discusses the following elements:
<specList><specDesc key="foreign"/><specDesc key="emph"/><specDesc key="distinct"/></specList>
These elements are all members of the <ident type="class">model.emphLike</ident> class. </p>
<div type="div4" xml:id="COHQHF"><head>Foreign Words or Expressions</head>
<div type="div4" xml:id="COHQHF"><head>Words or Expressions in Other Languages</head>
<p>Words or phrases which are not in the main language of the text
should be tagged as such, at least where the fact is indicated in the
text. Where the word or phrase concerned is already distinguished from
Expand All @@ -558,15 +558,33 @@ specify additionally that its language distinguishes it from the
surrounding text. Any element in the TEI scheme may take an
<att>xml:lang</att> attribute, which specifies both the writing system
and the language used by its content (see sections <ptr target="#STGAla"/> and <ptr target="#CHSH"/> for discussion of this
attribute and its values respectively). Where there is no other
applicable element, the element <gi>foreign</gi> may be used to
provide a peg onto which the <att>xml:lang</att> may be attached.
attribute and its values respectively).
<egXML xmlns="http://www.tei-c.org/ns/Examples" xml:id="COHQHF-egXML-me" source="#COHQHF-eg-5"><q>Aren't you confusing <foreign xml:lang="la">post hoc</foreign> with <foreign xml:lang="la">propter
hoc</foreign>?</q> said the Bee Master. <q>Wax-moth only succeed when
weak bees let them in.</q></egXML>
Where there is no other
applicable element, the element <gi>seg</gi> may be used to
provide a peg onto which the <att>xml:lang</att> may be attached.
</p>

<p>The <gi>foreign</gi> element should not be used in multilingual texts or texts originating from multilingual contexts because the words
in question may not be <soCalled>foreign</soCalled> to their intended audience.
In these cases it is also preferable to use <gi>seg</gi> with the appropriate <att>xml:lang</att>, or <gi>emph</gi> if the text is emphasized.</p>
<p>The following examples originate from bilingual contexts, namely English and Scots and Spanish and French.
<!-- TODO: add source -->
<egXML xmlns="http://www.tei-c.org/ns/Examples" xml:id="COHQF-egXML-aa" >
where there was "<del>a</del> <seg xml:lang="sco">Deel a Sole</seg> upon the Shoe"
</egXML>
<egXML xmlns="http://www.tei-c.org/ns/Examples" xml:id="COHQF-egXML-kbl" source="#COHQHF-eg-kbl">

@ebeshero ebeshero Sep 16, 2025

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect example!

<closer xml:lang="es">y firmo su Mrd. Con las demas partes Expressadas. de que yo el Es.<hi rend="sup">no</hi> Doy fe
<lb/>Derneville Fran.<hi rend="sup">co</hi> Broutin
<lb/>D Leonardo Mazange Frãn.<hi rend="sup">co</hi> Liotau
<lb/>Louis Lessier <emph xml:lang="fr">fils</emph>
</closer>
</egXML>
</p>

<p>The <gi>foreign</gi> element should not be used to represent foreign words
<p>The <gi>foreign</gi> element should additionally not be used to represent words in another language
which are mentioned or glossed within the text: for these use the
appropriate element from section <ptr target="#COHTG"/> below. Compare the
following example sentences:
Expand Down Expand Up @@ -600,7 +618,7 @@ indicated by the use of underlining. As the following examples
demonstrate, an encoder may choose whether or not to make explicit the
particular type of rendition associated with the emphasis. If a source
text consistently renders a particular feature (e.g. emphasis or words
in foreign languages) in a particular way, the rendering associated
in a different language) in a particular way, the rendering associated
with that feature may be described in the TEI header using the
<gi>rendition</gi> element. The <att>rend</att>,
<att>rendition</att>, or <att>style</att> attributes may then be used
Expand Down
5 changes: 5 additions & 0 deletions P5/Source/Specs/foreign.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,8 +55,13 @@ Ce ne seroyt que bon que nous rendissiez noz cloches...</egXML>
the phrase or words concerned. The global <att>xml:lang</att> attribute
should be used in preference to this element where it is intended to mark
the language of the whole of some text element.</p>
<p>In multilingual texts, or texts originating from multilingual contexts, this element may not be appropriate
for marking words or phrases as belonging to some language other than that of the
immediately surrounding text. The text in question may not be <soCalled>foreign</soCalled> to its intended audience.
In these cases it is preferable to use <gi>seg</gi> with the appropriate <att>xml:lang</att>, or <gi>emph</gi> if the text is emphasized.</p>

@tuurma tuurma Jan 6, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not suggest the use of distinct here, if the word or phrase is linguistically distinct, why muddle things up with the generic seg or imply emphasis where it is a separate characteristic (a phrase may be both linguistically distinct and emphasized)?

@lb42 lb42 Jan 6, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am pretty sure i also suggested using distinct when this issue was first raised

@lb42 lb42 Jan 6, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am pretty sure i also suggested using distinct when this issue was first raised

<p>The <gi>distinct</gi> element may be used to identify phrases belonging to
sublanguages or registers not generally regarded as true languages.</p>

</remarks>
<remarks versionDate="2007-06-12" xml:lang="fr">
<p>L'attribut global <att>xml:lang</att> doit être fourni dans cet élément pour
Expand Down