There is some pali leak in translation (Bhagavā avoca What do you think, Poṭṭhapāda? Have you ever heard of this before?” …)
2 Likes
Oops! I have fixed this.
Life Span (1st) but Long Life (2nd). Is that intentional? It also appears that the vagga name is different causing the vagga name to appear twice in the auto generated epub.
https://suttacentral.net/sn4.23/en/sujato
the vagga name changes from "3. Māra " to “3. Rule”
The following all relate to the generation of epubs:
For some reason in the Sakka Saṃyutta (https://suttacentral.net/sn11) the first two vagga headings don’t get inserted into the epub file. But the third one does. It looks fine on the front end of the website.
Same problem in the Anamatagga, Rahula, Lakkhana, Asaṅkhatasaṁyutta and Lābhasakkāra Saṃyutta with all vagga headings missing.
for https://suttacentral.net/sn45.170/en/sujato, I wonder if there should be a note explaining why there is a sutta name in the middle of the page. When doing reformatting of the epubs, this gets caught.
In https://suttacentral.net/sn50, the first five vagga headings don’t end up in the epub. I realize there is only one file under each of these, but shouldn’t it be there for consistency? (it is in the previous samyutta)
Same problem in SN53. As well, in this samyutta, the sutta names do not included the range of numbers as they do in the previous samyutta.
It looks like there are “hidden” suttas in https://suttacentral.net/sn46.57/en/sujato and I wonder if there should be mention of this in the description.
1 Like
Thanks, fixed.
Also fixed.
Umm, okay, I have no idea what’s going on here.
I have made a note for this and the similar case you mention below.
Good point, actually. Sometimes <h2> headings inside suttas are for subheadings, and sometimes they are for cases like this, a subsidiary sutta. We should have a CSS class that distinguishes the two uses, which can be used for the EPUBs. It’s not hard to do: all the former cases are in DN and MN, the latter in SN and AN.
For the other details you mention, I’ll add them to a github issue and we’ll address them at the programming level when we can.
1 Like
I’m assuming you mean you don’t understand why. If you need clarification, let me know.
Yes. In cleaning up the epubs of SN and AN, the vaggas seem to always be just in p tags. But because of the surrounding code I’m able to change them to h2. I haven’t even looked at the DN and MN auto gen files yet.
That’s right.
So, in the SN epub, to make them easier to navigate, I make the 56 samyuttas h1, the vaggas h2, and the individual suttas h3.
In the auto generated texts, the individual suttas are h1 and nothing else has a heading, except for those few cases you mention.
From my side there is no problem, I’ve manually added the missing vaggas into the epub. I was just mentioning what I am doing with them.
1 Like
Okay, that’s fine; I deleted my comment when I saw the file and how nice it looks!
What would be good at some point is if you could document the changes and adjustments you’re making, and they can ultimately be incorporated directly in the EPUB export. You can leave these here:
Oh, yes. I have a text file that documents everything. I wanted to be ready to do it all over again if you suddenly pushed out more updates. 
2 Likes
SN48.40 Irregular order
#sc 3.3 ‘The faculty of pleasure has arisen in me. And that has a precursor, a source, a condition, and a reason.
#sc 3.4 it’s not possible for the faculty of pain to arise without a precursor, a source, a condition, or a reason.’
Should be ‘pleasure’ here too.
looks like there is still a rogue close paren in dn16. It is styled as an endsection
https://suttacentral.net/dn16/en/sujato#sc172
It’s odd that there aren’t any recitation section endings at all in this sutta, especially because it is the longest of all.
in dn 21 epub there is this blank code. both an empty end section and an empty block quote.
<p class="endsection"></p><blockquote class="gatha"><p> <br/><br/><br/></p>
There is a similar chunk of empty code in DN 32, https://suttacentral.net/dn32/en/sujato#12.1 but this seems to be a case where the pali is paraphrased in the English.
<p></p>
<p></p>
<blockquote class="gatha"><p> <br/><br/><br/></p>
<p> <br/><br/><br/></p>
<p> <br/><br/><br/></p>
<p> <br/><br/><br/><br/><br/></p>
</blockquote>
<p></p>
<p></p>
<p></p>
1 Like
As I keep working on the DN epub, it seems like the end of recitation sections are problematic throughout. For example, the last sutta has a “ending first recitation section” but no ending for the second. The markup is there but it is empty.
There are also empty p class=“endbook” tags at the end of dn13 and dn23. Again, just mentioning what I see in the epubs in case it needs to be tidied in the code.
Network error when clicking Read This Sutta on one of the quotes. URL is …/an1.48/en/sujato
https://suttacentral.net/an1.48/en/sujato
I do not see a single thing that’s as quick to change as the mind.
Server, please slow down?
Thanks, fixed.
Fixed.
I think it’s a similar thing in both cases, the Pali is heavily abbreviated in the translation. We should be more effective about filtering these out, but it’s tricky to catch every case. Nevertheless, my understanding is that normally the browser will filter empty tags anyway, so they shouldn’t have any effect. Are they causing any problems? Oh, the <br> tags probably create extra lines, right?
If there are irregularities in the text, this is just how the source was, so we can’t do anything.
If the irregularities are with markup, we can fix those. You are right, the “end” tags are not always consistent. We should probably review them across the board.
Thanks, I will note this bug.
2 Likes
Yep. That was how I noticed it in the ebook. I realize these things are trivial. But sometimes they can be a sign of a bigger problem or cause problems when derivitave works are created, such as the epubs or pdfs on demand (hint hint 
)
I’m not sure of the origins of the “ending recitation sections”, but I would have thought they are standardized. As I said, I was finding the markup but no translation inside of it.
Much thanks as always!
Indeed. This is one of the reasons we are switching to a new way of precessing texts, which splits the sources into different files. This way it’s much cleaner and easier to operate on things.
1 Like
Yesterday trying to open DN16 the browser got hung up several times trying to load. Looks like you are already on the case.
Well, no, different thing really. DN 16 is kinda problematic, it’s so long and complex. For the sake of simplicity, we have always strived to get one sutta per page, but this is really stretching the limits. On my laptop, and a farly slow connection, it loads English/pali in a few seconds, and I can switch views to side-by-side or line-by-line (these are processor-intensive operations) also in a few seconds. But on older or less performant devices it will be a hassle. I’m honestly not sure what we can do about this, as the one-sutta-per-page assumption is baked so deeply into our site. I’m reluctant to make such changes for the sake of one text.
1 Like
Yes, I agree that one page per sutta is best.
I think the first would should be at, not as. SuttaCentral
As that time the brahmin Kasī-Bhāradvāja’s food distribution was happening.
I just noticed that the Mills translation of snp1.4 is actually a translation of SN 7.11. Could the remaining part of the Snp sutta be added?