glyph 0.4.2 → 0.5.0

data/book/text/text_editing/macro_intro.glyph

@@ -4,11 +4,11 @@ The most important concept to grasp about Glyph is the concept of _macro_.
 
 A Glyph macro is, in a nutshell, an identifier of some kind that wraps a value or parameters within square brackets. More specifically:
 * The macro identifier can contain _any_ character except for: @\[@, @\]@, @\\@, @\|@, code[@] or spaces.
-* The delimiters can be either @\[@ and @\]@ or @\[=@ and @=\]@ (\.fmi[differences between delimiters|#esc_quot]). 
-* The value can be anything, even other macros. If a macro supports more than one parameter, they must be separated with @\|@. For example, the %>[link] can take an optional second parameter for the link text: @\..[=link[#link_id\|This is the link text]=]@.
+* The delimiters can be either @\[@ and @\]@ or @\[=@ and @=\]@ (\/fmi[differences between delimiters|#esc_quot]). 
+* The value can be anything, even other macros. If a macro supports more than one parameter, they must be separated with @\|@. For example, the %>[link] can take an optional second parameter for the link text: @\/.[=link[#link_id\|This is the link text]=]@.
 * A macro can also have _attributes_, which look exactly like macros but their identifier starts with a code[@].
 
 A macro can often have one or more aliases. For example, @=>@ is an alias for the %>[link], so the following macro calls are equivalent:
-* code[=\.=>[#test\|Test Section]=]
-* code[=\.link[#test\|Test Section]=]
+* code[=\/=>[#test\|Test Section]=]
+* code[=\/link[#test\|Test Section]=]
 	]

data/book/text/text_editing/section_aliases.glyph

@@ -1,28 +1,28 @@
-	txt[
+  txt[
 There are _a lot_ of macros that can be used in the same way as @section@, one for each element commonly used in =>[http://en.wikipedia.org/wiki/Book_design|book design]. 
 
 The following table lists the identifiers of all section-like macros, divided according to the part of the book they should be placed in:
-	]
-	table[
-  	tr[
-   		th[Frontmatter]
-    	td[txt[@imprint@ ^†^, @dedication@ ^†^, @inspiration@ ^†^, @foreword@ ^‡^, @introduction@ ^‡^, @acknowledgement@ ^‡^, @prologue@ ^‡^, @toc@ ^*^]]
-  	]
-  	tr[
-    	th[Bodymatter]
-    	td[txt[@volume@, @book@, @part@, @chapter@]]
-  	]
-  	tr[
-    	th[Backmatter]
-    	td[txt[@epilogue@ ^‡^, @afterword@ ^‡^, @postscript@ ^†^, @appendix@, @addendum@ ^‡^, @glossary@ ^**‡^, @colophon@ ^†^, @bibliography@ ^**‡^, @promotion@ ^†^, @references@ ^**‡^, @index@ ^**‡^, @lot@ ^**‡^, @lof@ ^**‡^]]
-  	]
-	]
+  ]
+  table[
+    tr[
+      th[Frontmatter]
+      td[txt[@imprint@ ^†^, @dedication@ ^†^, @inspiration@ ^†^, @foreword@ ^‡^, @introduction@ ^‡^, @acknowledgement@ ^‡^, @prologue@ ^‡^, @toc@ ^*^]]
+    ]
+    tr[
+      th[Bodymatter]
+      td[txt[@volume@, @book@, @part@, @chapter@]]
+    ]
+    tr[
+      th[Backmatter]
+      td[txt[@epilogue@ ^‡^, @afterword@ ^‡^, @postscript@ ^†^, @appendix@, @addendum@ ^‡^, @glossary@ ^**‡^, @colophon@ ^†^, @bibliography@ ^**‡^, @promotion@ ^†^, @references@ ^**‡^, @index@ ^**‡^, @lot@ ^**‡^, @lof@ ^**‡^]]
+    ]
+  ]
 
-	p[strong[*]: The %>[toc] is used to generate the Table of Contents automatically, and it takes no parameters.]
-	p[strong[**]: This macro is likely to be extended in future versions to generate/aggregate content automatically.]
-	p[strong[†]: This section is not listed in the Table of Contents.]
-	p[strong[‡]: Any subsection of this section is not listed in the Table of Contents.]
+  p[strong[*]: The %>[toc] is used to generate the Table of Contents automatically, and it takes no parameters.]
+  p[strong[**]: This macro is likely to be extended in future versions to generate/aggregate content automatically.]
+  p[strong[†]: This section is not listed in the Table of Contents.]
+  p[strong[‡]: Any subsection of this section is not listed in the Table of Contents.]
 
-	note[
-		code[frontmatter], code[bodymatter] and code[backmatter] are also macro identifiers, but they are also exposed as attributes for the %>[book] and the %>[article], so if you're using either of these two macros as your root macro for your document, there's no need to use them explicitly.
-	]
+  note[
+    code[frontmatter], code[bodymatter] and code[backmatter] are also macro identifiers, but they are also exposed as attributes for the %>[book] and the %>[article], so if you're using either of these two macros as your root macro for your document, there's no need to use them explicitly.
+  ]

data/book/text/text_editing/sections.glyph

@@ -1,7 +1,7 @@
 
-	p[Glyph documents are normally organized as a hierarchical tree of nested chapters, appendixes, sections, etc. To define a section, use the %>[section] (aliased by code[§]), like so:]
+  p[Glyph documents are normally organized as a hierarchical tree of nested chapters, appendixes, sections, etc. To define a section, use the %>[section] (aliased by code[§]), like so:]
 
-	highlight[=html|
+  highlight[=html|
 section[
   @title[Section #1]
 Write the section contents here...
@@ -10,13 +10,13 @@ Write the section contents here...
 This section is nested into the previous one.
   ] --[End of Section #2]
 ] --[End of Section #1]
-	=]
+  =]
 
-	txt[This example defines two nested sections. If the code[@title] attribute is specified like in this case, it will be converted to a proper HTML header and it will appear in the Table of Contents (see the %>[toc]).
+  txt[This example defines two nested sections. If the code[@title] attribute is specified like in this case, it will be converted to a proper HTML header and it will appear in the Table of Contents (see the %>[toc]).
 
 Note an important difference from HTML: there is no need for an explicit level for the headers, as it will be determined at runtime when the document is compiled, based on how sections are nested. The previous code snippet (taken as it is), for example, will be transformed into the following HTML code:]
 
-	highlight[=html|
+  highlight[=html|
 <div class="section">
   <h2>Section #1</h2>
   <p>Write the section contents here...</p>
@@ -25,30 +25,30 @@ Note an important difference from HTML: there is no need for an explicit level f
     <p>This section is nested in the previous one</p>
   </div>
 </div>
-	=]
+  =]
 
-	txt[
+  txt[
 By default, in Glyph the first header level is _2_, so the two headers are rendered as @h2@ and @h3@, respectively (@--\[...\]@ macros are _comments_, therefore they are not included in the final output).
-	]
+  ]
   section[
-		@title[Markup-aware sections]
-		txt[Although Glyph can be used on its own to produce valid HTML or XML code, you may often want to use &[markups] to save some typing. Typically, you'll end up writing a lot of code like this:]
-	
-		highlight[=html|
+    @title[Markup-aware sections]
+    txt[Although Glyph can be used on its own to produce valid HTML or XML code, you may often want to use &[markups] to save some typing. Typically, you'll end up writing a lot of code like this:]
+  
+    highlight[=html|
 section[
-	@title[My Textile section]
-	textile[
+  @title[My Textile section]
+  textile[
 Textile markup can be used _here_.
-	]
+  ]
 ]
-		=]
-		txt[To save you even more typing, you can use the %>[textile_section] (aliased by @txt_section@ and @§txt@) and the %>[markdown_section] (aliased by @md_section@ and @§md@). By doing so, the previous code snippet can be written like this:]
-		highlight[=html|
+    =]
+    txt[To save you even more typing, you can use the %>[textile_section] (aliased by @txt_section@ and @§txt@) and the %>[markdown_section] (aliased by @md_section@ and @§md@). By doing so, the previous code snippet can be written like this:]
+    highlight[=html|
 §txt[
-	@title[My Textile section]
+  @title[My Textile section]
 Textile markup can be used _here_.
 ]
-		=]
-		tip[txt[On an Italian keyboard, you can type a @§@ character by pressing *SHIFT + &ugrave;*. Unfortunately, that's about the only useful thing an Italian keyboard does. If you use Vim, you can map it to some key sequence like @''s@, like this: @map! ''s <C-V>u00A7@.]]
+    =]
+    tip[txt[On an Italian keyboard, you can type a @§@ character by pressing *SHIFT + &ugrave;*. Unfortunately, that's about the only useful thing an Italian keyboard does. If you use Vim, you can map it to some key sequence like @''s@, like this: @map! ''s <C-V>u00A7@.]]
  
-	]
+  ]

data/book/text/text_editing/stylesheets.glyph

@@ -1,34 +1,34 @@
-	p[Currently, Glyph does not provide any native way to format text and pages. The reason is that there's absolutely no need for that: CSS does the job just fine. In particular, CSS3 offers specific attributes and elements that can be used specifically for paginated documents. That's no replacement for LaTeX by any means, but it is enough if you're not looking for advanced typographical features.]
-	p[You can embed CSS files using the %>[style], like this:]
-	p[code[= style[default.css] =]]
-	txt[In this case, the %>[style] looks for a @default.css@ file in the @/styles@ folder of your Glyph project _and_ among the default Glyph stylesheets, and embeds it within a @<style>@ tag. If you supply a file with a @.sass@ or @.scss@ extension, it will interpret it as a Sass file and convert it to CSS automatically (if the _Haml_ gem is installed).]
-	tip[
+  p[Currently, Glyph does not provide any native way to format text and pages. The reason is that there's absolutely no need for that: CSS does the job just fine. In particular, CSS3 offers specific attributes and elements that can be used specifically for paginated documents. That's no replacement for LaTeX by any means, but it is enough if you're not looking for advanced typographical features.]
+  p[You can embed CSS files using the %>[style], like this:]
+  p[code[= style[default.css] =]]
+  txt[In this case, the %>[style] looks for a @default.css@ file in the @/styles@ folder of your Glyph project _and_ among the default Glyph stylesheets, and embeds it within a @<style>@ tag. If you supply a file with a @.sass@ or @.scss@ extension, it will interpret it as a Sass file and convert it to CSS automatically (if the _Haml_ gem is installed).]
+  tip[
 By default, stylesheets are embedded within text files. If necessary, you can choose to link them or import them by changing the values of the $>[document.styles].
-	]
-	section[
-		@title[Default Stylesheets]
-		@id[default_stylesheets]
-		p[Glyph provides the following default stylesheets, that can be referenced directly using the %>[style]:]
-		table[
-			tr[
-				th[File name]
-				th[Notes]
-			]
-			tr[
-				td[code[default.css]]
-				td[The stylesheet used for this book.]
-			]
-			tr[
-				td[code[pagination.css]]
-				td[A CSS3-compliant stylesheet used for pagination, suitable for PDF generation using &[prince].]
-			]
-			tr[
-				td[code[coderay.css]]
-				td[The default &[coderay] stylesheet, used for syntax highlighting.]
-			]
-			tr[
-				td[code[ultraviolet/*]]
-				td[This folder contains the following &[uv] stylesheets, used for syntax highlighting: code[%[(Glyph::HOME/"styles/ultraviolet").children.sort.map{\|c\| c.basename}.join(", ")]]]
-			]
-		]
-	]
+  ]
+  section[
+    @title[Default Stylesheets]
+    @id[default_stylesheets]
+    p[Glyph provides the following default stylesheets, that can be referenced directly using the %>[style]:]
+    table[
+      tr[
+        th[File name]
+        th[Notes]
+      ]
+      tr[
+        td[code[default.css]]
+        td[The stylesheet used for this book.]
+      ]
+      tr[
+        td[code[pagination.css]]
+        td[A CSS3-compliant stylesheet used for pagination, suitable for PDF generation using &[prince].]
+      ]
+      tr[
+        td[code[coderay.css]]
+        td[The default &[coderay] stylesheet, used for syntax highlighting.]
+      ]
+      tr[
+        td[code[ultraviolet/*]]
+        td[This folder contains the following &[uv] stylesheets, used for syntax highlighting: code[%[(Glyph::HOME/"styles/ultraviolet").children.sort.map{\|c\| c.basename}.join(", ")]]]
+      ]
+    ]
+  ]

data/book/text/text_editing/topics.glyph

@@ -8,9 +8,9 @@ Glyph does not formally enforce the correctness of topic composition and usage,
 ]
 highlight[=html|
 section[
-	@title[My First Topic]
-	@id[first_topic]
-	@src[test/first_topic.glyph]
+  @title[My First Topic]
+  @id[first_topic]
+  @src[test/first_topic.glyph]
 ]
 =]
 txt[
@@ -18,9 +18,9 @@ This is an ordinary section with a title and an explicit ID, but it has no conte
 ]
 highlight[=html|
 section[
-	@title[My First Topic]
-	@id[first_topic]
-	include[test/first_topic.glyph]
+  @title[My First Topic]
+  @id[first_topic]
+  include[test/first_topic.glyph]
 ]
 =]
 txt[

data/book/text/text_editing/xml_fallback.glyph

@@ -59,7 +59,7 @@ table[@class[features]
 	]
 	p[Basically, if the $>[options.xml_fallback] is set to code[true], any macro unknown to Glyph with at most one parameter will be converted to an XML tag with the same name and any attribute will be converted to the corresponding XML attribute.]
 	important[While macro names and attributes are validated so that an error is returned if they contain illegal character, no check is performed against any particular XML schema.]
-	txt[Additionally, it is possible to force macro-to-XML conversion by prepending an equal sign to any macro, so for example code[=\.=snippet[test]=] will be converted into @<snippet>test</snippet>@.]
+	txt[Additionally, it is possible to force macro-to-XML conversion by composing the name of a tag with the %>[xml], so for example code[=\/xml/snippet[test]=] will be converted into @<snippet>test</snippet>@.]
 	section[
 		@title[Blacklisted XML tags]
 		@id[xml_blacklist]

data/book/text/troubleshooting/errors_command.glyph

@@ -1,5 +1,5 @@
 	error_table[
-		ref_error[Source file '\.em[source_file]' does not exist|
+		ref_error[Source file '\/em[source_file]' does not exist|
 Returned if Glyph is running in =>[#lite_mode|lite mode] and the specified source file was not found.
 		]
 		ref_error[Source and destination file are the same|
@@ -17,7 +17,7 @@ No file name was specified for the #>[add].
 		ref_error[Output target not specified|
 Returned if no target was specified for the #>[compile] _and_ if the $>[document.output] is not set.
 		]
-		ref_error[Unknown output target '\.em[target_name]'|
+		ref_error[Unknown output target '\/em[target_name]'|
 An unsupported output target was specified for the #>[compile]. Only the following output targets are supported:
 			ul[
 				li[html]
@@ -27,10 +27,10 @@ An unsupported output target was specified for the #>[compile]. Only the followi
 		ref_error[Too few/too many arguments|
 Returned if the #>[config] was used with no arguments or more than two arguments respectively.
 		]
-		ref_error[Unknown setting '\.em[setting_name]'|
+		ref_error[Unknown setting '\/em[setting_name]'|
 The name of an unknown setting was specified for the #>[config].
 		]
-		ref_error[Cannot reset '\.em[setting_name]' setting (system use only).|
+		ref_error[Cannot reset '\/em[setting_name]' setting (system use only).|
 Returned by the #>[config] when attempting to override a setting in the code[system.*] namespace.
 		]
 	]

data/book/text/troubleshooting/errors_generic.glyph

@@ -1,9 +1,12 @@
 	error_table[
-		ref_error[Invalid alias: macro '\.em[macro_name]' already exists|
+		ref_error[Invalid alias: macro '\/em[macro_name]' already exists|
 The alias name supplied to the code[macro_alias] method has already been used for another macro or alias.
 		]
-		ref_error[Undefined macro '\.em[macro_name]'|
+		ref_error[Undefined macro '\/em[macro_name]'|
 The document contains a macro that does not exist, i.e. it is not a standard or used-defined =>[#macro_ref|Glyph macro or alias].
+		]
+		ref_error[No macro representation for '\/em[macro_name]'|
+There is no valid macro representation for the specified macro.
 		]
 		ref_error[An error occurred when generating _file-name_.pdf|
 Returned if Prince could not generate the PDF file or if Prince is not installed. Normally, Prince provides additional details on the specific error(s).
@@ -11,34 +14,37 @@ Returned if Prince could not generate the PDF file or if Prince is not installed
 		ref_error[Glyph cannot generate PDF. Please specify a valid output.pdf.generator setting|
 Returned if the $>[output.pdf.generator] has not be set to a valid PDF renderer. Currently, the only supported values for this setting are code[prince] and code[wkhtmltopdf].
 		]
+    ref_error[Glyph cannot generate e-book. At present, output.\/em[ebook_format].generator can only be set to 'calibre'.|
+Returned if the output.\/em[ebook_format].generator setting has not be set to @calibre@.
+    ]
 		ref_error[The current directory is not a valid Glyph project|
 Returned if a glyph command was executed outside a valid glyph project directory.
 		]
 		ref_error[Invalid snippet file|
 The code[snippet.yml] file contains invalid data. Most likely, it does not evaluate to a Ruby code[Hash].
 		]
-		ref_error[Directory '\.em[directory_name]' is not empty|
+		ref_error[Directory '\/em[directory_name]' is not empty|
 	Returned when executing the #>[init] in a directory that is not empty.
 		]
-		ref_error[File '\.em[file_name]' already exists|
+		ref_error[File '\/em[file_name]' already exists|
 Returned if the name of an existing file was specified as a parameter for the #>[add].
 		]
-		ref_error[Unknown macro '\.em[macro_name]'|
+		ref_error[Unknown macro '\/em[macro_name]'|
 Returned by the #>[stats] if the specified macro was not found.
 		]
-		ref_error[Macro '\.em[macro_name]' is not used in this document|
+		ref_error[Macro '\/em[macro_name]' is not used in this document|
 Returned by the #>[stats] if the specified macro is defined but unused.
 		]
-		ref_error[Bookmark '\.em[bookmark_name]' does not exist|
+		ref_error[Bookmark '\/em[bookmark_name]' does not exist|
 Returned by the #>[stats] if the specified bookmark does not exist.
 		]
-		ref_error[No link matching /\.em[regexp]/ was found|
+		ref_error[No link matching /\/em[regexp]/ was found|
 Returned by the #>[stats] if the no link target matches the supplied regular expression.
 		]
-		ref_error[Unknown snippet '\.em[snippet_name]'|
+		ref_error[Unknown snippet '\/em[snippet_name]'|
 Returned by the #>[stats] if the specified snippet was not found.
 		]
-		ref_error[Snippet '\.em[snippet_name]' is not used in this document|
+		ref_error[Snippet '\/em[snippet_name]' is not used in this document|
 Returned by the #>[stats] if the specified snippet is defined but unused.
 		]
 	]

data/book/text/troubleshooting/errors_macro.glyph

@@ -14,25 +14,25 @@ Where:
 * em[macro_value] is the value of the macro (shown only if Glyph is running in =>[#debug_switch|debug mode]).
 	]
 	error_table[
-		ref_error[Macro '\.em[name]' takes up to em[x] parameter(s) (\.em[y] given)|
+		ref_error[Macro '\/em[name]' takes up to em[x] parameter(s) (\/em[y] given)|
 Returned if the macro was called with extra parameters.
 		]
-		ref_error[Macro '\.em[name]' takes at least em[x] parameter(s) (\.em[y] given)|
+		ref_error[Macro '\/em[name]' takes at least em[x] parameter(s) (\/em[y] given)|
 Returned if the macro was called with fewer parameters than expected.
 		]
-		ref_error[Macro '\.em[name]' takes exactly em[x] parameter(s) (\.em[y] given)|
+		ref_error[Macro '\/em[name]' takes exactly em[x] parameter(s) (\/em[y] given)|
 Returned if the macro was called with a different number of parameters than.
 		]
 		ref_error[Macro not available when compiling a single file.|
 Returned by the %>[include] if used in =>[#lite_mode|lite mode].
 		]
-		ref_error[Filter macro '\.em[extension]' not available|
+		ref_error[Filter macro '\/em[extension]' not available|
 Returned by a filter macro if $>[options.filters_by_file_extension] is set to @true@, but the extension was not recognized.
 		]
 		ref_error[Invalid regular expression: em[regexp]|
 Returned by the %>[match] if an invalid regular expression was supplied.
 		]
-		ref_error[Macro '\.em[name]' takes no parameters (\.em[x] given)|
+		ref_error[Macro '\/em[name]' takes no parameters (\/em[x] given)|
 Returned if the macro was called with parameters but none are requested.
 		]
 		ref_error[No highlighter installed. Please run: gem install coderay|
@@ -44,16 +44,16 @@ Returned by the %>[highlight] if $>[filters.highlighter] is set to @coderay@ but
 		ref_error[UltraViolet highlighter not installed. Please run: gem install ultraviolet|
 Returned by the %>[highlight] if $>[filters.highlighter] is set to @ultraviolet@ but &[uv] is not installed.
 		]
-		ref_error[Mutual Inclusion in parameter/attribute(\.em[name]): '\.em[value]'|
+		ref_error[Mutual Inclusion in parameter/attribute(\/em[name]): '\/em[value]'|
 Returned if a catch-22 situation occurs with macro inclusion, for example if the value of a snippet includes a reference to the same snippet.
 		]
-		ref_error[Snippet '\.em[snippet_id]' does not exist|
+		ref_error[Snippet '\/em[snippet_id]' does not exist|
 Returned by the %>[snippet] if an invalid snippet ID was supplied.
 		]
-		ref_error[File '\.em[file_name]' not found|
+		ref_error[File '\/em[file_name]' not found|
 Returned by the %>[include] if an invalid file was supplied.
 		]
-		ref_error[Filter macro '\.em[macro_name]' not found|
+		ref_error[Filter macro '\/em[macro_name]' not found|
 Returned by the %>[include] if the $>[options.filters_by_file_extension] is set to @true@ but the file extension of the included file is not recognized as a filter macro.
 		]
 		ref_error[RedCloth gem not installed. Please run: gem install RedCloth|
@@ -65,37 +65,34 @@ Returned by the %>[markdown] if no valid Markdown converter gem is installed. Gl
 		ref_error[Image/Figure not found|
 Retured by the %>[image] or the %>[figure] respectively, if the specified image file could not be found within the code[images/] folder.
 		]
-		ref_error[Bookmark '\.em[bookmark_name]' already exists|
+		ref_error[Bookmark '\/em[bookmark_name]' already exists|
 Returned by the %>[anchor] or by the %>[section] if the anchor ID supplied as attribute has already been used in the document.
 		]
-		ref_error[Bookmark '\.em[bookmark_name]' already exists|
+		ref_error[Bookmark '\/em[bookmark_name]' already exists|
 Returned by the %>[link] if the anchor ID supplied as parameter has not been used in the document.
 		]
-		ref_error[Stylesheet '\.em[file_name]' not found|
+		ref_error[Stylesheet '\/em[file_name]' not found|
 Returned by the %>[style] if the code[.css] or code[.sass] file supplied as parameter was not found in the code[styles/] directory.
 		]
 		ref_error[Haml is not installed. Please run: gem install haml|
 Returned by the %>[style] if a code[.sass] file was passed as parameter but the Haml gem is not installed.
 		]
-		ref_error[Invalid XML element: '\.em[element_name]'|
+		ref_error[Invalid XML element: '\/em[element_name]'|
 An invalid XML element name was supplied to the code[\|xml\|] system macro (see =>[#other_elements]).
 		]
-		ref_error[Invalid XML element: '\.em[element_name]'|
+		ref_error[Invalid XML element: '\/em[element_name]'|
 An invalid XML attribute name was supplied to the code[\|xml\|] system macro (see =>[#other_elements]).
 		]
-		ref_error[Macro '\.em[macro_name]' cannot be used in safe mode|
+		ref_error[Macro '\/em[macro_name]' cannot be used in safe mode|
 Returned if a forbidden macro was used in safe mode (see =>[#modes]).
 		]
-		ref_error[Cannot reset 'system.\.em[setting_name]' setting (system use only).|
+		ref_error[Cannot reset 'system.\/em[setting_name]' setting (system use only).|
 Returned by the =>[#m_config_] when attempting to override a setting in the code[system.*] namespace.
 		]
-		ref_error[Macro '\.em[macro_name]' cannot be defined by itself|
-Returned by the =>[#m_rewrite_] if it contains a macro with the same name.
-		]
-		ref_error[Macro '\.em[macro_a]' must be within a '\.em[macro_b]' macro|
+		ref_error[Macro '\/em[macro_a]' must be within a '\/em[macro_b]' macro|
 Returned if a macro was used in the wrong place.
 		] 
-		ref_error[Macro '\.em[macro_a]' must not be within a '\.em[macro_b]' macro|
+		ref_error[Macro '\/em[macro_a]' must not be within a '\/em[macro_b]' macro|
 Returned if a macro was used in the wrong place.
 		] 
 	]

data/book/text/troubleshooting/errors_parser.glyph

@@ -1,23 +1,23 @@
 	error_table[
-		ref_error[Macro delimiter '\.em[delimiter]' not escaped|
+		ref_error[Macro delimiter '\/em[delimiter]' not escaped|
 Returned in case of unescaped code[\[]or code[\]].
 		]
 		ref_error[em[macro_name]\[...\] - A macro cannot start with '@' or a digit.|
 Returned if an invalid macro name was specified.
 		]
-		ref_error[Macro '\.em[macro_name]' not closed|
-Returned if a macro lacks its end delimiter code[\.=\]].
+		ref_error[Macro '\/em[macro_name]' not closed|
+Returned if a macro lacks its end delimiter code[\/=\]].
 		]
-		ref_error[Escaping macro '\.em[macro_name]' not closed|
-Returned if an escaping macro lacks its end delimiter code[\.=\]].
+		ref_error[Escaping macro '\/em[macro_name]' not closed|
+Returned if an escaping macro lacks its end delimiter code[\/=\]].
 		]
-		ref_error[Attribute @\.em[attribute_name] not closed|
+		ref_error[Attribute @\/em[attribute_name] not closed|
 Returned if a macro attribute lacks its end delimiter code[\]].
 		]
 		ref_error[Attributes cannot be nested|
 Returned if a macro attribute was found immediately within another attribute.
 		]
-		ref_error[Cannot nest escaping macro '\.em[macro_name_1]' within escaping macro '\.em[macro_name_2]'|
+		ref_error[Cannot nest escaping macro '\/em[macro_name_1]' within escaping macro '\/em[macro_name_2]'|
 Returned if an escaping macro contains another escaping macro.
 		]
 		ref_error[Parameter delimiter '\|' not allowed here|