Git Product home page Git Product logo

Comments (6)

mmwwah avatar mmwwah commented on July 27, 2024

Agreed that it would be nice to have.

In Junius 1, the titles of the homilies were added by Van Vliet in the early 1660s, so I’m not sure we need to add a second title. Thoughts?

meg

On 11 Sep 2016, at 18:48, Scott Kleinman [email protected] wrote:

Our proposed practice of encoding "whole manuscripts" means that the text does not contain any sort of title in the critical view. So, in Laud Misc. 108, there will be no visible transition between vitae except for a line break or whatever CSS styling accompanies the . That's fine for the diplomatic view, but for the critical view it would be nice to have something inline so that no convoluted processing is need to grab the title from the teiHeader. From the TEI Guidelines, the only thing that makes semantic sense to me is @n. So the code would look something like this:

... ... This works just fine in my test viewer. Any reason why I shouldn't go ahead and add it to the encoding Guidelines?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub #92, or mute the thread https://github.com/notifications/unsubscribe-auth/AHcqCfD3rE8SKa8XkQJKakvOS18fEOXbks5qpIUwgaJpZM4J6IHA.

from aeme.

scottkleinman avatar scottkleinman commented on July 27, 2024

Actually, I think we still need @n. Van Vliet's titles actually appear in the manuscript, so they should be encoded in the forme work. At present, that is only displayed in the diplomatic view. So we'll still need a separate way of displaying modern titles (even if they are taken from Van Vliet) in the critical view.

from aeme.

mmwwah avatar mmwwah commented on July 27, 2024

Oh, okay. I’d forgotten that forme work doesn’t appear in the CritV. I’ll get on it within the next couple of weeks, unless Sharon or Dokim mounts an objection.

meg

On 11 Sep 2016, at 19:28, Scott Kleinman [email protected] wrote:

Actually, I think we still need @n. Van Vliet's titles actually appear in the manuscript, so they should be encoded in the forme work. At present, that is only displayed in the diplomatic view. So we'll still need a separate way of displaying modern titles (even if they are taken from Van Vliet) in the critical view.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub #92 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/AHcqCc6e3t20GV_ULaJjojn_zs1k00T2ks5qpI6agaJpZM4J6IHA.

from aeme.

dorothyk98 avatar dorothyk98 commented on July 27, 2024

Works for me.
-Dorothy

On Sun, Sep 11, 2016 at 7:31 PM, mmwwah [email protected] wrote:

Oh, okay. I’d forgotten that forme work doesn’t appear in the CritV. I’ll
get on it within the next couple of weeks, unless Sharon or Dokim mounts an
objection.

meg

On 11 Sep 2016, at 19:28, Scott Kleinman [email protected]
wrote:

Actually, I think we still need @n. Van Vliet's titles actually appear
in the manuscript, so they should be encoded in the forme work. At present,
that is only displayed in the diplomatic view. So we'll still need a
separate way of displaying modern titles (even if they are taken from Van
Vliet) in the critical view.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub <https://github.com/
/issues/92#issuecomment-246212012>, or mute the thread <
https://github.com/notifications/unsubscribe-auth/AHcqCc6e3t20GV_ULaJjojn_
zs1k00T2ks5qpI6agaJpZM4J6IHA>.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#92 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIO1tQt1RzEgXxtN5eN5oWN_oP6sh2S8ks5qpI80gaJpZM4J6IHA
.

from aeme.

skgoetz avatar skgoetz commented on July 27, 2024

For somewhat less tag/attr abuse, how about <div1><title type="supplied">Havelok the Dane</title> [...] </div1>

from aeme.

scottkleinman avatar scottkleinman commented on July 27, 2024

Thanks, Sharon. title is actually much better. Let's go with that. I'm so used to using it for bibliographical entries that I forgot about its existence.

However, it raises another question about features like Van Vliet's titles. Let's say you had something like:

<div1>
    <title resp="#modernEditor">I'm  a modern editorial title</title>
    <pb/>
    <fw type="guideWords" resp="#VanVliet" place="topCenter">I'm a title written in the manuscript</fw>
    ...
</div1>

This will render the title element in the critical view and the fw element in the diplomatic view. Personally, I'm not a fan of the @type categories we have inherited from PPEA. It might be better to use title inside fw for this. Doing so makes rendering the distinction between diplomatic and critical titles a bit more difficult, but not impossible. But then what to put in fw@type? Any ideas about how we might improve on the taxonomy for this attribute?

from aeme.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.