Does putting the unicode-range first help?

i.e.:

@font-face {
unicode-range: U+26;
font-family: ‘Ampersand’;
src: local(‘Baskerville’), local(‘Palatino’), local(‘Book Antiqua’);
}

Wouldn’t that then (in Firefox’s case) abort the @font-face rule parsing and thus no override the default font-face font the ampersand?

(Sorry I don’t have time to check this idea right now)