Bug Tracker

ID:125 🔗
Status:Closed (Not a Bug)
Category:datatool
Version:v2.27
Submitted by:ThreePhaseEel
Date:2017-10-07 18:00:41
Summary:datatool + utf8 special chars in raw CSV import = sounds of breaking LaTeX

Report

MWE (test.tex, MUST HAVE TEST.CSV TO WORK):
\documentclass{article}
\usepackage[utf8]{inputenc}
\usepackage{datatool}
\begin{document}
\tableofcontents
\appendix
\section{Bill of Materials}

\DTLloadrawdb{bom}{test.csv}
\DTLdisplaydb{bom}
\end{document}
MWE (test.csv) (was UTF-8 encoded until the mojibake happened, can send separately if needed, LMK if you want a separate report about your bug report form):
"name","quantity"
"10μF 16V",5
"470Ω 1/2W",10
"33k×9",1
Salient error:
! Undefined control sequence.
\GenericError  ...                                
                                                    #4  \errhelp \@err@     ...
l.9 \DTLloadrawdb{bom}{test.csv}
Full logs:
[...]
(See [How do I get datatool to play nicely with utf8 inputenc and non-ASCII in the incoming CSV?] for more details and a non-mojibake'd test.csv btw)

MWE

\documentclass{article}
\usepackage[utf8]{inputenc}
\usepackage{datatool}
\begin{document}
\tableofcontents
\appendix
\section{Bill of Materials}

\DTLloadrawdb{bom}{test.csv}
\DTLdisplaydb{bom}
\end{document}

Evaluation

(I removed the log from your message as it's too noisy. The bug report script has saved the accompanying log file.) It's not a bug as you also get an error with just:
\documentclass{article}
\usepackage[utf8]{inputenc}
\begin{document}
10μF 16V, 5
470Ω 1/2W, 10
33k×9, 1
\end{document}
and your MWE works fine with recognised UTF-8 characters. For example, if test.csv is changed to:
"name","quantity"
"éîà",1
You need to map the unrecognised UTF-8 characters (as in Alan Munn's answer) or use a UTF-8 aware engine.

Add comment or return to search results.

Watch This Report

If you would like to be notified whenever updates are made to this report, please fill in your email address in the box below and click on "Notify Me of Changes" button. (Please ensure the address is valid.) Your details won't be passed on to third parties in line with this site's Privacy Policy.

If you supply your name, it will be used in the email greeting, which provides a more personal message, otherwise you'll just get a generic greeting. If you have previously supplied your name when signing up for notifications, you don't need to resupply it unless you want to change it.

If you have previously subscribed to notifications for this report, you can unsubscribe by clicking on the "Stop Notification" button.

The "Confirm Bug ID" field helps to protect against spambots. Please enter the bug ID (which you can find at the top of this page).

(Optional.)
E mail:
Confirm E mail:
Confirm Bug ID:

To unsubscribe from all notifications use the notifications page.

Comment

You can append a comment to the report using the form below. Comments are checked first before being added. Any spam or offensive content will be removed first according to this site's Terms of Website Use. Please bear in mind that I develop and maintain free software in my spare time. If you want commerical level support then you can hire a TeX consultant.

The "Confirm Bug ID" field helps to protect against spambots. Please enter the bug ID (which you can find at the top of this page).

(Optional. If provided, it will be shown with the comment.)
Confirm Bug ID:

You can use the following markup:

[pre]Displayed verbatim[/pre]
[tt]monospace text[/tt]
[em]emphasized text[/em]
[b]bold text[/b]
[url]web address[/url]

Ordered list:
[ol]
[li]first item[/li]
[li]second item[/li]
[/ol]

Unordered list:
[ul]
[li]first item[/li]
[li]second item[/li]
[/ul]

Click on the Preview button to preview the message.

Return to search results.