The command-line option -eofill sets pls->dev_eofill to true, and most devices (including the old wxwidgets device) honor that flag by using the even-odd fill rule rather than the default nonzero fill rule. Thus, using the command-line option -eofill makes a spectacular difference for example 27 for most devices, but that is not the case for new wxwidgets since that device currently does not honor pls->dev_eofill and thus always uses the nonzero fill rull. That fundamental deficiency (reported here) for the new wxwidgets device needs to be addressed.
This bug has now been fixed with commit b603fd2. That is,
now gives the correct even-odd fill rule results which are spectacularly different (many more spaces in the "fill" pages) than the non-zero fill rule results when the -eofill option is not used. Thanks, Phil, for this fix!