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.
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.
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!
Not sure if I should to report this on suttacentral or on the calling app (@benmneb).
I use the PTS Reference to Sutta Number tool (thank you very much).
It appends ?ref=benmneb.github.io/pts-converter/ to the end of the ‘Read this sutta’ links, so I might look up S III 109 and it will form the following url (for English): https://suttacentral.net/sn22.84/en/sujato?layout=sidebyside&reference=main/pts¬es=asterisk&highlight=false&script=latin#pts-vp-pli3.109?ref=benmneb.github.io/pts-converter/
But that takes me to the start of SN 22.84
If I remove the ?ref=benmneb.github.io/pts-converter/ from the end of the url, then it scrolls to pts-vp-pli3.109 which is the behaviour that I was actually hoping for.
Very nice. Thanks for letting me know. This is my fault, I put that on the end so Sujato knows where all the traffic I send there comes from without thinking there might already be query strings. I’ll fix it this week so it works for everyone.
If you find any other problems with the converter, post and issue on GitHub or @ me here. Thanks again