Subject: Re: [TS] Fidelity of Palm conversion
From: Jack Nutting (jnutting@baldwin.rat.se)
Date: Wed Apr 12 2000 - 09:27:28 EDT
> > Question: Why not let the Palm version "do HTML"? I don't mean full
> > HTML, but some reasonable (and easily parsable) subset. Use the same
> > subset in the desktop markup so there will be no confusion. An
> > initial implementation (for simplicity's sake) could even have the
> > Palm version ignoring all tags, but leaving them intact.
>
> That would be great, but very difficult to do. The most likely way for
> this to happen is with a plugin which processes the data and passes it off
> to Plucker or a similar program.
(CAVEAT: I have never looked at the TS desktop software, so I have no idea
what kind of HTML markup it supports. this ignorance probably influences
what I'm saying to a large degree)
Unless the desktop HTML markup allows the user to hand-edit raw HTML, it
seems that you should be able to just make sure that all the HTML created is
of a "strict" variety (i.e. not "sloppy" HTML like what is currently allowed
by the predominant browsers), with a subset of useful tags. For instance,
limit the used tags to just headers, bold, italic, links, lists, maybe
tables, etc. None of that should be terribly hard to parse on the Palm side
of things.
Now that I think about it, this leads us back into another XML discussion:
Why not just use XML for the markup, and forget about HTML markup on the
desktop?
-- Jack Nutting : jnutting@orcsoftware.com Orc Software : www.orcsoftware.com------------------------------------------------------------------------ Easter is easy with eGroups Check Out Our Gift Guide Now http://click.egroups.com/1/3121/4/_/6321/_/955546198/ ------------------------------------------------------------------------
This archive was generated by hypermail 2b25 : Wed Aug 30 2000 - 22:01:01 EDT