LATEX-L Archives

Mailing list for the LaTeX3 project

LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 30 Mar 2015 14:11:20 +0200
Reply-To: Mailing list for the LaTeX3 project <[log in to unmask]>
Content-Transfer-Encoding: 7bit
Message-ID: <[log in to unmask]>
Sender: Mailing list for the LaTeX3 project <[log in to unmask]>
From: Ulrike Fischer <[log in to unmask]>
Parts/Attachments: text/plain (38 lines)
The expanding use of key-val syntax in class and package options
means that packages can break due to unknown values. 
I just tumble over this example in a real document:

\documentclass[index=totoc]{scrbook}
\usepackage{acro}
\begin{document}
\end{document}


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! LaTeX error: "kernel/boolean-values-only"
! 
! Key 'index' accepts boolean values only.


It is easy to provoke a similar error with e.g. siunitx:

\documentclass[mode=special]{scrbook}
\usepackage{siunitx}
\begin{document}
 blub
\end{document}


I'm wondering what could/should be done to avoid such situations.
Should package authors avoid package options altogether and use
setup commands? Or can they (how?) parse the keys in the option list
in a way which doesn't gives errors but imply ignores unknown
values? Should the documentclass filter the options? How? 



-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/

ATOM RSS1 RSS2