slavonic / cu-books Goto Github PK
View Code? Open in Web Editor NEWChurch Slavonic text corpus
License: MIT License
cu-books's People
Contributors
Stargazers
Watchers
cu-books's Issues
Chasoslov has significant additions from Sledovatelnaya Psaltyr
Chasoslov has several chapters added from another book (Sledovatenlaya Psaltyr).
We need to separate them by creating a separate volume for (partially digitized) Seldovatelnaya Psaltyr.
Footnote target unclear in many places
From Dobrotolyubie 1_01.xml:
<p>рл҃и. Сме́ртное безсмє́ртнымъ подлежи́тъ, безсме́ртное же
смє́ртнымъ:<footnote lang="cu">Безсме́ртное здѣ́сь за долговре́менное и҆
долгопребыва́ющее бере́тсѧ.</footnote> слꙋ́жатъ, си́рѣчь, стїхі̑и человѣ́кꙋ,
по человѣколю́бїю, и҆ врожде́нной въ ни́хъ бла́гости созда́вшагѡ бг҃а.</p>
Or 2_03.xml:
...Поне́же ᲂу҆́бѡ по писа́нїю, всѧ́ко дре́во, не творѧ́щее плода̀ добра̀
посѣка́етсѧ, и҆ во ѻ҆́гнь вмета́етсѧ:<footnote lang="cu">Лꙋкѝ гл. г҃, ст. ѳ҃.</footnote>
ꙗ҆́вѣ, ꙗ҆́кѡ ѡ҆ плода́хъ всѐ на́ше тща́нїе до́лженствꙋетъ...
It is hardly reasonable to use the last word of the preceding phrase as footnote target. Especially when target is Jesus' parable.
How the original renders this? As a numbered superscript? Maybe we should leave superscript and mark this up as <sup>1</sup><footnote...?
Trebnik: may need finer file split
Looks like file chapters in Trebnik span several logical chapters. Should not this be split further?
Unmatched kavyka
I am expecting kavyka to be used in pairs, like this:
꙾па́че꙾
꙾꙾па́че꙾꙾
꙾꙾꙾па́че꙾꙾꙾
Yet in the following sources there seem to be unmatched kavyka symbols. Please review:
/Users/mike/git/cu-books/Evangelie1984/chapters/1mf.xml ꙾<footnote lang="cu">꙾и҆ ѻ҆гне́мъ꙾[лꙋкѝ г҃, ст. ѕ҃і].</footnote>
/Users/mike/git/cu-books/Evangelie1984/chapters/1mf.xml ꙾<footnote lang="cu">꙾и҆ лицемѣ́рнѡ на до́лзѣ мл҃твы творитѐ꙾</footnote>
/Users/mike/git/cu-books/Evangelie1984/chapters/1mf.xml ꙾<footnote lang="cu">꙾По ве́чери же сꙋббѡ́тнѣмъ꙾</footnote>
/Users/mike/git/cu-books/Evangelie1984/chapters/3lk.xml ꙾<footnote lang="cu">꙾попрости́тисѧ съ сꙋ́щими꙾</footnote>
/Users/mike/git/cu-books/Evangelie1984/chapters/3lk.xml ꙾<footnote lang="cu">꙾Междꙋ̀ тѣ́мъ꙾</footnote>
/Users/mike/git/cu-books/Apostol1989/chapters/22tim1.xml ꙾<footnote lang="cu">꙾ста́рца не ᲂу҆корѧ́й, но ᲂу҆молѧ́й꙾</footnote>
/Users/mike/git/cu-books/Irmologii1995/chapters/04glas.xml ꙾<footnote lang="cu">Оу҆спе́нїѧ вмѣ́стѡ, торжество̀: ꙾преставле́нїе꙾</footnote>
/Users/mike/git/cu-books/PostnayaTriod1992/chapters/12pt1.xml ꙾<footnote lang="cu">꙾па́че</footnote>
/Users/mike/git/cu-books/AugmentedPsalter1978/chapters/Cathisma_13.xml ꙾<footnote lang="cu">на́шъ꙾</footnote>
/Users/mike/git/cu-books/AugmentedPsalter1978/chapters/Cathisma_10.xml ꙾<footnote lang="cu">꙾же́злъ достоѧ́нїѧ твоегѡ̀, го́рꙋ сїѡ́нъ сїю̀</footnote>
/Users/mike/git/cu-books/AugmentedPsalter1978/chapters/01ps.xml ꙾<footnote lang="cu">꙾же́злъ достоѧ́нїѧ твоегѡ̀, го́рꙋ сїѡ́нъ сїю̀</footnote>
/Users/mike/git/cu-books/AugmentedPsalter1978/chapters/01ps.xml ꙾<footnote lang="cu">на́шъ꙾</footnote>
/Users/mike/git/cu-books/Trebnik1906/chapters/02ispovedanie.xml ꙾<footnote lang="cu">ст҃ы́хъ бг҃оѧвле́нїй во́дꙋ</footnote>
/Users/mike/git/cu-books/Trebnik1906/chapters/02ispovedanie.xml ꙾<footnote lang="cu">-ꙋ̀</footnote>
/Users/mike/git/cu-books/Trebnik1906/chapters/02ispovedanie.xml ꙾<footnote lang="cu">-ю̀</footnote>
/Users/mike/git/cu-books/Trebnik1906/chapters/02ispovedanie.xml ꙾<footnote lang="cu">є҆́й</footnote>
/Users/mike/git/cu-books/Trebnik1906/chapters/02ispovedanie.xml ꙾<footnote lang="cu">є҆́й</footnote>
/Users/mike/git/cu-books/Trebnik1906/chapters/54osv_tserkv.xml ꙾<footnote lang="cu">та́йнами</footnote>
/Users/mike/git/cu-books/Trebnik1906/chapters/07kan_ishod.xml ꙾<footnote lang="cu">-ѣй</footnote>
/Users/mike/git/cu-books/Trebnik1906/chapters/07kan_ishod.xml ꙾<footnote lang="cu">-ѣй</footnote>
/Users/mike/git/cu-books/Trebnik1906/chapters/07kan_ishod.xml ꙾<footnote lang="cu">-аѧ</footnote>
/Users/mike/git/cu-books/Trebnik1906/chapters/07kan_ishod.xml ꙾<footnote lang="cu">-а</footnote>
/Users/mike/git/cu-books/MineyaNovember1997/chapters/17.xml ꙾<footnote lang="cu">꙾Неѡко́росъ <disp lang="ru">или неокоръ (так у Дьяченко): греч.</disp> <disp lang="el">νεωκόρος,</disp> <disp lang="ru">«смотритель, блюститель храма, ризничий». У Бончева по-болгарски «пазител на храм, жрец» (Мин. ноем. 17 кан. п. 4). Прим.</disp> <disp lang="ru">orthlib.</disp></footnote>
/Users/mike/git/cu-books/Oktoih1981/chapters/08daily_trop.xml ꙾<footnote lang="cu">Внеза́пꙋ</footnote>
/Users/mike/git/cu-books/Oktoih1981/chapters/4_0.xml ꙾<footnote lang="cu">꙾ꙗ҆́домъ и҆спо́лнены въ мѧ̀꙾</footnote>
Missing line number in Matthew 21
In The Gospel of Matthew chapter 21 there's a line number missing for line 14. In /Evangelie1984/chapters/1mf.xml at line 395 pos 454.
Pagebreak anchors render incorrectly
This is how a pagebreak anchor appears in the source *.xml file:
<anchor type="folio" number="1v" label="а҃ ѡ҆б."/>
This is how the same anchor appears in the transformed target file (indentation added for readability):
<small class="pb">
<a title="folio 1v" href="http://www.ponomar.net/cgi-bin/bookpage.cgi?id=&page=1v">
1v
</a>
</small>
Please note how the actual content of the rendered element does not correspond to the value of label attribute of the initial markup.
As we can see in Ponomar Library, the pagebreak anchor element content is indeed supposed to match the label attribute value (and should be enclosed in brackets, even). To sum up, the pagebreak anchor taken as example is expected to transform as follows:
<small class="pb">
<a title="folio 1v" href="http://www.ponomar.net/cgi-bin/bookpage.cgi?id=&page=1v">
(л. а҃ ѡ҆б.)
</a>
</small>
Possibly incorrect use of pagebreak anchor
Pagebreak anchor should be placed just before first content on this page (unless I did not understand the definition).
This implies that <anchor> should never be the last element in a book.
It appears that some books (Evangelie) violate this convention. Probably because they place anchor
at the end of the current page content, not at the beginning.
Needs review and possibly fixing...
Texts lacking structure
For a format chosen as the barebone storage for CU texts, current XSLT markdown is lacking structure - severely if I may say so. Transformed xmls require a lot of manual work in preparation for digital publishing. I for one have two general concerns.
- There's not complex enough chapter breaking. The New Testament is an example. The NT consists of several books, and each book consists of several chapters. Currently, a book is a chapter. How convenient is that? Not very. To prepare the available Evangelie xmls to digital publishing I have to create the proper table of contents by hand.
- There's not enough structure inside the documents. There's a reason why heading elements exist in HTML. Some digital publishing systems construct tables of contents automatically based on the header structure of the document. This could - and should be used to our advantage.
Also, in The New Testament prints, each new verse usually starts with new line - there's a reason why<br>element exists in HTML, too! - Some digital publishing formats, namely ePUB, don't automaticaly begin a new chapter with a new page. Page breaks exist in ePUB in the way of the book consisting of multiple *.xhtml files, each containing a proper chapter. So, ideally, in my opinion, there should also be a way of indicating the chapter breaks explicitly.
Please respond if you think these concerns worth attention.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.