> > All others -- > > whether defined by Word or by users -- go at top level. > > I would rather see them prefixed by 'custom.' or something > similar. We *may* chose to support other metadata standards in the > future[1], and IMHO it's better if *all* keys are prefixed.
I'm going to prefix our custom keys with "abiword." as a namespace, of sorts. User-defined tags will be prefixed with "custom." > > 1. For those of you who read the above date examples > > carefully, I'm not sure whether our canonical datetime output > > should include the timezone offsets or not. For details, see: > > > > http://www.w3.org/TR/NOTE-datetime > > I would prefer if they did. I'm preferring that they have GMT-XXXX included in there too, or something similar. > > 3. FWIW, I'm not sure it's all that safe to map Word's > > company onto DC's publisher. Word actually has a separate > > publisher keyword in their custom tag. > > Then we shouldn't map it, IMO. MSWord's OLE Summary Streams do not have anything resembling a Publisher tag (at least as standard). I can show you specs and implementations to this effect, and you can probably show me a screenshot that proves your point. I'm leaving things as-is for now until I'm convinced that we should do otherwise. I've just committed the proper prefixing stuff to CVS HEAD. Dom CVS: ---------------------------------------------------------------------- CVS: Enter Log. Lines beginning with `CVS:' are removed automatically CVS: CVS: Committing in . CVS: CVS: Modified Files: CVS: src/text/ptbl/xp/pd_Document.h CVS: ----------------------------------------------------------------------
signature.asc
Description: This is a digitally signed message part
