Error: Reference source not found

Dear ODF 1.3 spec reviewers, I have worked this week on the ODF 1.3 packages specification and started on Friday a checklist on GitHub with minor editorial changes: https://github.com/oasis-tcs/odf-tc/issues/21 I would suggest using GitHub issues for editorial issues in the future because GitHub is naturally far better integrated with its own issue tracker than with Jira. In addition, GitHub offers useful features as the checkbox feature I have been using. Finally, everyone can easily separate ODF feature issues from editorial ones and ignore the latter. There is an update on the ODF 1.3 packages specification. After the pull request was reviewed and merged (and in general), you may find the latest ODT 1.3 specification documents at: https://github.com/oasis-tcs/odf-tc/tree/master/src/main/resources/odf1.3 The location of ODF 1.3 HTML files is listed in our README table . Before the pull request was reviewed and merged a newer HTML & ODF of part 2 packages can be found at my GitHub repository. I am aiming to fix some further minor issues ( checkboxes ) over the weekend on all parts. Perhaps someone could assist me with the check on correct spelling & usage of our Terminology (e.g. ISO Keywords). Just ping me... ;-) Have a nice weekend, Svante Am Fr., 14. Aug. 2020 um 20:08 Uhr schrieb Svante Schubert < [email protected] >: Hello Regina, I borrowed the editor's token from Francis and already earlier some broken Internet links when I checked the HTML result with a link checker. Two more references were broken in Part2 and I fixed some other problems on Top of Francis' work: https://github.com/oasis-tcs/odf-tc/pull/22 Still have to add my prior changes of this week now manually due to the problems with merging ODF changes... I aim to fix further editorial problems until our TC meeting, mainly HTML layout. Have a nice weekend, Svante Am Fr., 14. Aug. 2020 um 17:19 Uhr schrieb Francis Cave < [email protected] >: Thanks, Regina. I must say I thought I'd fixed that, as I certainly saw this bug before. I'll make sure that it's fixed in CSD02. I have issued a pull request on GitHub. Kind regards, Francis