Though for Epubs we have our preferred alternative that we utilise through
Tpt's tool on toollabs for the epub version; well we do that at enWS.

I am more concerned by the PDF version loss of tables which are critical
for many works at the WSes, especially where they implement a ToC (front
and centre of many works) through a table.  It seems that we have a
WP-focused solution that disregards the WSes. There is a clear statement
the table issue will not be a priority to resolve. What is the urgency that
tables are not a concern? So we have to try and test this without something
in beta, and no knowledge of what is the issue with tables. Seems less than
satisfactory, and less than consultative.

Further the works are going to reproduced in two columns, and there is no
indication on how works with images will reproduce. Again it seems wholly
unsatisfactory that there is no capacity to view this as a beta function,
and it has to be done through a javascript hack. Why the lack of
resolution, why the lack of clear vision of what is an issue in
reproduction.

For the bulk of our users at enWS, they are clearly beta feature users,
rather than hackers of javascript files. The approach of javascript being
the testing methodology seems focused at only the technical capable, not
the broad spectrum of users.

Regards, Billinghurst