Thanks for Ruby feedback

older
More NVDL issues: Spec files not...

Martin Holmes

3 Feb 2021 3 Feb '21

4:58 p.m.

Hi all, Thanks for the feedback on the location for the Ruby prose. The consensus is clear -- it should be in core -- and the comments suggest that the most appropriate approach will be to integrated it with the content relating to glosses, which is currently in 3.3.4, "Terms, Glosses, Equivalents, and Descriptions". That sub-subsection is already quite long, so what I propose to attempt is this: Take 3.3.4 "Terms, Glosses, Equivalents, and Descriptions" and 3.3.5 "Some Further Examples" and make them into a new subsection (i.e. one level higher), which will become 3.4. Title the new section "Terms, Glosses, Equivalents, Descriptions, and Ruby". (JJ suggests that terms belongs elsewhere, but that would be a major reorg, and I don't think we have time for that right now.) Create subsections: 3.4.1 "Terms and Glosses" covering the first part of what is now 3.3.4. This would also include the "Further Examples" bit, which is really an extension of this. 3.4.2 "Ruby Annotations" containing the new prose already proposed. 3.4.3 "Equivalents and Descriptions" containing the part of what is now 3.3.4 which discusses altIdent, desc, and equiv; I think this is a different topic, really, from glossing terms. I'm doing this work in a separate branch: https://github.com/TEIC/TEI/tree/issue-2054-ruby which I'll merge dev into steadily as I go, to minimize later merge conflicts. I'll also set up a build job for this branch on my Jenkins when the initial work is done. The time is relatively short, but I think we can get there before the freeze. I'll post the meat of this on the ticket too, for the record. Cheers, Martin -- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca

Show replies by date

Martin Holmes

3 Feb 3 Feb

6:56 p.m.

New subject: Ruby Core chapter now built

Hi all, A first draft of the reorganized version of the CO chapter incorporating the new Ruby section can now be seen here: https://teijenkins.hcmc.uvic.ca/job/TEIP5-issue-2054-ruby/lastSuccessfulBuil... Please take a look and let me know what you think. I haven't yet added links/refs from other chapters because I want to make sure the ids etc. are stable before I do that. Since Nagasaki-sensei has kindly provided translations of the glosses and descs on the Spec pages, the 日本語 links at the bottom of those pages will hopefully be useful. Cheers, Martin On 2021-02-03 7:58 a.m., Martin Holmes wrote:

...

Hi all,

Thanks for the feedback on the location for the Ruby prose. The consensus is clear -- it should be in core -- and the comments suggest that the most appropriate approach will be to integrated it with the content relating to glosses, which is currently in 3.3.4, "Terms, Glosses, Equivalents, and Descriptions". That sub-subsection is already quite long, so what I propose to attempt is this:

Take 3.3.4 "Terms, Glosses, Equivalents, and Descriptions" and 3.3.5 "Some Further Examples" and make them into a new subsection (i.e. one level higher), which will become 3.4.

Title the new section "Terms, Glosses, Equivalents, Descriptions, and Ruby". (JJ suggests that terms belongs elsewhere, but that would be a major reorg, and I don't think we have time for that right now.)

Create subsections:

3.4.1 "Terms and Glosses" covering the first part of what is now 3.3.4. This would also include the "Further Examples" bit, which is really an extension of this.

3.4.2 "Ruby Annotations" containing the new prose already proposed.

3.4.3 "Equivalents and Descriptions" containing the part of what is now 3.3.4 which discusses altIdent, desc, and equiv; I think this is a different topic, really, from glossing terms.

I'm doing this work in a separate branch:

https://github.com/TEIC/TEI/tree/issue-2054-ruby

which I'll merge dev into steadily as I go, to minimize later merge conflicts. I'll also set up a build job for this branch on my Jenkins when the initial work is done.

The time is relatively short, but I think we can get there before the freeze.

I'll post the meat of this on the ticket too, for the record.

Cheers, Martin

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca

Janelle Jenstad

7:18 p.m.

New subject: Ruby Core chapter now built

Quick observation: This parenthentical phrase is meant to be a note on the first use of pinyin, I think: " (pinyin píngzi = bottle, taken from Wikipedia.)" It's right after this egXML: https://teijenkins.hcmc.uvic.ca/job/TEIP5-issue-2054-ruby/lastSuccessfulBuil.... Janelle Jenstad, Associate Professor, Department of English, University of Victoria Director, Map of Early Modern London; Director, Linked Early Modern Drama Online Coordinating Platform Editor, Digital Renaissance Editions Email: jenstad@uvic.ca, lemdo@uvic.ca, or london@uvic.ca -----Original Message----- From: Tei-council On Behalf Of Martin Holmes Sent: February 3, 2021 9:57 AM To: tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Subject: [Tei-council] Ruby Core chapter now built Notice: This message was sent from outside the University of Victoria email system but is claiming to be from UVic. Please be cautious with links, attachments, and sensitive information. Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links and sensitive information. Hi all, A first draft of the reorganized version of the CO chapter incorporating the new Ruby section can now be seen here: https://teijenkins.hcmc.uvic.ca/job/TEIP5-issue-2054-ruby/lastSuccessfulBuil... Please take a look and let me know what you think. I haven't yet added links/refs from other chapters because I want to make sure the ids etc. are stable before I do that. Since Nagasaki-sensei has kindly provided translations of the glosses and descs on the Spec pages, the 日本語 links at the bottom of those pages will hopefully be useful. Cheers, Martin On 2021-02-03 7:58 a.m., Martin Holmes wrote:

...

Hi all,

Thanks for the feedback on the location for the Ruby prose. The consensus is clear -- it should be in core -- and the comments suggest that the most appropriate approach will be to integrated it with the content relating to glosses, which is currently in 3.3.4, "Terms, Glosses, Equivalents, and Descriptions". That sub-subsection is already quite long, so what I propose to attempt is this:

Take 3.3.4 "Terms, Glosses, Equivalents, and Descriptions" and 3.3.5 "Some Further Examples" and make them into a new subsection (i.e. one level higher), which will become 3.4.

Title the new section "Terms, Glosses, Equivalents, Descriptions, and Ruby". (JJ suggests that terms belongs elsewhere, but that would be a major reorg, and I don't think we have time for that right now.)

Create subsections:

3.4.1 "Terms and Glosses" covering the first part of what is now 3.3.4. This would also include the "Further Examples" bit, which is really an extension of this.

3.4.2 "Ruby Annotations" containing the new prose already proposed.

3.4.3 "Equivalents and Descriptions" containing the part of what is now 3.3.4 which discusses altIdent, desc, and equiv; I think this is a different topic, really, from glossing terms.

I'm doing this work in a separate branch:

https://github.com/TEIC/TEI/tree/issue-2054-ruby

which I'll merge dev into steadily as I go, to minimize later merge conflicts. I'll also set up a build job for this branch on my Jenkins when the initial work is done.

The time is relatively short, but I think we can get there before the freeze.

I'll post the meat of this on the ticket too, for the record.

Cheers, Martin

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

Martin Holmes

7:20 p.m.

New subject: Ruby Core chapter now built

I think the p of Pinyin should be capital, so it's a full sentence; other than that, I think it's OK. Did you mean that it should be a footnote? Cheers, Martin On 2021-02-03 10:18 a.m., Janelle Jenstad wrote:

...

Quick observation:

This parenthentical phrase is meant to be a note on the first use of pinyin, I think: " (pinyin píngzi = bottle, taken from Wikipedia.)" It's right after this egXML: https://teijenkins.hcmc.uvic.ca/job/TEIP5-issue-2054-ruby/lastSuccessfulBuil....

Janelle Jenstad, Associate Professor, Department of English, University of Victoria Director, Map of Early Modern London; Director, Linked Early Modern Drama Online Coordinating Platform Editor, Digital Renaissance Editions Email: jenstad@uvic.ca, lemdo@uvic.ca, or london@uvic.ca

-----Original Message----- From: Tei-council On Behalf Of Martin Holmes Sent: February 3, 2021 9:57 AM To: tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Subject: [Tei-council] Ruby Core chapter now built

Notice: This message was sent from outside the University of Victoria email system but is claiming to be from UVic. Please be cautious with links, attachments, and sensitive information.

Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links and sensitive information.

Hi all,

A first draft of the reorganized version of the CO chapter incorporating the new Ruby section can now be seen here:

https://teijenkins.hcmc.uvic.ca/job/TEIP5-issue-2054-ruby/lastSuccessfulBuil...

Please take a look and let me know what you think. I haven't yet added links/refs from other chapters because I want to make sure the ids etc. are stable before I do that.

Since Nagasaki-sensei has kindly provided translations of the glosses and descs on the Spec pages, the 日本語 links at the bottom of those pages will hopefully be useful.

Cheers, Martin

On 2021-02-03 7:58 a.m., Martin Holmes wrote:

...
Hi all,

Thanks for the feedback on the location for the Ruby prose. The consensus is clear -- it should be in core -- and the comments suggest that the most appropriate approach will be to integrated it with the content relating to glosses, which is currently in 3.3.4, "Terms, Glosses, Equivalents, and Descriptions". That sub-subsection is already quite long, so what I propose to attempt is this:

Take 3.3.4 "Terms, Glosses, Equivalents, and Descriptions" and 3.3.5 "Some Further Examples" and make them into a new subsection (i.e. one level higher), which will become 3.4.

Title the new section "Terms, Glosses, Equivalents, Descriptions, and Ruby". (JJ suggests that terms belongs elsewhere, but that would be a major reorg, and I don't think we have time for that right now.)

Create subsections:

3.4.1 "Terms and Glosses" covering the first part of what is now 3.3.4. This would also include the "Further Examples" bit, which is really an extension of this.

3.4.2 "Ruby Annotations" containing the new prose already proposed.

3.4.3 "Equivalents and Descriptions" containing the part of what is now 3.3.4 which discusses altIdent, desc, and equiv; I think this is a different topic, really, from glossing terms.

I'm doing this work in a separate branch:

https://github.com/TEIC/TEI/tree/issue-2054-ruby

which I'll merge dev into steadily as I go, to minimize later merge conflicts. I'll also set up a build job for this branch on my Jenkins when the initial work is done.

The time is relatively short, but I think we can get there before the freeze.

I'll post the meat of this on the ticket too, for the record.

Cheers, Martin

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca

Janelle Jenstad

7:26 p.m.

New subject: Ruby Core chapter now built

Oh, I get it now. It's meant to be an English gloss on the preceding Pinyin example. It's just out of step with the pattern already established. All the others have the English gloss embedded in the introduction to the <egXML>. How about: "Here is a similar example from Taiwan using Bopomofo (Pinyin píngzi = bottle, taken from Wikipedia):" -- followed by the <egXML>. J. Janelle Jenstad, Associate Professor, Department of English, University of Victoria Director, Map of Early Modern London; Director, Linked Early Modern Drama Online Coordinating Platform Editor, Digital Renaissance Editions Email: jenstad@uvic.ca, lemdo@uvic.ca, or london@uvic.ca -----Original Message----- From: Martin Holmes Sent: February 3, 2021 10:21 AM To: Janelle Jenstad ; tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Subject: Re: [Tei-council] Ruby Core chapter now built I think the p of Pinyin should be capital, so it's a full sentence; other than that, I think it's OK. Did you mean that it should be a footnote? Cheers, Martin On 2021-02-03 10:18 a.m., Janelle Jenstad wrote:

...

Quick observation:

This parenthentical phrase is meant to be a note on the first use of pinyin, I think: " (pinyin píngzi = bottle, taken from Wikipedia.)" It's right after this egXML: https://teijenkins.hcmc.uvic.ca/job/TEIP5-issue-2054-ruby/lastSuccessfulBuil....

Janelle Jenstad, Associate Professor, Department of English, University of Victoria Director, Map of Early Modern London; Director, Linked Early Modern Drama Online Coordinating Platform Editor, Digital Renaissance Editions Email: jenstad@uvic.ca, lemdo@uvic.ca, or london@uvic.ca

-----Original Message----- From: Tei-council On Behalf Of Martin Holmes Sent: February 3, 2021 9:57 AM To: tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Subject: [Tei-council] Ruby Core chapter now built

Notice: This message was sent from outside the University of Victoria email system but is claiming to be from UVic. Please be cautious with links, attachments, and sensitive information.

Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links and sensitive information.

Hi all,

A first draft of the reorganized version of the CO chapter incorporating the new Ruby section can now be seen here:

<https://teijenkins.hcmc.uvic.ca/job/TEIP5-issue-2054-ruby/lastSuccess fulBuild/artifact/P5/Guidelines-web/en/html/CO.html>

Please take a look and let me know what you think. I haven't yet added links/refs from other chapters because I want to make sure the ids etc. are stable before I do that.

Since Nagasaki-sensei has kindly provided translations of the glosses and descs on the Spec pages, the 日本語 links at the bottom of those pages will hopefully be useful.

Cheers, Martin

On 2021-02-03 7:58 a.m., Martin Holmes wrote:

...
Hi all,

Thanks for the feedback on the location for the Ruby prose. The consensus is clear -- it should be in core -- and the comments suggest that the most appropriate approach will be to integrated it with the content relating to glosses, which is currently in 3.3.4, "Terms, Glosses, Equivalents, and Descriptions". That sub-subsection is already quite long, so what I propose to attempt is this:

Take 3.3.4 "Terms, Glosses, Equivalents, and Descriptions" and 3.3.5 "Some Further Examples" and make them into a new subsection (i.e. one level higher), which will become 3.4.

Title the new section "Terms, Glosses, Equivalents, Descriptions, and Ruby". (JJ suggests that terms belongs elsewhere, but that would be a major reorg, and I don't think we have time for that right now.)

Create subsections:

3.4.1 "Terms and Glosses" covering the first part of what is now 3.3.4. This would also include the "Further Examples" bit, which is really an extension of this.

3.4.2 "Ruby Annotations" containing the new prose already proposed.

3.4.3 "Equivalents and Descriptions" containing the part of what is now 3.3.4 which discusses altIdent, desc, and equiv; I think this is a different topic, really, from glossing terms.

I'm doing this work in a separate branch:

https://github.com/TEIC/TEI/tree/issue-2054-ruby

which I'll merge dev into steadily as I go, to minimize later merge conflicts. I'll also set up a build job for this branch on my Jenkins when the initial work is done.

The time is relatively short, but I think we can get there before the freeze.

I'll post the meat of this on the ticket too, for the record.

Cheers, Martin

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca

Martin Holmes

7:26 p.m.

New subject: Ruby Core chapter now built

Ah, better idea. Will do. Cheers, Martin On 2021-02-03 10:26 a.m., Janelle Jenstad wrote:

...

Oh, I get it now. It's meant to be an English gloss on the preceding Pinyin example. It's just out of step with the pattern already established. All the others have the English gloss embedded in the introduction to the <egXML>.

How about: "Here is a similar example from Taiwan using Bopomofo (Pinyin píngzi = bottle, taken from Wikipedia):" -- followed by the <egXML>.

J.

Janelle Jenstad, Associate Professor, Department of English, University of Victoria Director, Map of Early Modern London; Director, Linked Early Modern Drama Online Coordinating Platform Editor, Digital Renaissance Editions Email: jenstad@uvic.ca, lemdo@uvic.ca, or london@uvic.ca

-----Original Message----- From: Martin Holmes Sent: February 3, 2021 10:21 AM To: Janelle Jenstad ; tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Subject: Re: [Tei-council] Ruby Core chapter now built

I think the p of Pinyin should be capital, so it's a full sentence; other than that, I think it's OK. Did you mean that it should be a footnote?

Cheers, Martin

On 2021-02-03 10:18 a.m., Janelle Jenstad wrote:

...
Quick observation:

This parenthentical phrase is meant to be a note on the first use of pinyin, I think: " (pinyin píngzi = bottle, taken from Wikipedia.)" It's right after this egXML: https://teijenkins.hcmc.uvic.ca/job/TEIP5-issue-2054-ruby/lastSuccessfulBuil....

Janelle Jenstad, Associate Professor, Department of English, University of Victoria Director, Map of Early Modern London; Director, Linked Early Modern Drama Online Coordinating Platform Editor, Digital Renaissance Editions Email: jenstad@uvic.ca, lemdo@uvic.ca, or london@uvic.ca

-----Original Message----- From: Tei-council On Behalf Of Martin Holmes Sent: February 3, 2021 9:57 AM To: tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Subject: [Tei-council] Ruby Core chapter now built

Notice: This message was sent from outside the University of Victoria email system but is claiming to be from UVic. Please be cautious with links, attachments, and sensitive information.

Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links and sensitive information.

Hi all,

A first draft of the reorganized version of the CO chapter incorporating the new Ruby section can now be seen here:

<https://teijenkins.hcmc.uvic.ca/job/TEIP5-issue-2054-ruby/lastSuccess fulBuild/artifact/P5/Guidelines-web/en/html/CO.html>

Please take a look and let me know what you think. I haven't yet added links/refs from other chapters because I want to make sure the ids etc. are stable before I do that.

Since Nagasaki-sensei has kindly provided translations of the glosses and descs on the Spec pages, the 日本語 links at the bottom of those pages will hopefully be useful.

Cheers, Martin

On 2021-02-03 7:58 a.m., Martin Holmes wrote:

...
Hi all,

Thanks for the feedback on the location for the Ruby prose. The consensus is clear -- it should be in core -- and the comments suggest that the most appropriate approach will be to integrated it with the content relating to glosses, which is currently in 3.3.4, "Terms, Glosses, Equivalents, and Descriptions". That sub-subsection is already quite long, so what I propose to attempt is this:

Take 3.3.4 "Terms, Glosses, Equivalents, and Descriptions" and 3.3.5 "Some Further Examples" and make them into a new subsection (i.e. one level higher), which will become 3.4.

Title the new section "Terms, Glosses, Equivalents, Descriptions, and Ruby". (JJ suggests that terms belongs elsewhere, but that would be a major reorg, and I don't think we have time for that right now.)

Create subsections:

3.4.1 "Terms and Glosses" covering the first part of what is now 3.3.4. This would also include the "Further Examples" bit, which is really an extension of this.

3.4.2 "Ruby Annotations" containing the new prose already proposed.

3.4.3 "Equivalents and Descriptions" containing the part of what is now 3.3.4 which discusses altIdent, desc, and equiv; I think this is a different topic, really, from glossing terms.

I'm doing this work in a separate branch:

https://github.com/TEIC/TEI/tree/issue-2054-ruby

which I'll merge dev into steadily as I go, to minimize later merge conflicts. I'll also set up a build job for this branch on my Jenkins when the initial work is done.

The time is relatively short, but I think we can get there before the freeze.

I'll post the meat of this on the ticket too, for the record.

Cheers, Martin

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca

Scholger, Martina (martina.scholger＠uni-graz.at)

4 Feb 4 Feb

4:20 p.m.

New subject: Ruby Core chapter now built

Hi Martin, Thanks - looks good to me. Some quick comments: * For the title of the section I would follow the order of the sub-sections. The title is currently "Terms, Glosses, Equivalents, Descriptions, and Ruby Annotations". The order of the sub-sections is Terms and Glosses, (Further Examples), Ruby Annotations, and Equivalents and Descriptions. And, I wonder if "Some Further Examples" should be 3.4.1.1 instead of 3.4.2? * The note needs to be deleted: [NOTE: if proposed layout/@rubyPlace is implemented, it should be explained here.] * In "We could also use a standoff approach with anchors and pointers:" anchor could be a link to the specs. * <rt> and <rb> specs: "contained by" is empty * <rt> specs: in the example there is a superfluous space in <rb> and <rt> Best, Martina -----Ursprüngliche Nachricht----- Von: Tei-council Im Auftrag von Martin Holmes Gesendet: Mittwoch, 3. Februar 2021 19:27 An: Janelle Jenstad ; tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Betreff: Re: [Tei-council] Ruby Core chapter now built Ah, better idea. Will do. Cheers, Martin On 2021-02-03 10:26 a.m., Janelle Jenstad wrote:

...

Oh, I get it now. It's meant to be an English gloss on the preceding Pinyin example. It's just out of step with the pattern already established. All the others have the English gloss embedded in the introduction to the <egXML>.

How about: "Here is a similar example from Taiwan using Bopomofo (Pinyin píngzi = bottle, taken from Wikipedia):" -- followed by the <egXML>.

J.

Janelle Jenstad, Associate Professor, Department of English, University of Victoria Director, Map of Early Modern London; Director, Linked Early Modern Drama Online Coordinating Platform Editor, Digital Renaissance Editions Email: jenstad@uvic.ca, lemdo@uvic.ca, or london@uvic.ca

-----Original Message----- From: Martin Holmes Sent: February 3, 2021 10:21 AM To: Janelle Jenstad ; tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Subject: Re: [Tei-council] Ruby Core chapter now built

I think the p of Pinyin should be capital, so it's a full sentence; other than that, I think it's OK. Did you mean that it should be a footnote?

Cheers, Martin

On 2021-02-03 10:18 a.m., Janelle Jenstad wrote:

...
Quick observation:

This parenthentical phrase is meant to be a note on the first use of pinyin, I think: " (pinyin píngzi = bottle, taken from Wikipedia.)" It's right after this egXML: https://teijenkins.hcmc.uvic.ca/job/TEIP5-issue-2054-ruby/lastSuccessfulBuil....

Janelle Jenstad, Associate Professor, Department of English, University of Victoria Director, Map of Early Modern London; Director, Linked Early Modern Drama Online Coordinating Platform Editor, Digital Renaissance Editions Email: jenstad@uvic.ca, lemdo@uvic.ca, or london@uvic.ca

-----Original Message----- From: Tei-council On Behalf Of Martin Holmes Sent: February 3, 2021 9:57 AM To: tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Subject: [Tei-council] Ruby Core chapter now built

Notice: This message was sent from outside the University of Victoria email system but is claiming to be from UVic. Please be cautious with links, attachments, and sensitive information.

Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links and sensitive information.

Hi all,

A first draft of the reorganized version of the CO chapter incorporating the new Ruby section can now be seen here:

<https://teijenkins.hcmc.uvic.ca/job/TEIP5-issue-2054-ruby/lastSucces s fulBuild/artifact/P5/Guidelines-web/en/html/CO.html>

Please take a look and let me know what you think. I haven't yet added links/refs from other chapters because I want to make sure the ids etc. are stable before I do that.

Since Nagasaki-sensei has kindly provided translations of the glosses and descs on the Spec pages, the 日本語 links at the bottom of those pages will hopefully be useful.

Cheers, Martin

On 2021-02-03 7:58 a.m., Martin Holmes wrote:

...
Hi all,

Thanks for the feedback on the location for the Ruby prose. The consensus is clear -- it should be in core -- and the comments suggest that the most appropriate approach will be to integrated it with the content relating to glosses, which is currently in 3.3.4, "Terms, Glosses, Equivalents, and Descriptions". That sub-subsection is already quite long, so what I propose to attempt is this:

Take 3.3.4 "Terms, Glosses, Equivalents, and Descriptions" and 3.3.5 "Some Further Examples" and make them into a new subsection (i.e. one level higher), which will become 3.4.

Title the new section "Terms, Glosses, Equivalents, Descriptions, and Ruby". (JJ suggests that terms belongs elsewhere, but that would be a major reorg, and I don't think we have time for that right now.)

Create subsections:

3.4.1 "Terms and Glosses" covering the first part of what is now 3.3.4. This would also include the "Further Examples" bit, which is really an extension of this.

3.4.2 "Ruby Annotations" containing the new prose already proposed.

3.4.3 "Equivalents and Descriptions" containing the part of what is now 3.3.4 which discusses altIdent, desc, and equiv; I think this is a different topic, really, from glossing terms.

I'm doing this work in a separate branch:

https://github.com/TEIC/TEI/tree/issue-2054-ruby

which I'll merge dev into steadily as I go, to minimize later merge conflicts. I'll also set up a build job for this branch on my Jenkins when the initial work is done.

The time is relatively short, but I think we can get there before the freeze.

I'll post the meat of this on the ticket too, for the record.

Cheers, Martin

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca

Martin Holmes

4:34 p.m.

New subject: Ruby Core chapter now built

Thanks Martina -- all good points. The most worrying bit is the empty contained-by thing... Cheers, Martin On 2021-02-04 7:20 a.m., Scholger, Martina (martina.scholger@uni-graz.at) wrote:

...

Hi Martin,

Thanks - looks good to me.

Some quick comments: * For the title of the section I would follow the order of the sub-sections. The title is currently "Terms, Glosses, Equivalents, Descriptions, and Ruby Annotations". The order of the sub-sections is Terms and Glosses, (Further Examples), Ruby Annotations, and Equivalents and Descriptions. And, I wonder if "Some Further Examples" should be 3.4.1.1 instead of 3.4.2?

* The note needs to be deleted: [NOTE: if proposed layout/@rubyPlace is implemented, it should be explained here.]

* In "We could also use a standoff approach with anchors and pointers:" anchor could be a link to the specs.

* <rt> and <rb> specs: "contained by" is empty

* <rt> specs: in the example there is a superfluous space in <rb> and <rt>

Best, Martina

-----Ursprüngliche Nachricht----- Von: Tei-council Im Auftrag von Martin Holmes Gesendet: Mittwoch, 3. Februar 2021 19:27 An: Janelle Jenstad ; tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Betreff: Re: [Tei-council] Ruby Core chapter now built

Ah, better idea. Will do.

Cheers, Martin

On 2021-02-03 10:26 a.m., Janelle Jenstad wrote:

...
Oh, I get it now. It's meant to be an English gloss on the preceding Pinyin example. It's just out of step with the pattern already established. All the others have the English gloss embedded in the introduction to the <egXML>.

How about: "Here is a similar example from Taiwan using Bopomofo (Pinyin píngzi = bottle, taken from Wikipedia):" -- followed by the <egXML>.

J.

Janelle Jenstad, Associate Professor, Department of English, University of Victoria Director, Map of Early Modern London; Director, Linked Early Modern Drama Online Coordinating Platform Editor, Digital Renaissance Editions Email: jenstad@uvic.ca, lemdo@uvic.ca, or london@uvic.ca

-----Original Message----- From: Martin Holmes Sent: February 3, 2021 10:21 AM To: Janelle Jenstad ; tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Subject: Re: [Tei-council] Ruby Core chapter now built

I think the p of Pinyin should be capital, so it's a full sentence; other than that, I think it's OK. Did you mean that it should be a footnote?

Cheers, Martin

On 2021-02-03 10:18 a.m., Janelle Jenstad wrote:

...
Quick observation:

This parenthentical phrase is meant to be a note on the first use of pinyin, I think: " (pinyin píngzi = bottle, taken from Wikipedia.)" It's right after this egXML: https://teijenkins.hcmc.uvic.ca/job/TEIP5-issue-2054-ruby/lastSuccessfulBuil....

Janelle Jenstad, Associate Professor, Department of English, University of Victoria Director, Map of Early Modern London; Director, Linked Early Modern Drama Online Coordinating Platform Editor, Digital Renaissance Editions Email: jenstad@uvic.ca, lemdo@uvic.ca, or london@uvic.ca

-----Original Message----- From: Tei-council On Behalf Of Martin Holmes Sent: February 3, 2021 9:57 AM To: tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Subject: [Tei-council] Ruby Core chapter now built

Notice: This message was sent from outside the University of Victoria email system but is claiming to be from UVic. Please be cautious with links, attachments, and sensitive information.

Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links and sensitive information.

Hi all,

A first draft of the reorganized version of the CO chapter incorporating the new Ruby section can now be seen here:

<https://teijenkins.hcmc.uvic.ca/job/TEIP5-issue-2054-ruby/lastSucces s fulBuild/artifact/P5/Guidelines-web/en/html/CO.html>

Please take a look and let me know what you think. I haven't yet added links/refs from other chapters because I want to make sure the ids etc. are stable before I do that.

Since Nagasaki-sensei has kindly provided translations of the glosses and descs on the Spec pages, the 日本語 links at the bottom of those pages will hopefully be useful.

Cheers, Martin

On 2021-02-03 7:58 a.m., Martin Holmes wrote:

...
Hi all,

Thanks for the feedback on the location for the Ruby prose. The consensus is clear -- it should be in core -- and the comments suggest that the most appropriate approach will be to integrated it with the content relating to glosses, which is currently in 3.3.4, "Terms, Glosses, Equivalents, and Descriptions". That sub-subsection is already quite long, so what I propose to attempt is this:

Take 3.3.4 "Terms, Glosses, Equivalents, and Descriptions" and 3.3.5 "Some Further Examples" and make them into a new subsection (i.e. one level higher), which will become 3.4.

Title the new section "Terms, Glosses, Equivalents, Descriptions, and Ruby". (JJ suggests that terms belongs elsewhere, but that would be a major reorg, and I don't think we have time for that right now.)

Create subsections:

3.4.1 "Terms and Glosses" covering the first part of what is now 3.3.4. This would also include the "Further Examples" bit, which is really an extension of this.

3.4.2 "Ruby Annotations" containing the new prose already proposed.

3.4.3 "Equivalents and Descriptions" containing the part of what is now 3.3.4 which discusses altIdent, desc, and equiv; I think this is a different topic, really, from glossing terms.

I'm doing this work in a separate branch:

https://github.com/TEIC/TEI/tree/issue-2054-ruby

which I'll merge dev into steadily as I go, to minimize later merge conflicts. I'll also set up a build job for this branch on my Jenkins when the initial work is done.

The time is relatively short, but I think we can get there before the freeze.

I'll post the meat of this on the ticket too, for the record.

Cheers, Martin

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca

Martin Holmes

4:43 p.m.

New subject: Ruby Core chapter now built

Thanks again Martina -- I've made all these changes, and the rebuild should be done in an hour or so. But I can't see the superfluous space in the rt spec example -- where do you see it? Cheers, Martin On 2021-02-04 7:20 a.m., Scholger, Martina (martina.scholger@uni-graz.at) wrote:

...

Hi Martin,

Thanks - looks good to me.

Some quick comments: * For the title of the section I would follow the order of the sub-sections. The title is currently "Terms, Glosses, Equivalents, Descriptions, and Ruby Annotations". The order of the sub-sections is Terms and Glosses, (Further Examples), Ruby Annotations, and Equivalents and Descriptions. And, I wonder if "Some Further Examples" should be 3.4.1.1 instead of 3.4.2?

* The note needs to be deleted: [NOTE: if proposed layout/@rubyPlace is implemented, it should be explained here.]

* In "We could also use a standoff approach with anchors and pointers:" anchor could be a link to the specs.

* <rt> and <rb> specs: "contained by" is empty

* <rt> specs: in the example there is a superfluous space in <rb> and <rt>

Best, Martina

-----Ursprüngliche Nachricht----- Von: Tei-council Im Auftrag von Martin Holmes Gesendet: Mittwoch, 3. Februar 2021 19:27 An: Janelle Jenstad ; tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Betreff: Re: [Tei-council] Ruby Core chapter now built

Ah, better idea. Will do.

Cheers, Martin

On 2021-02-03 10:26 a.m., Janelle Jenstad wrote:

...
Oh, I get it now. It's meant to be an English gloss on the preceding Pinyin example. It's just out of step with the pattern already established. All the others have the English gloss embedded in the introduction to the <egXML>.

How about: "Here is a similar example from Taiwan using Bopomofo (Pinyin píngzi = bottle, taken from Wikipedia):" -- followed by the <egXML>.

J.

Janelle Jenstad, Associate Professor, Department of English, University of Victoria Director, Map of Early Modern London; Director, Linked Early Modern Drama Online Coordinating Platform Editor, Digital Renaissance Editions Email: jenstad@uvic.ca, lemdo@uvic.ca, or london@uvic.ca

-----Original Message----- From: Martin Holmes Sent: February 3, 2021 10:21 AM To: Janelle Jenstad ; tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Subject: Re: [Tei-council] Ruby Core chapter now built

I think the p of Pinyin should be capital, so it's a full sentence; other than that, I think it's OK. Did you mean that it should be a footnote?

Cheers, Martin

On 2021-02-03 10:18 a.m., Janelle Jenstad wrote:

...
Quick observation:

This parenthentical phrase is meant to be a note on the first use of pinyin, I think: " (pinyin píngzi = bottle, taken from Wikipedia.)" It's right after this egXML: https://teijenkins.hcmc.uvic.ca/job/TEIP5-issue-2054-ruby/lastSuccessfulBuil....

Janelle Jenstad, Associate Professor, Department of English, University of Victoria Director, Map of Early Modern London; Director, Linked Early Modern Drama Online Coordinating Platform Editor, Digital Renaissance Editions Email: jenstad@uvic.ca, lemdo@uvic.ca, or london@uvic.ca

-----Original Message----- From: Tei-council On Behalf Of Martin Holmes Sent: February 3, 2021 9:57 AM To: tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Subject: [Tei-council] Ruby Core chapter now built

Notice: This message was sent from outside the University of Victoria email system but is claiming to be from UVic. Please be cautious with links, attachments, and sensitive information.

Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links and sensitive information.

Hi all,

A first draft of the reorganized version of the CO chapter incorporating the new Ruby section can now be seen here:

<https://teijenkins.hcmc.uvic.ca/job/TEIP5-issue-2054-ruby/lastSucces s fulBuild/artifact/P5/Guidelines-web/en/html/CO.html>

Please take a look and let me know what you think. I haven't yet added links/refs from other chapters because I want to make sure the ids etc. are stable before I do that.

Since Nagasaki-sensei has kindly provided translations of the glosses and descs on the Spec pages, the 日本語 links at the bottom of those pages will hopefully be useful.

Cheers, Martin

On 2021-02-03 7:58 a.m., Martin Holmes wrote:

...
Hi all,

Thanks for the feedback on the location for the Ruby prose. The consensus is clear -- it should be in core -- and the comments suggest that the most appropriate approach will be to integrated it with the content relating to glosses, which is currently in 3.3.4, "Terms, Glosses, Equivalents, and Descriptions". That sub-subsection is already quite long, so what I propose to attempt is this:

Take 3.3.4 "Terms, Glosses, Equivalents, and Descriptions" and 3.3.5 "Some Further Examples" and make them into a new subsection (i.e. one level higher), which will become 3.4.

Title the new section "Terms, Glosses, Equivalents, Descriptions, and Ruby". (JJ suggests that terms belongs elsewhere, but that would be a major reorg, and I don't think we have time for that right now.)

Create subsections:

3.4.1 "Terms and Glosses" covering the first part of what is now 3.3.4. This would also include the "Further Examples" bit, which is really an extension of this.

3.4.2 "Ruby Annotations" containing the new prose already proposed.

3.4.3 "Equivalents and Descriptions" containing the part of what is now 3.3.4 which discusses altIdent, desc, and equiv; I think this is a different topic, really, from glossing terms.

I'm doing this work in a separate branch:

https://github.com/TEIC/TEI/tree/issue-2054-ruby

which I'll merge dev into steadily as I go, to minimize later merge conflicts. I'll also set up a build job for this branch on my Jenkins when the initial work is done.

The time is relatively short, but I think we can get there before the freeze.

I'll post the meat of this on the ticket too, for the record.

Cheers, Martin

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca

Scholger, Martina (martina.scholger＠uni-graz.at)

4:46 p.m.

New subject: Ruby Core chapter now built

Sorry, it is in the rb specs <ruby> <rb>你 </rb> <rt place="above">nǐ </rt> </ruby> <ruby> <rb>好</rb> <rt place="above">hǎo</rt> </ruby> Best, Martina -----Ursprüngliche Nachricht----- Von: Martin Holmes Gesendet: Donnerstag, 4. Februar 2021 16:43 An: Scholger, Martina (martina.scholger@uni-graz.at) ; Janelle Jenstad ; tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Betreff: Re: AW: [Tei-council] Ruby Core chapter now built Thanks again Martina -- I've made all these changes, and the rebuild should be done in an hour or so. But I can't see the superfluous space in the rt spec example -- where do you see it? Cheers, Martin On 2021-02-04 7:20 a.m., Scholger, Martina (martina.scholger@uni-graz.at) wrote:

...

Hi Martin,

Thanks - looks good to me.

Some quick comments: * For the title of the section I would follow the order of the sub-sections. The title is currently "Terms, Glosses, Equivalents, Descriptions, and Ruby Annotations". The order of the sub-sections is Terms and Glosses, (Further Examples), Ruby Annotations, and Equivalents and Descriptions. And, I wonder if "Some Further Examples" should be 3.4.1.1 instead of 3.4.2?

* The note needs to be deleted: [NOTE: if proposed layout/@rubyPlace is implemented, it should be explained here.]

* In "We could also use a standoff approach with anchors and pointers:" anchor could be a link to the specs.

* <rt> and <rb> specs: "contained by" is empty

* <rt> specs: in the example there is a superfluous space in <rb> and <rt>

Best, Martina

-----Ursprüngliche Nachricht----- Von: Tei-council Im Auftrag von Martin Holmes Gesendet: Mittwoch, 3. Februar 2021 19:27 An: Janelle Jenstad ; tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Betreff: Re: [Tei-council] Ruby Core chapter now built

Ah, better idea. Will do.

Cheers, Martin

On 2021-02-03 10:26 a.m., Janelle Jenstad wrote:

...
Oh, I get it now. It's meant to be an English gloss on the preceding Pinyin example. It's just out of step with the pattern already established. All the others have the English gloss embedded in the introduction to the <egXML>.

How about: "Here is a similar example from Taiwan using Bopomofo (Pinyin píngzi = bottle, taken from Wikipedia):" -- followed by the <egXML>.

J.

Janelle Jenstad, Associate Professor, Department of English, University of Victoria Director, Map of Early Modern London; Director, Linked Early Modern Drama Online Coordinating Platform Editor, Digital Renaissance Editions Email: jenstad@uvic.ca, lemdo@uvic.ca, or london@uvic.ca

-----Original Message----- From: Martin Holmes Sent: February 3, 2021 10:21 AM To: Janelle Jenstad ; tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Subject: Re: [Tei-council] Ruby Core chapter now built

I think the p of Pinyin should be capital, so it's a full sentence; other than that, I think it's OK. Did you mean that it should be a footnote?

Cheers, Martin

On 2021-02-03 10:18 a.m., Janelle Jenstad wrote:

...
Quick observation:

This parenthentical phrase is meant to be a note on the first use of pinyin, I think: " (pinyin píngzi = bottle, taken from Wikipedia.)" It's right after this egXML: https://teijenkins.hcmc.uvic.ca/job/TEIP5-issue-2054-ruby/lastSuccessfulBuil....

Janelle Jenstad, Associate Professor, Department of English, University of Victoria Director, Map of Early Modern London; Director, Linked Early Modern Drama Online Coordinating Platform Editor, Digital Renaissance Editions Email: jenstad@uvic.ca, lemdo@uvic.ca, or london@uvic.ca

-----Original Message----- From: Tei-council On Behalf Of Martin Holmes Sent: February 3, 2021 9:57 AM To: tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Subject: [Tei-council] Ruby Core chapter now built

Notice: This message was sent from outside the University of Victoria email system but is claiming to be from UVic. Please be cautious with links, attachments, and sensitive information.

Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links and sensitive information.

Hi all,

A first draft of the reorganized version of the CO chapter incorporating the new Ruby section can now be seen here:

<https://teijenkins.hcmc.uvic.ca/job/TEIP5-issue-2054-ruby/lastSucce s s fulBuild/artifact/P5/Guidelines-web/en/html/CO.html>

Please take a look and let me know what you think. I haven't yet added links/refs from other chapters because I want to make sure the ids etc. are stable before I do that.

Since Nagasaki-sensei has kindly provided translations of the glosses and descs on the Spec pages, the 日本語 links at the bottom of those pages will hopefully be useful.

Cheers, Martin

On 2021-02-03 7:58 a.m., Martin Holmes wrote:

...
Hi all,

Thanks for the feedback on the location for the Ruby prose. The consensus is clear -- it should be in core -- and the comments suggest that the most appropriate approach will be to integrated it with the content relating to glosses, which is currently in 3.3.4, "Terms, Glosses, Equivalents, and Descriptions". That sub-subsection is already quite long, so what I propose to attempt is this:

Take 3.3.4 "Terms, Glosses, Equivalents, and Descriptions" and 3.3.5 "Some Further Examples" and make them into a new subsection (i.e. one level higher), which will become 3.4.

Title the new section "Terms, Glosses, Equivalents, Descriptions, and Ruby". (JJ suggests that terms belongs elsewhere, but that would be a major reorg, and I don't think we have time for that right now.)

Create subsections:

3.4.1 "Terms and Glosses" covering the first part of what is now 3.3.4. This would also include the "Further Examples" bit, which is really an extension of this.

3.4.2 "Ruby Annotations" containing the new prose already proposed.

3.4.3 "Equivalents and Descriptions" containing the part of what is now 3.3.4 which discusses altIdent, desc, and equiv; I think this is a different topic, really, from glossing terms.

I'm doing this work in a separate branch:

https://github.com/TEIC/TEI/tree/issue-2054-ruby

which I'll merge dev into steadily as I go, to minimize later merge conflicts. I'll also set up a build job for this branch on my Jenkins when the initial work is done.

The time is relatively short, but I think we can get there before the freeze.

I'll post the meat of this on the ticket too, for the record.

Cheers, Martin

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca

Martin Holmes

4:58 p.m.

New subject: Ruby Core chapter now built

Ah, thanks! Should be fixed now, and visible in the next build. If there's no other feedback, I'll add the links from other locations today, and aim to have a merge request by tomorrow. I'll also generate schemas today and validate the content of the examples. Syd, would you have time to take a look today? Cheers, Martin On 2021-02-04 7:46 a.m., Scholger, Martina (martina.scholger@uni-graz.at) wrote:

...

Sorry, it is in the rb specs <ruby> <rb>你 </rb> <rt place="above">nǐ </rt> </ruby> <ruby> <rb>好</rb> <rt place="above">hǎo</rt> </ruby>

Best, Martina

-----Ursprüngliche Nachricht----- Von: Martin Holmes Gesendet: Donnerstag, 4. Februar 2021 16:43 An: Scholger, Martina (martina.scholger@uni-graz.at) ; Janelle Jenstad ; tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Betreff: Re: AW: [Tei-council] Ruby Core chapter now built

Thanks again Martina -- I've made all these changes, and the rebuild should be done in an hour or so.

But I can't see the superfluous space in the rt spec example -- where do you see it?

Cheers, Martin

On 2021-02-04 7:20 a.m., Scholger, Martina (martina.scholger@uni-graz.at) wrote:

...
Hi Martin,

Thanks - looks good to me.

Some quick comments: * For the title of the section I would follow the order of the sub-sections. The title is currently "Terms, Glosses, Equivalents, Descriptions, and Ruby Annotations". The order of the sub-sections is Terms and Glosses, (Further Examples), Ruby Annotations, and Equivalents and Descriptions. And, I wonder if "Some Further Examples" should be 3.4.1.1 instead of 3.4.2?

* The note needs to be deleted: [NOTE: if proposed layout/@rubyPlace is implemented, it should be explained here.]

* In "We could also use a standoff approach with anchors and pointers:" anchor could be a link to the specs.

* <rt> and <rb> specs: "contained by" is empty

* <rt> specs: in the example there is a superfluous space in <rb> and <rt>

Best, Martina

-----Ursprüngliche Nachricht----- Von: Tei-council Im Auftrag von Martin Holmes Gesendet: Mittwoch, 3. Februar 2021 19:27 An: Janelle Jenstad ; tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Betreff: Re: [Tei-council] Ruby Core chapter now built

Ah, better idea. Will do.

Cheers, Martin

On 2021-02-03 10:26 a.m., Janelle Jenstad wrote:

...
Oh, I get it now. It's meant to be an English gloss on the preceding Pinyin example. It's just out of step with the pattern already established. All the others have the English gloss embedded in the introduction to the <egXML>.

How about: "Here is a similar example from Taiwan using Bopomofo (Pinyin píngzi = bottle, taken from Wikipedia):" -- followed by the <egXML>.

J.

Janelle Jenstad, Associate Professor, Department of English, University of Victoria Director, Map of Early Modern London; Director, Linked Early Modern Drama Online Coordinating Platform Editor, Digital Renaissance Editions Email: jenstad@uvic.ca, lemdo@uvic.ca, or london@uvic.ca

-----Original Message----- From: Martin Holmes Sent: February 3, 2021 10:21 AM To: Janelle Jenstad ; tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Subject: Re: [Tei-council] Ruby Core chapter now built

I think the p of Pinyin should be capital, so it's a full sentence; other than that, I think it's OK. Did you mean that it should be a footnote?

Cheers, Martin

On 2021-02-03 10:18 a.m., Janelle Jenstad wrote:

...
Quick observation:

This parenthentical phrase is meant to be a note on the first use of pinyin, I think: " (pinyin píngzi = bottle, taken from Wikipedia.)" It's right after this egXML: https://teijenkins.hcmc.uvic.ca/job/TEIP5-issue-2054-ruby/lastSuccessfulBuil....

Janelle Jenstad, Associate Professor, Department of English, University of Victoria Director, Map of Early Modern London; Director, Linked Early Modern Drama Online Coordinating Platform Editor, Digital Renaissance Editions Email: jenstad@uvic.ca, lemdo@uvic.ca, or london@uvic.ca

-----Original Message----- From: Tei-council On Behalf Of Martin Holmes Sent: February 3, 2021 9:57 AM To: tei-council@lists.tei-c.org; Kiyonori NAGASAKI ; Kazuhiro Okada ; Nicholas Cole Subject: [Tei-council] Ruby Core chapter now built

Notice: This message was sent from outside the University of Victoria email system but is claiming to be from UVic. Please be cautious with links, attachments, and sensitive information.

Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links and sensitive information.

Hi all,

A first draft of the reorganized version of the CO chapter incorporating the new Ruby section can now be seen here:

<https://teijenkins.hcmc.uvic.ca/job/TEIP5-issue-2054-ruby/lastSucce s s fulBuild/artifact/P5/Guidelines-web/en/html/CO.html>

Please take a look and let me know what you think. I haven't yet added links/refs from other chapters because I want to make sure the ids etc. are stable before I do that.

Since Nagasaki-sensei has kindly provided translations of the glosses and descs on the Spec pages, the 日本語 links at the bottom of those pages will hopefully be useful.

Cheers, Martin

On 2021-02-03 7:58 a.m., Martin Holmes wrote:

...
Hi all,

Thanks for the feedback on the location for the Ruby prose. The consensus is clear -- it should be in core -- and the comments suggest that the most appropriate approach will be to integrated it with the content relating to glosses, which is currently in 3.3.4, "Terms, Glosses, Equivalents, and Descriptions". That sub-subsection is already quite long, so what I propose to attempt is this:

Take 3.3.4 "Terms, Glosses, Equivalents, and Descriptions" and 3.3.5 "Some Further Examples" and make them into a new subsection (i.e. one level higher), which will become 3.4.

Title the new section "Terms, Glosses, Equivalents, Descriptions, and Ruby". (JJ suggests that terms belongs elsewhere, but that would be a major reorg, and I don't think we have time for that right now.)

Create subsections:

3.4.1 "Terms and Glosses" covering the first part of what is now 3.3.4. This would also include the "Further Examples" bit, which is really an extension of this.

3.4.2 "Ruby Annotations" containing the new prose already proposed.

3.4.3 "Equivalents and Descriptions" containing the part of what is now 3.3.4 which discusses altIdent, desc, and equiv; I think this is a different topic, really, from glossing terms.

I'm doing this work in a separate branch:

https://github.com/TEIC/TEI/tree/issue-2054-ruby

which I'll merge dev into steadily as I go, to minimize later merge conflicts. I'll also set up a build job for this branch on my Jenkins when the initial work is done.

The time is relatively short, but I think we can get there before the freeze.

I'll post the meat of this on the ticket too, for the record.

Cheers, Martin

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca

1379

Age (days ago)

1380

Last active (days ago)

List overview

Download

10 comments

3 participants

participants (3)

Janelle Jenstad
Martin Holmes
Scholger, Martina (martina.scholger＠uni-graz.at)

Thanks for Ruby feedback

tags

participants (3)