[...] That would result in diagrams that > > 1) Had a predictable size on the screen (compared to column width). > > 2) Looks good even on high-resolution screens. > > 3) Can be printed without looking bad (printing a 72dpi diagram at > 600 dpi is pretty ugly).
4) Use a lot more bandwidth on low speed connections 5) use a lot more cpu on low power devices like phones. So it shouldn't be the default. > > Is there some technical reason that won't work? If mscgen can do different resolution pngs, no, but with a quick look I can't see how? > > Taking another tack, what's the status of including SVG diagrams in > HTML output? I tried that with another toolchain a few years ago, and > most browsers didn't seem up to the task of rendering such pages. IIUC only IE9 and later support SVG, most other recentish browsers support it ok. Cheers Lex -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/asciidoc?hl=en.
