|Summary:||define contract for images and assets in backend store, move to XHTML2 strict.|
|Component:||Miscellaneous||Assignee:||Lenya Developers <dev>|
Description J 2007-04-25 01:48:26 UTC
we need a clearly defined contract as to what is stored in the repository and how. for instance, what is the generic format of images? do we store dimensions (yes we do, but how exactly?) do we store alignment information? currently, it is not easily possible to generate XHTML1.0 strict *and* use image resizing, because height/width/align attributes are not allowed... with a clearly defined backend format, we can easily prepare the data for each editor so that those features work, convert them back to clean XHTML and produce correct XHTML strict output. in addition, we really should move to XHTML2 for storage. it greatly simplifies re-using content snippets out of context, because the stupid <hN/> tags are now embedded in <section/>s which can be arbitrarily nested. plus i think that a really picky backend format is a good exercise :) XHTML2 can be trivially transformed into XHTML1.0, or, if you must, into HTML 3.0 :)
Comment 1 J 2007-11-01 13:54:49 UTC
with the introduction of uuid-based links, we're already in quite good shape. the svn image resizing could use some normative documentation, but other than that we're fine, so i'm downgrading this one...