SuttaCentral 2021: bug reports here! 🐛

trusolo · May 23, 2022, 1:24pm

Ayya @Pasanna, This seems to be a generic issue, at least on IPads; back button directs to the page you linked. It doesn’t seem specific to any particular portion or a book. I usually don’t use the back button but click on where I need to go back in the top bar, which shows the whole chain of links. Thank you for bringing this up.

sujato · May 23, 2022, 10:33pm

I don’t get that bug with the back button on Chrome, so it may be an iDevice bug. But I still do get a bug, back doesn’t always work. We’ll fix that and hopefully it will fix your problem too.

Pasanna · May 23, 2022, 11:51pm

I’m also having problems with the pwa.
The ‘static’ content pages load but no suttas. I’ve cleared cache and re installed twice.

DhammaByTheHeart · May 25, 2022, 5:50pm

Browser: Chrome, 101.0.4951.61
OS: Android, 8.0.0
Device: LG v20

Browsing directly to SuttaCentral shows undefined. See the screnshot:

Khemarato.bhikkhu · May 26, 2022, 1:06am

I believe there is no /search page. Just click the and type your search in the box

Danny · June 29, 2022, 7:08pm

Search doesn’t seem to be working properly, only dictionary results are found or translated text, the search doesn’t bring up results from the root texts.

mavanyrecords · July 7, 2022, 10:40am

your browser type and version number:
Chrome Version 103.0.5060.114 (Official Build) (x86_64)
your OS: macOS

Reading a sutta in a different language and then pressing “next” when the next sutta isn’t translated in that language will get the tab stuck in a loop refreshing page multiple times per second.

For example SuttaCentral

^ this button will loop the tab.

sabbamitta · July 7, 2022, 10:59am

We had this recently with the Saarländisch Metta Sutta because of a wrong translator name in the code.

I think what normally should happen if a Sutta has no translation in the chosen language is that the Suttaplex card should be shown. This way the user can find out what translations or parallels for that Sutta are available.

@HongDa ? Bhante @sujato ?

Danny · July 7, 2022, 12:57pm

This still doesn’t seem to work. Now I wanted to look for a B.Bodhi translation but also those were not found.

ORsEnTURVi · July 7, 2022, 1:30pm

Well, previously we have 0 result when searching for “dukkha”

Now, we have 1346 results when searching for “dukkha”. Big improvement!

However, we now only have 1 result when searching for “sukha”

Joking just to lighten up the mood, the message is: "Search is broken. Please fix it, thank you "

ORsEnTURVi · July 8, 2022, 4:40pm

Update: Search seems to be working again. We now have 870 results for “sukha”. Yay!

and less results for “dukkha” (1199 compared to 1346 as before). Not too sure if it’s a good indication though

I checked the commits recently on Github but didn’t find any hint to the root cause of the problem.

Is it because @HongDa re-ran the index to fix the search? Could anyone kindly tell me more clearly how did you fix it? Thank you again for fixing the search.

lantern · July 25, 2022, 4:19pm

Wrong simile link?

On https://suttacentral.net/similes, under Lamp, the link in a dark house Mil 2.1.14 doesn’t seem to work for me.

sabbamitta · July 25, 2022, 4:41pm

Yes, there are many wrong links in that file. I am currently about to go through them all so that they can be fixed.

As for the Milindapanha links, try replacing the first digit “2” by “3” → Mil 3.1.14.

gustavo · August 6, 2022, 9:47pm

Hi! I found that the padding is missing in the Spanish version of this Sutta: Digha Nikaya 26
Cakkavatti Sutta. Thank you

sujato · August 10, 2022, 7:09am

Thanks for the heads up. Turns out, it’s not the padding exactly. The problem is that these translations include the Pali subheadings, which in some cases are very long. But browsers don’t know how to hyphenate Pali, so they just keep something like Bhikkhunoāyuvaṇṇādivaḍḍhanakathā (in a large font) all on one line. In our Pali files, we have a (painful and inadequate) process to mitigate this, but we don’t expect Pali headings in translation files.

I’ve removed the Pali from these headings.

Meanwhile, I have previously made a proposal to fix this problem in browsers by creating aliases for hyphenation. A thumbs up would help!

github.com/w3c/csswg-drafts

[css-text] Allow alias for language hyphenation

opened 01:34AM - 30 Jun 20 UTC

sujato

css-text-4 i18n-tracker

The CSS spec provides for hyphenation of text, leaving the choice of language up… to the UA: https://www.w3.org/TR/css-text-4/#hyphenation Currently Firefox offers the best support, but even they only support fairly small subset of the world's languages. https://developer.mozilla.org/en-US/docs/Web/CSS/hyphens The thing is, it is sometimes better to have imperfect hyphenation than none at all. No hyphenation can result in a broken UI and unreadable text, whereas imperfect hyphenation might work fine, or at worst be merely inelegant. I work with texts in Pali and Sanskrit, which can have very long words formed by compounding. There is no browser support for hyphenation for these, nor is there likely to be. Surely these are not the only languages affected. Here is a typical example, rendered in firefox: ![Screenshot from 2020-06-30 09-26-16](https://user-images.githubusercontent.com/6112010/86071515-ccc36280-bac2-11ea-8338-b6cee8657cdf.png) It is possible to hack around this by activating hyphens and setting `lang='la'`: ![Screenshot from 2020-06-30 09-25-58](https://user-images.githubusercontent.com/6112010/86071483-b6b5a200-bac2-11ea-906e-5b711bc018b8.png) This is identical to the result that a proper Pali hyphenation would produce. Note that in tradition Indic orthography, there is no concept of a correct breakpoint; scribes merely wrote to the end of the line and continued on the next line. Thus the traditional practice would agree with the idea that sometimes *any* breakpoint is better than none. However, it's obviously not a good idea to deliberately set a false language. Hence my proposal: **Allow the CSS to declare a language alias for hyphenation**. So the text language is unaffected, and the HTML does not change. But the user can declare via CSS something like: ``` hyphenate-alias-languages: pli, la; ``` Meaning: "for the purpose of hyphenation, Latin and Pali may be substituted." Such substitution would apply only if explicit support for that language is missing. So if `lang='pli'` is set on the HTML, then if one UA has support for Pali hyphens, that is used, if not, it looks for support for Latin.

gustavo · August 10, 2022, 7:47am

Thank you Bhante! I gave a thumb up on Github

gustavo · August 11, 2022, 6:13am

Looking for a translation of “sammā” in Google, I found the one from Suttacentral.net, when you enter the page it is cut off in the cell phone…

sujato · August 14, 2022, 6:21am

Oh thanks, this is an oversight, I have submitted a fix for it.

gustavo · August 14, 2022, 8:00am

Thank you Bhante !

oldmangeorge · September 4, 2022, 4:27pm

Hello, the link to the Jataka takes the user to the Anguttara Nikaya instead: SuttaCentral

Even though the header identifies the Jataka, the text is the contents to AN.

Thank you for reading this. I hope it was useful. I apologize if this has already been addressed.