The answer is here:
Hear now the doctrine of the <j> tag!
Verse lines are finicky to typeset. Sometimes a line is just too long and you get something like this.
A brahmin’s so-called because they have banished
evil,
an ascetic’s so-called since they live a serene life.
Or, worse:
A brahmin’s so-called because they have banished ev-
il,
an ascetic’s so-called since they live a serene life.
Throw a <j> tag in:
A brahmin’s so-called <j>because they have banished evil,
an ascetic’s so-called <…
See also:
But yeah if Google Play doesn’t like it we should fix it. It’s not really relevant in ereaders anyway (because the reading environment is arbitrary) so we should probably just strip them from there.
Any validation errors, please post them here, that would be very helpful.
Browsers parse and use custom tags just fine, regardless of what a validator says. The <j> tag is a special element that creates an “enjambment”, i.e. it splits a long line of verse over two lines, like this.
[Screenshot from 2023-03-13 10-28-38]
But yeah if Google Play doesn’t like it we should fix it. It’s not really relevant in ereaders anyway (because the reading environment is arbitrary) so we should probably j…
