I’m trying to understand this part of the forum
https://typst.app/docs/reference/scripting/#:~:text=If%20a%20character%20would%20continue%20the%20expression%20but%20should%20be%20interpreted%20as%20text%2C%20the%20expression%20can%20forcibly%20be%20ended%20with%20a%20semicolon%20(%3B)
Modules
I’m trying to explain my problem with the screenshot. See the message “File not found”
I’m working offline. Both files are in the same directory.
I must have missed something.
I’m far from experienced in Typst, but looking at your screenshot, I think it should be #include "tables.typ". I had a similar problem a while ago; I think you use#import "…"for packages or templates from Typst Universe for instance, not for files in the same folder/directory.
This should completely work if this file is sibling to your main file (regardless of whether you use include or import). What editor are you using?
Note that include and import have two different purposes:
import imports the definitions from the module so that you can programmatically access them in your file. Content that is defined in the imported module and that is not bound to any variable will not be available.include includes all contents into the current file. However, definitions are not imported into the current scope.Sometimes, you will even want to do both!
I haven’t yet come across the term “sibling” while reading the documentary.
I would like to understand the effects of import and include using a simple example.
I use Typesetter 13.1.
Regarding my intention, please read my reply to Mc-Zen.
That would be one explanation.
“Sibling” is the standard English non-gender-specific word covering both “brother and sister”, so here it means two or more files in the same folder.
Mark
It took me a while to understand the concept of projects in Typst.
Once a project is created, images can be added using the Navigator, similarly, new content files can be created with the extension “typ”. In my attempt, the name of the content file is “chapter 2.typ”.
This file contains the content that will later be incorporated into the main file.
Despite much trial and error, I haven’t yet managed to integrate them into the main file.
Using the functions #import or #include “chapter 2” produces the following output:
File not found: chapter 2
Unfortunately, the documentation is unclear at this point, or have I overlooked something?
As far as I know, the Typesetter editor is restricted by operating system sandboxing in which files it is allowed to read, so maybe that’s the issue? Typesetter is a third-party project, so I’m not sure. If you are comfortable with using a terminal, you could try checking whether you can reproduce the problem with the official Typst command line compiler or whether that just works.
You are right. the better place is a question to Hadn Trowell, the author of typesetter 0.16.