> For the complete documentation index, see [llms.txt](https://tracer.gitbook.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tracer.gitbook.io/manual/support/faq.md).

# FAQ

## Q. How do I cite TRACER?

The first TRACER article in English is still under publication. Depending on your referencing style, you can adapt the following:

Büchler, M., Franzini, G., Franzini, E. Bulert, K. (2018 forthcoming) ‘TRACER - a multilevel framework for historical Text Reuse detection’, *Journal of Data Mining and Digital Humanities - Special Issue on Computer-Aided Processing of Intertextuality in Ancient Languages*.

## Q. Can I reuse TRACER’s code in my work?

Yes. As per TRACER’s Academic Free License (see [Copyright](/manual/manual/introduction/tracer-overview.md)), you’re allowed to repurpose the source code as long as you credit the source, share your code in a similar fashion and don’t financially profit from it.

## Q. Where can I find information about future TRACER tutorials?

The [www.etrap.eu](https://github.com/gfranzini/tracer-manual/tree/fcf664a1bd71584352b193a070b981eb8b89f224/www.etrap.eu) website always lists upcoming tutorials a few weeks in advance. These are typically run during conferences or summer schools.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://tracer.gitbook.io/manual/support/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.