>> if we can get rid of dvipost, why not do it? > > You never know. We don't have time for extensive testing, and maybe soul.sty > does not work in all cases. > For instance, it obviously has problems with > utf8 (however, I'm not sure whether this applies to underlining and > striking out as well, or only to letterspacing).
there is another beta though, so i'd still stick with 1 (pas d'omelette sans casser d'oeufs) however, the most obvious orthodox alternative is 3: use soul but keep dvipost as a backup option (since we intend to abandon dvipost anyway right?)
