| Re: [jakartaee-platform-dev] [jakartaee-spec-project-leads] [External] : Re: specification document html version generation settings |
This workaround is implemented now. The Connectors 2.0 specification HTML and PDF files are being served from their Jakarta EE Specifications folder.
We are working on longer term recommendations. For now, I'd suggest anything bigger than 10-20 MB be served from the Specifications folder -- that is until we can resolve, or better clarify the hosting issues we are currently facing.
Thanks,
-- Ed
I was trying to fix this without forcing the team to create a new document and upload it. For the immediate problem, we have a workaround which is to just take the document that was originally pushed in the PR and host it from the Eclipse Specification download page.
That should suffice for the immediate term. Whenever a revision is planned, we can update the document and it's hosted location at that time.
-- Ed
On 8/25/2021 8:51 AM, Scott Stark wrote:
Thanks Dmitri. You could create PR against the Jakarta Connectors project, but I would create an issue to double check that they have time to accept it.
On Aug 25, 2021 at 10:08:09 AM, Dmitri Cerkas via jakartaee-platform-dev <jakartaee-platform-dev@xxxxxxxxxxx> wrote:
If you want I can convert images in SVG format and they will be a few dozens kilobytes in size.
Dmitri.
On Wednesday, August 25, 2021, 05:02:17 PM GMT+2, Scott Stark <starksm64@xxxxxxxxx> wrote:
_______________________________________________FYI, I created the following issue on the Jakarta Connectors project about the excessively large html version of the spec that is being created:
It seems like specs that were generated from the original JCA based Adobe Illustrator exports have very large image sizes and are using a <data-uri /> setting in the asciidoctor-maven-plugin setting to embed images into the html document. Just turning that off reduced the generated html size from ~59Mb to 1.1Mb. The CDI specification does not do this, so it is likely just a setting inherited from some initial project import.
It seems that files above about 50Mb are not being downloaded completely by the EF infrastructure. Beyond that problem, such a large html file kind of defeats the purpose of producing a streamable version of the specification.
The image sizes could also be reduced by several Mbs by exporting them as low quality jpgs instead of high quality without any noticeable loss in resolution to also reduce the generated pdf file size.
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev
_______________________________________________ jakartaee-spec-project-leads mailing list jakartaee-spec-project-leads@xxxxxxxxxxx To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads__;!!ACWV5N9M2RV99hQ!bvc4PH_mIz71nrncX_iAgJKXHXpSf7L6wvcPx-nFRl4q5SBylw-Qs6-1oTpU7cI$
_______________________________________________ jakartaee-spec-project-leads mailing list jakartaee-spec-project-leads@xxxxxxxxxxx To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads__;!!ACWV5N9M2RV99hQ!bqHjtfn6baljbqDa9Pw0LW0JMtqcWuVqyf2AMPYdXuOvOf3Gypxroynvej6jiW8$