I'm in the process of migrating a class I wrote from xkeyval
to kvoptions
, mainly because I'd like to provide class options whose values could be list of comma separated values:
\documentclass[myoption={val1,val2}]{myclass}
and, for this, xkeyval
needs xkvltxp
which is currently buggy.
I'd like to know if there is any tutorial that explains how perform this migration, especially how to deal with xkeyval
's \define@choicekey
macro. Another questions are about:
+
extension ofxkeyval
's macros that allow to deal with unexpected values passed by the user,\ExecuteOptionsX
and\ProcessOptionsX
equivalents.
xkeyval
does 'general' key-value input whereaskvoptions
is rather more focussed on a smaller number of common entry types. The net result is that replacingxkeyval
bykvoptions
will also require hand-coded keys using justkeyval
, and thus an answer here would have to be an entire guide to creating keyval input! – Joseph Wright♦ Mar 8 '15 at 14:46xkeyval
). Meanwhile, I switched tol3keys2e
for new classes (but couldn't find time to switch the concerned class). – Denis Bitouzé Jan 28 '18 at 17:30