On Tue, 20 Jan 2004, Jewett, Jim J wrote:
> (1) A plucker document contains many records, and
> each record is an entire "page". The distinction between
> individual paragraphs is not visible to the palm itself.
The individual paragraphs are enumerated in each record.
> (2) Right now, an anchor (or bookmark?) points to
> a page and a paragraph. The viewer tracks paragraph
> boundaries as it reads the text (and intercepts "characters"
> that are really meant to change formatting, like underline).
>
> You would prefer to point to a page and character offset,
> and not have to worry about paragraph counting.
I don't mind the paragraph counting. It's just that I would like an
anchor to be able to jump to the middle of a paragraph if this is what the
original html meant it to do.
> (3)
> The paragraph counter is already large enough to
> point to individual characters (or else we would need
> to break the page).
The viewer already has the machinery to scroll a record to a desired
character offset.
> Somewhere (version number? new record type?) there
> will be an indication of which type of offset is used.
New link type.
> Can the link types be mixed in one document?
As far as the viewer is concerned.
> Would it be any more backwards compatible to
> keep the paragraph offset correct and add an
> extra field for character offset to the url records?
There is no room for this, I think.
> If so, is there any (dis)advantage to making this
> offset from the start-of-paragraph instead of from
> the start-of-page? This seems less fragile to me,
> but it might be more complicated for the
> viewer.
The viewer already has the facilities for moving to a given character
offset. It uses these to seek to a bookmark position after a font change,
or to keep position across font changes.
> (4) What counts in determining the character
> offset? Are all characters 1? Even multi-byte
> characters? Does the font matter? Does white
> space collapse? Does formatting information
> (like "start bold") count? Is this the uncompressed
> character count, rather than the bytes-as-stored?
It's an uncompressed byte offset actually.
> (5) Will you need information on the size of the
> anchor, to underline it or anything? Should the
> parser request any special decoration for anchor
> targets?
One can just do whatever it does for other anchors.
Alex
--
Dr. Alexander R. Pruss || e-mail: [EMAIL PROTECTED]
Philosophy Department || online papers and home page:
Georgetown University || www.georgetown.edu/faculty/ap85
Washington, DC 20057 ||
U.S.A. ||
-----------------------------------------------------------------------------
"Philosophiam discimus non ut tantum sciamus, sed ut boni efficiamur."
- Paul of Worczyn (1424)
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
