This example book is written to give readers the example of the Book Language.

Under the book typesetting system, a Book is a collection of texts typesetted for an improved legibility, enumerable pages, with insertion of other helpful resources such as illustrations and hyperlinks.

Books are considered as bound and always presented in two pages for reading.

Typewriter allows quick scribbling of the words in convenient manners, just click on them and get writing!

But it comes with big downsides: you cannot type in multiple writing systems, cannot have defined chapters and sections, cannot include any illustrations, no hyperlinks, and of course, ragged texts.

Typed papers are considered as non-bound and only one page at a time will be presented.

All in all, you cannot write a true Book using a typewriter.

Professional-looking texts, with all the benefits of a real Book can be made, or even mass-produced easily with the help of publishers.

To have your precious texts to be printed, you must send your manuscripts to a publisher, and the manuscript must be written in a special language: the .

allows concise description of the entire shape of your book, any style the book typesetting system can support can be described and printing presses will produce the papers accordingly. You can even try to mimic the look and feel of papers created using a typewriter, if you want to.

(pronounced as /biːtɛk/) is a markup language based on XML, with a resemblance of the . abstracts away the meticulous styling and typesetting configurations, so you can focus on actually writing your texts than debugging the macros. This does come with a downside of not being able to change the given style.

document is divided up to five parts: the Style Declaration, the Cover, the Table of Contents, the Manuscript, and the Index Page, of which the Style Declaration and the Manuscript are the mandatory parts.

The Style Declaration is the very first line of a document. Its syntax is as follows:

The btexdoc tag takes following attributes:

• cover — changes the style of the cover. Possible values: hardcover, none
• inner — changes the style of the body. Possible values: standard, typewriter
• papersize — defines the size of the paper. Possible values: standard

The Cover defines the text on the cover of the book. If your text has no cover, this part can be omitted. Its syntax is as follows:

Only the title tag is mandatory. Cover texts will be printed using a special font that has wider gaps between characters. The title text will be printed in a double-size.

The cover can have different colour with the hue attribute, which takes a number between 0 and 360.

The contents of the Table of Contents is filled in automatically by reading through your manuscript; parts, chapters and sections will be added. Its syntax is as follows:

The optional title attribute allows a custom name can be given to this page. If unspecified, the default name is “Table of Contents”.

The tag <tableofcontents/> is an internal tag used by the typesetter.

This is the part where you actually write your body texts in. The body text can have the following tags:

• part — inserts part separation page to your book
• chapter, section — inserts a new chapter/section. If an alternative name is required on the Table of Contents, the alt attribute can be used. If the chapter/section needs to be hidden on the Table of Contents, add the hide="1" attribute. If the chapter must start on a new page, see the Macro Definition
• p — inserts a new paragraph. The body texts must be written inside this tag. All paragraphs will have a 16-pixel indentation, with the following exceptions: first p of the part/chapter/section; first p after br, newpage, callout, ul, ol or anonbreak
• span — allows changing the colour or the style of the texts. The colour must be specified in the colour attribute. Six-digit hex code, three-digit hex code and CSS Colours Level 4 named colours are supported. Note that all the colours will be rounded to the nearest three-digit hex code
• emph — is a special case of the span tag. The resulting text will be red
• itemname — is a special case of the span tag used to highlight the name of the ingame item. The resulting text will be blue
• targetname — is a special case of the span tag used to highlight the name of an arbitrary target or goals. The resulting text will be green
• code — is a special case of the span tag used to highlight the code element in-line. The resulting text will be magenta and monospaced
• br — self-closing tag; inserts an anonymous line break
• newpage — self-closing tag; inserts an anonymous page break
• anonbreak — self-closing tag; inserts a paragraph break in the text. The break will be in a form of a long straight line on the centre of the text. Useful for typesetting novels
• callout — is a paragraph box that holds a text in a grey box
• ul — starts an unordered list. List elements are defined using the li tag
• ol — starts an ordered list. List elements are defined using the li tag
• fullpagebox — is used to typeset its child tags into a box that fills an entire page, with its contents centred on the page. Must be used after the newpage
• btex — self-closing tag; inserts an inline form of the logo in the text

Self-closing tags have no child tags. To use a self-closing tag, simply do <tagname/>.

The part, chapter and section takes optional type attributes which changes how the chapter should be numbered. Available options are:

• a — use alphabets for the number (a, b, c, …)
• A — use majuscule alphabets for the number (A, B, C, …)
• i — use Roman numerals for the number (i, ii, iii, …)
• I — use majuscule Roman numerals for the number (I, II, III, …)
• 1 — use Arabic numerals (1, 2, 3)

