You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
need an api call that will convert the justifications into separate PDFs - the call should return whether the conversion runs successfully. Any files that are included in the document store are presented "in the same directory" as the main text so that inclusions (for images and possible bibliography) can also be made
for latex a "standard style" will be assumed and the VM that the latex processing runs on will have only that style included so that attempts to use a different style will fail.
the above probably means that a "document processing" micro service needs to be created. It might be best that the front end talks to that directly so that this issue would really belong in the project that creates the micro service
The text was updated successfully, but these errors were encountered:
this has mostly been completed for Latex - however not as separate micro service, but integrated in with the API micro service - need to be able to deploy successfully
given that i see a latex processing page within the justifications when set to latex, i would think this is complete. but i note that there's no pdf button for the other types (ASCIIDOC and RST). does this mean the ticket still has work to do? or is this hidden under the hood for when submission is done?
i note that theres no checks yet to verify if the latex does compile.
need an api call that will convert the justifications into separate PDFs - the call should return whether the conversion runs successfully. Any files that are included in the document store are presented "in the same directory" as the main text so that inclusions (for images and possible bibliography) can also be made
the above probably means that a "document processing" micro service needs to be created. It might be best that the front end talks to that directly so that this issue would really belong in the project that creates the micro service
The text was updated successfully, but these errors were encountered: