Open paregorios opened 7 years ago
Just to add a bit of flesh to my suggestion: The great advantage (perhaps the only advantage) of the lunate sigma is to represent text in a way that does not foreclose alternative understandings of word divisions. The terminal and medial sigma both express particular views of what the word is and what the role of sigma is in the word. Lunate sigma is agnostic, and this seems to me useful in the apparatus. (Whether we ought to use it more broadly is another question.) I do not think this is urgent, however, and without a sense of the time-cost of implementing it, I would hesitate to put any priority on it.
agree useful as described but not urgent. have no opinion about use in DCLP, but want to be sure that we dont produce unintended mess in DDbDP apps
-- Associate Professor in Class ical Studies & History, Duke University | Duke Collaborat ory for Classics Computing | Greek, Roman and Byzantine S tudies | Duke Data Bank of D ocumentary Papyri | papyri.i nfo | people.duke.edu/~jds15http://people.duke.edu/~jds15
On Jun 7, 2017, at 2:02 PM, rogerbagnall notifications@github.com<mailto:notifications@github.com> wrote:
Just to add a bit of flesh to my suggestion: The great advantage (perhaps the only advantage) of the lunate sigma is to represent text in a way that does not foreclose alternative understandings of word divisions. The terminal and medial sigma both express particular views of what the word is and what the role of sigma is in the word. Lunate sigma is agnostic, and this seems to me useful in the apparatus. (Whether we ought to use it more broadly is another question.) I do not think this is urgent, however, and without a sense of the time-cost of implementing it, I would hesitate to put any priority on it.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_DCLP_dclpxsltbox_issues_280-23issuecomment-2D306876685&d=DwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=GWmHrFDZvSPNmQnfB_uD9Q&m=jZvXTmJK0f5TE03VHW_7UPFrRzxs4GqITsyZV2LxMeM&s=h5LbH7ksYQ9E-2bReZ2CyLC2LPDw6HGOqytZloU80ug&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ACBqc2KFUQv4co2IdnzFf8-5F6co750Exdks5sBuXQgaJpZM4NzBIe&d=DwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=GWmHrFDZvSPNmQnfB_uD9Q&m=jZvXTmJK0f5TE03VHW_7UPFrRzxs4GqITsyZV2LxMeM&s=ijq_k8xcxQkNj4pDFSFx7JqsbBf6al3oFToLN1Gop3I&e=.
It's trivial to implement output of lunate sigma in apparatus at this point (for DCLP and DDB together with one brickbat); we've already done the code archaeology. There are other knock-on questions:
I'd suggest we discuss this live with Josh next week. It seems to me that consistency across DCLP and DDBDP would be desirable, but I'm not sure what implications there might be for the latter.
Sure. With the weeks remaining priority here will have to go to basic functional deployment. So, suggest that all things like this one (helpful but not essential) be arranged in rank order. Have the conversion scripts, XSLT, etc ready to go. Then, we can start marching down that list once we are running smoothly.
-- Associate Professor in Class ical Studies & History, Duke University | Duke Collaborat ory for Classics Computing | Greek, Roman and Byzantine S tudies | Duke Data Bank of D ocumentary Papyri | papyri.i nfo | people.duke.edu/~jds15http://people.duke.edu/~jds15
On Jun 8, 2017, at 9:25 AM, rogerbagnall notifications@github.com<mailto:notifications@github.com> wrote:
I'd suggest we discuss this live with Josh next week. It seems to me that consistency across DCLP and DDBDP would be desirable, but I'm not sure what implications there might be for the latter.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_DCLP_dclpxsltbox_issues_280-23issuecomment-2D307102217&d=DwMCaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=GWmHrFDZvSPNmQnfB_uD9Q&m=jtpJwon0Sk7H3NcerRllJOc0RcEJIfBfqkM5SQdRndY&s=_ssuIJsEppVaW2omqyDmZw2kpoS3d-PTSpy4i14MdCE&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ACBqc2Wwbvfi4oF-2DhOtuZ-2D4baSWRNOyMks5sB-5FZDgaJpZM4NzBIe&d=DwMCaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=GWmHrFDZvSPNmQnfB_uD9Q&m=jtpJwon0Sk7H3NcerRllJOc0RcEJIfBfqkM5SQdRndY&s=2uQmT4dqqHSlRJE83mNcmvhpVR_ajpfahBlUMOJH9CA&e=.
Marking "priority: low (defer)" for now, per comment from @jds15
In discussing another issue (#163), @rogerbagnall suggested that we switch from using medial sigma in apparatus (even when we print final sigma in text) to using lunate sigma.
I've created this new issue so we can discuss that suggestion and arrive at a decision about whether to implement and with what urgency.
I've assigned it to @rogerbagnall, @jcowey, @rla2118, @HolgerEssler for discussion (and have also copied @jds15, who has not accepted the invitation to join this issue tracker, so I can't assign him).