By default, parts use majuscule Roman numerals and others use Arabic. Alternative styling for the part and the chapter can be defined using the Macro Definition.

The p and callout tags can take align attribute, which controls how the text should be aligned. Available options are:

• left — aligns the text flush to the left without breaking words, also known as ragged-right
• right — aligns the text flush to the right without breaking words, also known as ragged-left
• center — aligns the text aligned at the centre along the width of the paper without breaking words
• justify — aligns the text as evenly as possible, similar to real books. This is the default value.

The p, span and callout tags also take class="code" attribute, which results in the text printed using the code font.

Hyperlinks can be defined using index and a tags.

• index — will define a target for a link. Indices require a unique identifier to work as a link, and the identifier must be defined in the id attribute
• a — will make its child texts to be clickable. The link target (index identifier) must be defined in the href attribute

Figures, or external images can be inserted using the self-closing img tag. This tag inserts the image at the centre of the page, starting from the current line; if the size is taller than the remaining lines, the image will be printed onto the next page. Its syntax is as follows:

The height attribute specifies the height of the image in the number of lines, rather than pixels, the width is calculated automatically; image width wider than the text width will cause an error. The tag optionally takes caption attribute which prints a text below the image.

Supported image formats: JPEG, PNG, BMP or TGA

The contents of the Index Page is filled in automatically by reading through your manuscript. All the usage of index tags will be shown here. Its syntax is as follows:

The optional title attribute allows a custom name can be given to this page. If unspecified, the default name is “Index”.

The tag <tableofindices/> is an internal tag used by the typesetter.

The document must begin with the opening btexdoc tag, and therefore must end with a matching closing tag. Simply write away </btexdoc> and the document is finished.

The finished book description using can be sent to a publisher, and if there are no errors on your submission, the printed books of specified number of copies will be delivered to your location within a reasonable amount of business days. Happy writing!

This part explains the set of macros the typesetting system uses, and how you can manipulate them to introduce a limited set of customisations.

Macros can be defined using the macrodef tag which comes before the cover tag. Its syntax is as follows:

Internally, part and chapter headings are printed using macros. Changing the value of the macro will change how the heading numbers are printed. The following is a list of names and default values:

• thepart — Part heading. Default: Part %1$s
• parttype — Default style of the part tag. Default: I
• thechapter — Chapter heading. Default: %1$s
• chaptertype — Default style of the chapter tag. Default: 1
• chapteronnewpage — Controls if a chapter must start on a new page. Put non-zero value to enable this behaviour. Default: 0
• resetchapterafterpart — Controls if the chapter number should reset after a part. Put non-zero value to enable this behaviour. Default: 0
• parindent — Controls the indentation size of the paragraphs. Default: 16

The argument key %1$s will be replaced into a number, Roman numerals, etc. depending on the value of type attribute.

These macros can be used to localise the chapter headings for your language. For example, in Korean text, the following idiomatic definition will be useful:

Defining the text to be printed outside the typesetting system, such as the name of the sender and the recipient, can be desired. These texts can be used with the self-closing v tag. This tag can also be used to use an ingame string as well.

To print an external variable, use the id attribute; to print an ingame string, use fromgame attribute. Note that only one of two attributes must be used, using both attributes in a single tag will cause an error.

In order to print a text such as “The total is 1234”, the bucks tag can be used along with the v tag. The following code is an example case:

If the external variable invoice_total_amount contains a string toomany, this code would print out “The total is toomany”.

To accommodate the Korean Postposition transformations, special v series tags are added:

• veun vneun — 은/는
• vi vga — 이/가
• veul vreul — 을/를
• vwa vgwa — 와/과
• vro veuro — 로/으로

Either of the tag in the pair can be used; they will put the correct postposition based on the word. In other words, veun and vneun are identical.

These tags can be used in the following situation: suppose you have a document,

The variables will be resolved based on the current ingame language, then the necessary linguistic processing is performed, which would result in a following paragraph (text in blue denotes the text is inserted using the tags):

The engine is not fast; it takes at least a few seconds to print a book. The “waiting” system is there because the book is being printed in the background on separate threads (yes, they are multi-threaded!) to not interfere with the normal gameplay, or else the players will encounter the freezing every time the book is being printed, and this would be a huge minus towards the gameplay experience.

If the process exits without any error, the mailing system will be notified and will send the mail containing finished books to the player; if the process exits with errors, the mail containing details of the errors will be sent instead.

For this reason, the “printing press” is not exposed to the player, they only get to interact with it indirectly through the “publisher” via mail.