Skip to content

Encoding language mix #175

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

Open
juliajbeine wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Encoding language mix #175

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
513eb62
Update dracor.odd
juliajbeine Dec 21, 2025
eec2d0c
Update dracor.odd
juliajbeine Dec 21, 2025
ebf331c
Update dracor.odd
juliajbeine Dec 21, 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
24 changes: 24 additions & 0 deletions dracor.odd
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1501,6 +1501,30 @@
for unknown speakers, see
https://github.com/dracor-org/dracor-schema/issues/106
-->
<div>
<head>Mix of Languages in Text</head>
<p>
A play may feature words, speeches or entire scenes in a
language other than the main language of the play.
Examples for this phenomenon may be found in NeoLatDraCor,
RomDraCor, UDraCor, or YiDraCor. The passages are encoded
as follows. Add the <att>xml:lang</att> attribute to the
highest possible element, e.g. a <gi>sp</gi> or <gi>div</gi>
element.
If there is no element to add the <att>xml:lang</att>
attribute to, use the <gi>foreign</gi> tag to mark up the
respective word or passage. This case may apply to single
words or sentences within a speech, stage direction, or
similar. The <gi>foreign</gi> element is used to mark up
words or passages in another language. For words or passages
in a dialect other than the main language of a play, use the
<gi>distinct</gi> element.
</p>
</div>
<!--
for mix of languages, see
https://github.com/dracor-org/dracor-schema/issues/129
-->
Comment on lines +1524 to +1527
Copy link
Member

@cmil cmil Jan 20, 2026 •
edited
Loading

Choose a reason for hiding this comment

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

Should this perhaps be added as a footnote so that readers of the guidelines could easily access this information?

Copy link
Collaborator Author

@juliajbeine juliajbeine Jan 22, 2026

Choose a reason for hiding this comment

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

@cmil, I could only find links to related issues in this mode, not as footnotes (see line 721, 1693, 1780, 2059, 2086, 3258, 3907, 5431, 5608, 5768). If these links should be better referenced in footnotes, I would change that uniformly for all links.

Copy link
Member

@cmil cmil Jan 23, 2026

Choose a reason for hiding this comment

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

The links you are referring to (I checked the first three) are reminders of open issues. They are not meant to provide more context to the current guidelines and therefore should not be revealed to the guidelines reader. On closer look, your comment refers to issue that this PR intends to solve and should therefore be unnecessary. To fully solve the issue we should, however, add some examples.

Copy link
Collaborator Author

@juliajbeine juliajbeine Jan 23, 2026

Choose a reason for hiding this comment

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

Thank you for the context. I will search for examples and add them.

</div>
</div>
</div>
Expand Down