Skip to content
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.

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

inconsistent spelling of header #1969

Closed
sydb opened this issue Feb 3, 2020 · 13 comments
Closed

inconsistent spelling of header #1969

sydb opened this issue Feb 3, 2020 · 13 comments

Comments

@sydb
Copy link
Member

sydb commented Feb 3, 2020

@martinascholger says we are inconsistent in our use of “TEI Header” vs “TEI header”. A little bit of research says she’s right. Looking at 1b6e0b1, I find

    137 TEI header
     19 TEI Header
      9 TEI-Header
      4 TEI-Headers
      2 TEI headers
      1 TEI header's
      1 TEI Headers

in the content. (I.e., looking only at text() nodes.) If we remove the apostrophes and esses, that reduces to:

    140 TEI header
     20 TEI Header
     13 TEI-Header

Document TCW 20 does not mention how to spell this. But it does refer the reader to the Style Guide, but that link is dead.

@martinascholger
Copy link
Member

Here ist the style guide: http://teic.github.io/TCW/tcw24.html
and it says TEI header

@sydb
Copy link
Member Author

sydb commented Feb 3, 2020

Excellent, thanks!
Can you fix the pointer in TCW 20, and I’ll fix the other spellings?

@martinascholger
Copy link
Member

fixed in TCW20: TEIC/Documentation@c3511ed

sydb added a commit that referenced this issue Feb 3, 2020
Per #1969, changed "TEI Header" to "TEI header" in running prose.
@sydb
Copy link
Member Author

sydb commented Feb 3, 2020

Mostly fixed in 55e9569. German speakers: I did not know what to do with

umfasst Elemente, die innerhalb von TEI Header benutzt werden dürfen und mehrmals auftreten können.

in model.teiHeaderPart.

@martinascholger
Copy link
Member

In German it is "TEI-Header"

sydb added a commit that referenced this issue Feb 6, 2020
@sydb
Copy link
Member Author

sydb commented Feb 6, 2020

So the German description of model.teiHeaderPart should read “umfasst Elemente, die innerhalb von TEI-Header benutzt werden dürfen und mehrmals auftreten können.” then, eh? I will check that in now. Please let me know (or fix directly) if I have that wrong.

@sydb sydb closed this as completed Feb 6, 2020
@duncdrum
Copy link
Contributor

duncdrum commented Feb 6, 2020

innerhalb von des TEI-Header

@sydb sydb reopened this Feb 7, 2020
@martinascholger
Copy link
Member

@sydb I'll change this now

@sydb
Copy link
Member Author

sydb commented Feb 7, 2020

Unless there is an objection from another German speaker (@martinascholger, @peterstadler, @ martinmueller39, and @smjwsk jump to mind) I will plan to delete “von” in a few hours.

@martinascholger
Copy link
Member

"innerhalb des TEI-Headers"

@martinascholger
Copy link
Member

closing with 2c2d3ac

@sydb
Copy link
Member Author

sydb commented Feb 7, 2020

Danke!

@gimsieke
Copy link

gimsieke commented Feb 8, 2020

As a native speaker of German, I agree that genitive is “des Headers”. This is what Duden says, too. Interestingly, Duden also says that the plural of the Germanized word “Header” is “die Headers”. I don’t think this English-style plural is how the German speakers who regularly use “Header” would form the plural. It ought to be “die Header”, as in “der Koffer, des Koffers, die Koffer“. This is an indication that Header has truly been adopted as a German word, at least in the IT community. Virtually no one outside IT uses “Header” in German.

I just noticed that Duden also claims that Header may be either male oder neuter. It’s male in my view. I launched a Twitter poll on that.

@martinascholger martinascholger added this to the Guidelines 3.7.0 milestone Feb 9, 2020
hcayless pushed a commit that referenced this issue Jun 26, 2022
Per #1969, changed "TEI Header" to "TEI header" in running prose.
hcayless pushed a commit that referenced this issue Jun 26, 2022
hcayless pushed a commit that referenced this issue Jun 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants