Hmm. Like I said, I have a different model now, but putting this in the extra CSS
pre { font-family: serif !important; }
worked for me.
Oooh, and here's a neat trick which, again, may not work for your model, but
pre { white-space: pre-wrap; word-wrap: break-word; }
wrapped a deliberately long line I created.
. . . sorry. Shiny things.
I suggest creating a test HTML document with a short snippet of pre text (& regular text if so inclined, whatever) but nothing else, importing that into Calibre, running a convert on it, and seeing what it looks like on your device. Then you'll know what the device is capable of, and can debug from there--maybe there are funky things in the HTML file that aren't immediately obviously, maybe the 300 requires further hacking to be useful (there are actually a bunch of alternate firmwares that are really neat and easy to use, I installed one to give me a clock in the corner and let me turn pages with 7/8), etc.
Re: help?
pre {
font-family: serif !important;
}
worked for me.
Oooh, and here's a neat trick which, again, may not work for your model, but
pre {
white-space: pre-wrap;
word-wrap: break-word;
}
wrapped a deliberately long line I created.
. . . sorry. Shiny things.
I suggest creating a test HTML document with a short snippet of pre text (& regular text if so inclined, whatever) but nothing else, importing that into Calibre, running a convert on it, and seeing what it looks like on your device. Then you'll know what the device is capable of, and can debug from there--maybe there are funky things in the HTML file that aren't immediately obviously, maybe the 300 requires further hacking to be useful (there are actually a bunch of alternate firmwares that are really neat and easy to use, I installed one to give me a clock in the corner and let me turn pages with 7/8), etc.