This section contains frequently asked questions about the capabilities and use of FontoXML Editor.
We have implemented applications with SX modules for standards such as, but not limited to: DITA, TEI, XHTML, JATS and S1000D. We have also implemented many other applications with SX modules for specializations of the aforementioned standards and completely custom schemas.
Feel free to contact us if you would like to know more about the configuration of these schemas or what it would take to configure unlisted or specialized elements and attributes. Our schema experience module is designed to easily add support for many kinds of XML elements.
Fonto works optimally in Chrome because it offers the best overall support for the latest web standards as well as superior performance. We guarantee error-free behavior and a non-broken visual interface in its two latest stable major versions at the point of FontoXML version release, only with the exception of known browser bugs which we will try to work around.
With ‘error-free behavior’ we mean that every function of the application will meet the acceptance criteria of the issue in which it was created or changed. The user will always be able to reach their goals within the scope of the agreed functionality, although the exact way in which they do so may differ slightly from environment to environment.
With ‘non-broken visual interface’ we mean that the interface will nowhere be obviously distorted (incorrect layout, unreadable text, etc). Decorative effects may be rendered differently between combinations of operating system and browser versions.
We also support the two latest stable major versions of Firefox and the latest stable major version of Microsoft Edge and Safari. They may however present the user with non-blocking differences in visual appearance and perform slower than Chrome. Currently, we don’t actively support any other browsers or versions. FontoXML will notify users if they try to open the application in an environment we don’t support. We encourage users to download Chrome if they hadn’t already; it is a free and lightweight browser with a large worldwide market share that’s available for all major operating systems.
We don’t exclude specific operating systems. Fonto will work on recent versions of Microsoft Windows and Mac OS X and on many distributions of Linux. One thing to consider, especially for Windows, is that older machines may come with poor performance which is not ideal for a state of the art application like Fonto.
Fonto is a responsive web application that adapts to the size of the screen it is viewed on. However, we do recommend using a display at least 1280 pixels wide.
We support direct keyboard input only; this excludes input method editors (IME). Fonto cannot be used on tablets, smartphones and doesn’t work with touch interfaces.
We impose no specific limit on the number or size of documents that can be concurrently loaded in Fonto. Obviously, smaller documents will perform better than very large ones but the actual limits depend on the machine and browser used.
Reducing the total size of the project file and chunking documents into smaller ones are probably the best ways to prevent performance problems and match principles of structured authoring as well.
The Fonto development tools can only provide you with the FontoXML platform in the form of an editor instance. To create an editor instance you will need to supply your own schema in the XSD format.
No. FontoXML will have to be configured to have your content visible.
Element configuration is done by using our Content Visualization Kit (CVK). This contains what we call families. Every family represents a grouping based on semantics which determine an elements visualization and behavior.
Yes. We allow you to create custom modals, sidebars, and popovers through the use of our FontoXML Design System (FDS) components. While you also have the possibility to create a custom visualization for an element using the Object family we do advise against using this unless there is no other solution. If you feel this is the case please use our support board so we can provide you with needed assistance.
Your XML file may contain a BOM character. These are often not noticed or ignored by online validators.
No. Outside of using our APIs to configure your editor you are free to use the programming languages as you see fit.