-
Notifications
You must be signed in to change notification settings - Fork 2
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
euphemism policy? #79
Comments
Any encoding of this type would be on top of the minimal markup schema, so there's no policy in place. Initially, I'm not sure that we'll be able to implement search functionality in the AEME interface, but one can easily open the code and use control+F with the But this does raise a question. If you want to include this information, is there a standard why of encoding it? I think the standard TEI method would be as follows. Assuming God is defined somewhere as <name type="person" ref="#God">Godd</name>, <seg corresp="#God">Min Drihhten</seg> See http://www.tei-c.org/release/doc/tei-p5-doc/en/html/SA.html#SACS. Is there any reason why AEME may need a different or procedure from (or more restrictive procedure than) standard TEI? |
I guess I was being more naive about it. I was envisioning something like this: |
Ah yes, that's that little dance of making the markup semantic. "Min Drihhten" isn't a name, so you don't want to use |
Right. Got it. I think I'll skip the euphemisms for now. |
Do we have a policy for euphemisms and
#bio
references? At the moment I'm looking at Min Drihhten, but I can imagine all other kinds of euphemisms. Bio-tag them or no? (And should we add a line in the Guidelines accordingly?)The text was updated successfully, but these errors were encountered: