This PDF/HTML is going to be sent via emails to individuals. The idea is that those who read the emails could be able to check and validate the form content; I don’t need them to change anything, at least for now. I think it does not need to be accessed offline.
About the second paragraph. The thing is that I expect that if I deploy ODK in my organization then we would have to create multiple forms over time, and if I use mail merge and scripts, then we would have to create a template and script for each form we deploy, and by the tests I did using this (by your suggestion in other post), that is not easy and fast enough. I don’t know much about google mail merge and google apps scripts, but I expect that to be more or less the same.
Another problem I had is that using pyODK I can access form submissions data but stripped from “visualization” information like labels and hints. So in my python script I needed to manually type that information because pyODK does not have easy methods to access “visual“ information in form definitions. Maybe I could be able to access that info using those HTML verb methods in pyODK, but I don’t know much about that and it adds another layer of complexity about creating scripts for doing mail merge for a given form.
Finally, Other issue is that I want to deploy something that other people are able to manage and maintain without much technical knowledge, because I will not be in this organization much time, I expect. So it would be better for me to be able to write a script that works for every possible form than writing a new script every time a new form is created, and maybe I will not be here when those new forms will be deployed.