User Tools
faq
Differences
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:22] sszenti [Error: Lonely … --perhaps a missing list environment.] |
faq [2019/11/12 10:25] (current) sszenti [Biber fails on OS X] |
||
|---|---|---|---|
| Line 40: | Line 40: | ||
| ==== 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|}} | ||
| Line 56: | Line 56: | ||
| ==== 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. | ||
| Line 73: | 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). | ||
faq.1533558168.txt.gz · Last modified: 2018/08/06 14:22 by sszenti
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution 4.0 International
