From b1000a5f50e215356294859473bd4a5fb2c44a00 Mon Sep 17 00:00:00 2001 From: Syd Bauman Date: Tue, 4 Apr 2023 11:44:25 -0400 Subject: [PATCH] Last-minute tweaks by the release techs --- P5/ReleaseNotes/readme-4.6.0.xml | 33 ++++++++++++-------------------- 1 file changed, 12 insertions(+), 21 deletions(-) diff --git a/P5/ReleaseNotes/readme-4.6.0.xml b/P5/ReleaseNotes/readme-4.6.0.xml index f2510e98d1..a8732dd65a 100644 --- a/P5/ReleaseNotes/readme-4.6.0.xml +++ b/P5/ReleaseNotes/readme-4.6.0.xml @@ -44,7 +44,7 @@ See the file COPYING.txt for details New encoding features The calendar element is now a member of att.typed, permitting the type and subtype attributes (att.typed, giving it the type and subtype attributes (#2396). The lg element may now contain any of the members of model.pPart.transcriptional, including supplied, redo, and @@ -106,14 +106,14 @@ See the file COPYING.txt for details In addition, several typos, unclear expressions, and faulty encodings have been corrected (#2252, #2403, #2387), #2387, #2225, PR #2375, #2356. + target="https://github.com/TEIC/TEI/issues/2356">#2356). - The TEI oXygen framework has been updated to - accomodate the fact that newer versions of oXygen use Saxon 11 (#2251) The title elements with ref @@ -155,8 +154,8 @@ See the file COPYING.txt for details class via an attRef that refers to another attribute class (as opposed to class membership via memberOf or attribute definition via attDef) was not showing up in - the documentation specification pages. (#419) + the documentation specification pages; this has been fixed (#419). Infelicitous spacing in egXML was corrected with resetting the HTML output declaration to prevent indentation (Corrected a problem with processing the minOccurs attribute on attDef — when set to 0 minOccurs was behaving as if - it has been set to 1 unless maxOccurs + it had been set to 1 unless maxOccurs was unbounded (#557). - - - Cases of an attDef mode="delete" that was - inside an attList that was itself inside an - attList were not being processed; this was - corrected (Cases of an attDef with a mode of + delete that was inside an attList that + was itself inside an attList were not being + processed; this was corrected (PR #601).