4 ms·
Hello from a fellow LaTeX enthusiast. Out of curiosity, how do you handle external assets (e.g., images [1])? Extending the retailer example - suppose such co
by vitorsr 6y ago
Hello from a fellow LaTeX enthusiast.
Out of curiosity, how do you handle external assets (e.g., images [1])?
Extending the retailer example - suppose such company would further like to include a thumbnail for each product in a receipt. Or, extending the inspection example included in the support section, suppose the sender wishes to include a blueprint or an external document. How should they proceed?
Some questions in anticipation. What if it is not possible to store the whole catalog locally for a given receipt template? What if catalog items are regarded as sensitive information for the company?
[1] https://tex.stackexchange.com/questions/5433/can-i-use-an-image-located-on-the-web-in-a-latex-document https://tex.stackexchange.com/questions/5433/can-i-use-an-im...
- VelNZ 6y agoHey, there's quite a few LaTeX enthusiasts on HN! Great question and observation! Currently, the platform doesn't handle external non-text assets at all. This is something I will definitely be incorporating in the future. You can submit a private template where you bundle your logo and any other images and those will compile as normal with \includegraphics{}, but users of the template can't submit images or other assets beyond text at this stage. An image is a string of characters, so I don't imagine it will be too difficult to accept an image as a new document variable type, send it along with the bundle that goes to the workers, recreate it as a .jpg, and make use of it in the template. The difficulty then becomes coding the template in a way that if a user specifies a really tall or really wide image, the document still looks good.