This file contains ambiguous Unicode characters that may be confused with others in your current locale. If your use case is intentional and legitimate, you can safely ignore this warning. Use the Escape button to highlight these characters.
title: Technical aspects of generating books
sort: 5
- Now the graphic design of La Distancia Levenshtein lee a Cortázar is using html and weasyprint, but weasyprint does not support javascript. All variations of the book have to be generated by the layer generating the scripts. This doesn’t have to be a problem, but it does offer a limitation. Weasyprint is implemented in Python, but it is also implementing it's own browser/render engine. The development of the library is limited.
- Gijs has a clear prreference to work with paged.js because it supports javascript. On the other side it needs a browser running on the server (100MB). Another downside of pagedjs is that it is running in node, that means an extra layer / technology to maintain.
- What is the api of the publishing platform? What is infrastructure of the publishing house? On what server? How to deal with safety? How to make sure it keeps running? How to avoid server overload? Harmful robots? Or multiple users at the same time? Make a waiting row? What is the scale of this project? For now, there is the proposal to run the server a year to see what happens.
- What about the ecological impact of the 'infinite' generation of books? How do we calculate that? Include or exclude it?