You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A long-standing problem with Pali and Sanskrit is that certain words are very long, making it difficult to produce decent layout on the web.
Ideally this would work via browser hyphenation, but there is no support for Pali or Sanskrit. I have proposed a solution using fallbacks in CSS but this will take time, if it is ever implemented.
In the past, SC added soft-hyphens to the Pali text, but it ended up creating a bunch of problems with search, reusing texts, etc.
Karl based on Vimala's work has now implemented a js-based hyphenation for Pali.
Soft-hyphens must be inserted as late as practical. We found that they tend to create issues, sometimes unpredictably, so they should not be in the text that is used for search, or anything else. The problem they are solving is purely about presentation in a specific context, so they should only apply in that context, i.e. when the text is rendered in the browser. Thus I think it will be best to apply them client-side. To avoid slowing the page, do it lazily.
As for minimum word length, Karl uses it at 20 characters for voice. Let's try that for starters.
The text was updated successfully, but these errors were encountered:
A long-standing problem with Pali and Sanskrit is that certain words are very long, making it difficult to produce decent layout on the web.
Ideally this would work via browser hyphenation, but there is no support for Pali or Sanskrit. I have proposed a solution using fallbacks in CSS but this will take time, if it is ever implemented.
In the past, SC added soft-hyphens to the Pali text, but it ended up creating a bunch of problems with search, reusing texts, etc.
Karl based on Vimala's work has now implemented a js-based hyphenation for Pali.
https://github.com/sc-voice/js-ebt/tree/master/src
Let us implement this on SC.
Soft-hyphens must be inserted as late as practical. We found that they tend to create issues, sometimes unpredictably, so they should not be in the text that is used for search, or anything else. The problem they are solving is purely about presentation in a specific context, so they should only apply in that context, i.e. when the text is rendered in the browser. Thus I think it will be best to apply them client-side. To avoid slowing the page, do it lazily.
As for minimum word length, Karl uses it at 20 characters for voice. Let's try that for starters.
The text was updated successfully, but these errors were encountered: