Sorry, but either this "conversation" is spinning out of control, or we are living on different planets. *My* planet is one inhabited by people reading on small machines, including epub and mobi devices. When I make comments about poetry, it is about how people actually reading on those machines, actually experiencing poetry, when read by their very own eyes. When I say something "doesn't work" I mean that what I understand someone on this forum is proposing I or other have tried experimentally, and we find that it shows up as "scrambled eggs" on small epub and mobi devices. Now if all you have ever worked on is 20" monitors attached to desktop machines you may have a hard time understanding this other planet. Again, suggest you actually try what you are proposing on small epub and mobi machines and see what happens. It is not hard to perform such an experiment. Install Amazon's "Kindle Previewer Version 2" http://www.amazon.com/gp/feature.html?ie=UTF8&docId=1000234621 And then feed your HTML page to that Previewer. The Kindle Previewer is a software emulator for a variety of Amazon epub/mobi devices. If you switch Previewer to emulate "Kindle Fire" you will see results similar to what you would see on an epub device. If you switch Previewer to emulate "Kindle" then you will see results similar to what you would see on a Klassic Kindle mobi device. Presumably some people who try this experiment will now blame Amazon when they find that their code doesn't work in practice. Its not Amazon, its your choice of coding. You can try that coding on a variety of other epub devices and again you will find that your code doesn't work. When I say something "works" or "doesn't work" what do I mean? I mean something "works" when a user can read that poetry on their machine and it "looks" like valid poetry formatted as-if one were reading poetry in a paper book about poetry. I say something "doesn't work" if it comes out scrambled so that it doesn't look like valid poetry formatted in a paper book about poetry. I also say something "doesn't work" if some or all of the poem is simply unreadable on the end users machine, or if they have to perform some kind of strange contortions on their machine to get it readable. In turn this all means that a "poetry scheme" needs to understand the issue of line wrapping and specifically how line wrapping applies to poetry. And it needs to understand the issue of fonts and font families (and why they don't work) Again, there are authors who "get" these issues, people who actually write books for small machines and about small machines. See the writings of Elizabeth Castro, Rufus Deuchler, and Joshua Tallent for example.