This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
faq [2018/08/06 14:16] sszenti |
faq [2019/11/12 10:25] sszenti [Biber fails on OS X] |
||
---|---|---|---|
Line 9: | Line 9: | ||
==== Brackets ==== | ==== Brackets ==== | ||
- | An opening bracket must always be matched with a closing bracket of the same type. The most common error is forgetting to type the closing bracket. | + | An opening bracket must always be matched with a closing bracket of the same type. The most common error is forgetting to type the closing bracket. |
==== Typing error ==== | ==== Typing error ==== | ||
- | Another common error is the typing error. The TeX parser is not able to understand commands that are inaccurately typed: commands such as ''\EOAseection'' will not be accepted as the parser is not able to ignore the second "e." | + | Another common error is the typing error. The TeX parser is not able to understand commands that are inaccurately typed: commands such as ''\EOAseection'' will not be accepted as the parser is not able to ignore the second "e." |
==== Special characters ==== | ==== Special characters ==== | ||
- | Special characters present a further source of errors. So-called reserved characters such as _ \ $ & # { } % cannot simply be typed into the text as they carry a special meaning in TeX. An underscore character, for example, must be directly preceded in the text by a backslash (''MacOS X shortcut alt + shift + 7''). Thus you would type \_ rather than _. The special EOA command ''\EOAtilde'' must be used to write the tilde character (~). | + | Special characters present a further source of errors. So-called reserved characters such as _ \ $ & # { } % cannot simply be typed into the text as they carry a special meaning in TeX. An underscore character, for example, must be directly preceded in the text by a backslash (''MacOS X shortcut alt + shift + 7''). Thus you would type \_ rather than _. The special EOA command ''\EOAtilde'' must be used to write the tilde character (~). |
===== Common error messages ===== | ===== Common error messages ===== | ||
Line 22: | Line 22: | ||
==== Undefined control sequence ==== | ==== Undefined control sequence ==== | ||
- | Here, an unknown command has been detected. This is often due to typing errors, such as ''\EOAsction{title}'' in place of ''\EOAsection{title}''. | + | Here, an unknown command has been detected. This is often due to typing errors, such as ''\EOAsction{title}'' in place of ''\EOAsection{title}''. |
==== 'Runaway argument?' ==== | ==== 'Runaway argument?' ==== | ||
- | This error is due to the omission of a closing bracket: | + | This error is due to the omission of a closing bracket: |
- | ''\EOAsection{title'' | + | \EOAsection{title |
- | . This leads the parser to interpret the whole of the following text as part of this section title. | + | . |
+ | This leads the parser to interpret the whole of the following text as part of this section title. | ||
==== ! Too many }s. ==== | ==== ! Too many }s. ==== | ||
- | This is the opposite of the above error. Here, there are too many closing brackets. It is possible that ''\EOAsection{title}}'' has been entered. | + | This is the opposite of the above error. Here, there are too many closing brackets. It is possible that ''\EOAsection{title}}'' has been entered. |
==== Missing $ inserted ==== | ==== Missing $ inserted ==== | ||
- | Special characters such as _ \ $ & # { } % have not been preceded with the necessary backslash. The entry 300,- $ causes an error, whereas 300,- \$ produces the correct text. | + | Special characters such as _ \ $ & # { } % have not been preceded with the necessary backslash. The entry 300,- $ causes an error, whereas 300,- \$ produces the correct text. |
==== Error: Lonely … --perhaps a missing list environment. ==== | ==== Error: Lonely … --perhaps a missing list environment. ==== | ||
- | The ''\item'' command can only be used within the ''EOAitems'' or ''EOAlist'' environment. If entered in the text without these commands, it will lead to an error. | + | The ''\item'' command can only be used within the ''EOAitems'' or ''EOAlist'' environment. If entered in the text without these commands, it will lead to an error. |
==== File 'Dateiname' not found on input line ==== | ==== File 'Dateiname' not found on input line ==== | ||
- | The file was not found. This could be due to an incorrectly labeled image, folder or a faulty path. For example, ''Image/Picture1.png'' when the folder containing images is actually called Images. (The use of blanks and special characters in file names is not accepted in TeX.) | + | The file was not found. This could be due to an incorrectly labeled image, folder or a faulty path. For example, ''Image/Picture1.png'' when the folder containing images is actually called Images. (The use of blanks and special characters in file names is not accepted in TeX.) |
===== Parsing protocol ===== | ===== Parsing protocol ===== | ||
- | Almost all editors like [[http://www.edition-open-sources.org/support/texshop.html|TeXShop]] give the parser output in a window. The image below shows the protocol of a parsing run in which a grave error has been detected. | + | Almost all editors like [[texshopconfiguration|TeXShop]] give the parser output in a window. The image below shows the protocol of a parsing run in which a grave error has been detected. |
{{:support:faq_linenumber.png|}} | {{:support:faq_linenumber.png|}} | ||
==== Page numbers in square brackets ==== | ==== Page numbers in square brackets ==== | ||
- | The lead text gives information about loading the required TeX packages; the numbers in square brackets show which pages are currently being parsed. The parsing run in the window below shows that the first four pages have been parsed without difficulty. | + | The lead text gives information about loading the required TeX packages; the numbers in square brackets show which pages are currently being parsed. The parsing run in the window below shows that the first four pages have been parsed without difficulty. |
==== Chapters and images ==== | ==== Chapters and images ==== | ||
- | Information such as //Chapter 1// or //<use "inline/A.jpg" >// indicate that a chapter has started or that an illustration has been incorporated. | + | Information such as //Chapter 1// or //<use "inline/A.jpg" >// indicate that a chapter has started or that an illustration has been incorporated. |
==== Line number references ==== | ==== Line number references ==== | ||
- | The parsing run shown in the window was interrupted. The error message is: | + | The parsing run shown in the window was interrupted. The error message is:\\ |
- | //./publication.tex:43: Undefined control sequence | + | //./publication.tex:43: Undefined control sequence\\ |
- | l.43 Lorem ipsum dolor sit amet \EOAfnn | + | l.43 Lorem ipsum dolor sit amet \EOAfnn\\ |
- | {This is a | + | {This is a\\ |
- | ?// | + | ?\\ // |
- | TeX refers to the actual error as //Undefined control sequence//. The reason for this is a simple typing error: the footnote command was given as ''\EOAfnn'' rather than ''\EOAfn''. The superfluous n led to the error. To find such typing errors quickly, the TeX parser refers to the line where the error can be found, l.43 (l = line). The error can be removed by changing ''\EOAfnn'' to ''\EOAfn'' in line 43 in the file publication.tex. | + | TeX refers to the actual error as //Undefined control sequence//. The reason for this is a simple typing error: the footnote command was given as ''\EOAfnn'' rather than ''\EOAfn''. The superfluous n led to the error. To find such typing errors quickly, the TeX parser refers to the line where the error can be found, l.43 (l = line). The error can be removed by changing ''\EOAfnn'' to ''\EOAfn'' in line 43 in the file publication.tex. |
===== Deleting auxiliary files ===== | ===== Deleting auxiliary files ===== | ||
Line 72: | Line 73: | ||
When using OS X, the following error warning may occasionally be given when creating a bibliography with Biber: | When using OS X, the following error warning may occasionally be given when creating a bibliography with Biber: | ||
- | ''FATAL - Error loading data source package 'Biber::Input::file::bibtex': data source /var/folders/0F/0FD2fdygFEGjRYF9eAhna++++TM/-Tmp-/par-user/cache-fe147f467ff57455f519af2e054cbfc46578602e/ /inc/lib/Biber/Input/file/bibtex.dcf not found in . Compilation failed in require at (eval 79) line 2.'' | + | FATAL - Error loading data source package 'Biber::Input::file::bibtex': |
+ | data source /var/folders/0F/0FD2fdygFEGjRYF9eAhna++++TM/-Tmp-/par-user/ | ||
+ | cache-fe147f467ff57455f519af2e054cbfc46578602e//inc/lib/Biber/Input/file/bibtex.dcf | ||
+ | not found in . Compilation failed in require at (eval 79) line 2. | ||
If this happens, save all documents and restart your computer. Technically savvy users can also simply delete the directory at the terminal with the command ''rm -rv $(biber --cache)'' (administrator rights required). | If this happens, save all documents and restart your computer. Technically savvy users can also simply delete the directory at the terminal with the command ''rm -rv $(biber --cache)'' (administrator rights required). | ||
Line 81: | Line 85: | ||
**Separate files**: If there are many instances of uncommon words being incorrectly hyphenated in the text, then you may define the hyphenation in a separate file using the command \hyphenation{word}. To do this, you must create a new file labelled hyphenation.tex and save this in your publication folder. In the main file of your publication, before the line \begin{document} you must include the command \include{hyphenation}. In the hyphenation.tex file you may specify your suggestions for hyphenation, for example, | **Separate files**: If there are many instances of uncommon words being incorrectly hyphenated in the text, then you may define the hyphenation in a separate file using the command \hyphenation{word}. To do this, you must create a new file labelled hyphenation.tex and save this in your publication folder. In the main file of your publication, before the line \begin{document} you must include the command \include{hyphenation}. In the hyphenation.tex file you may specify your suggestions for hyphenation, for example, | ||
- | ''\hyphenation{in-com-pre-hen-si-bil-i-ties} | + | \hyphenation{in-com-pre-hen-si-bil-i-ties} |
- | \hyphenation{su-per-a-bun-dant}'' | + | \hyphenation{su-per-a-bun-dant} |