Subject: Re: Questions about our XML grammar
From: Randy Kramer (rhkramer@fast.net)
Date: Tue Jan 09 2001 - 09:39:08 CST
Leonard,
Sounds good to this lurker (who just wanted to get his $.02 in). I
especially would like the capability to vary page sizes and margins
within a document, in other words make them section attributes.
One use would be to include portrait and landscape oriented pages (but
maybe that's already covered).
The other use would be to include oversize pages where appropriate (like
legal or 11x17, which would probably be folded to match the 8 1/2 x 11
(I'm an american, but the same thing is applicable for European
sizes)). I'm not sure how I'd print the different size pages, but it
would be convenient to have them stored within one file, at least while
editing.
Just for completeness, some more comments below:
Randy Kramer
Leonard Rosenthol wrote:
>
> I'm working on a new project that involves reading AbiWord files, and
> in looking over some output from Abi (so that I could then write the
> code to process it), I noticed a few things that I'd like to suggest
> be changed and I might even submit the patch to do it if no one
> objects.
>
> * No tags/attributes for page sizes and/or margins. I would suggest
> that these are probably either abiword or section attributes.
I vote for section attributes, or maybe both if there is a good reason.
>
> * Is there a reason we call it "props" rather than "style"? Yes, it
> is our properties, but it's also similar to CSS style values.
I vote for styles. (It is a common term. I forget what KLyX and LyX
use, but it is not a common term.)
>
> * The "line-height" property for <p> is tracked as a multiple of
> something I'm guessing the default line height), rather than the more
> common fixed value for "leading".
I don't think I know enough to comment. I certainly want to keep the
option to single, double, triple, or 1 1/2 space within a paragraph, and
be able to specify separately a "space before" and a "space after" a
paragraph (style).
>
> * The "color" property for <c> should have a leading # in front of
> the size hex values to delineate it as a hex value (as per CSS spec).
> That way we could also support other types of color specifications
> such as names ("aqua", "black", etc.) or other color spaces (CMYK,
> gray, etc.).
Sounds good to me.
>
> * Subscript and Superscript are handled with the "text-position"
> property, but that seems pretty limiting since it doesn't provide for
> control over baseline shift percentage. Could we replace that value
> with a float (or int) specifying how much to baseline shift by (and
> it should support both fixed values as well as percentages - eg. 5,
> -5, 50%).
Sounds good to me.
>
> * The columns property tells one how many columns, but nothing about
> their sizes/margins.
>
Sounds like something missing (to me).
> That's it for now, since I'm on the road with my Wintel laptop and
> the Windows build doesn't have bullet or border dialogs, so I can't
> try to see what they generate. If someone wants to send me some
> sample docs that use though, that would be much appreciated!
>
> Leonard
> --
> ----------------------------------------------------------------------------
> You've got a SmartFriend in Pennsylvania
> ----------------------------------------------------------------------------
> Leonard Rosenthol Internet: leonardr@lazerware.com
> America Online: MACgician
> Web Site: <http://www.lazerware.com/>
> FTP Site: <ftp://ftp.lazerware.com/>
> PGP Fingerprint: C76E 0497 C459 182D 0C6B AB6B CA10 B4DF 8067 5E65
This archive was generated by hypermail 2b25 : Tue Jan 09 2001 - 09:41:13 CST