2020.1

Alternatively you could import resources and scripts from another template; click File >Import
Resources... in the menu and select a template to import resources from (see ).
Once added or imported, internal resources are accessed using a relative path, depending
where they're called from. Resources can be located in the following folders:
l images/ contains the files in the Images folder.
l fonts/ contains the files in the Fonts folder.
l css/ contains the files in the Stylesheets folder.
l js/ contains the files in the JavaScripts folder.
l snippets/ contains the files in the Snippets folder.
When refering to them, normally you would simply use the path directly with the file name. The
structure within those folders is maintained, so if you create a "signatures" folder within the
"Images" folder, you need to use that structure, for example in HTML: <img
src="images/signatures/johnsmith.gif">. In scripts, you can refer to them in the same way, for
example:
results.loadhtml("snippets/en/navbar.html");
See also: "Loading a snippet via a script" on page404 and "Writing your own scripts" on
page377.
Note
When referring to images or fonts from a CSS file, you need to remember that the current
path is css/, meaning you can't just call images/image.jpg. Use a relative path, for
example: #header {background-image: url('../images/image.jpg'); }
External resources
External resources are not stored in the template, but on the local hard drive or on a network
drive. They are accessed using a path. The path must have forward slashes, for example <img
src="file:///c:/resources/images/signatures/johnsmith.gif"> or var json_variables = loadjson
("file:///d:/jsondata/variables.json");. The complete syntax is:file://<host>/<path>. If the host
is"localhost", it can be omitted, as it is in the example, resulting infile:///<path>. The empty
string is interpreted as `the machine from which the URL is being interpreted'.
Page 112