Re: conversation history
Brian Enigma <enigma-LFZw70usjZxWk0Htik3J/[email protected]> Sat, 3 Apr 2004 10:55:02 -0800
| Newsgroups | gmane.network.fire.devel |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
First off, I apologize if I am bringing up something that was
already discussed. I have only been vaguely following this thread for
the past few weeks. I am not much of an Objective C programmer (at
least, not something with the size and complexity of Fire), so do not
monitor the list so closely and tend to delete messages after briefly
skimming them.
On Apr 3, 2004, at 7:19 AM, Graham Booker wrote:
> The result, I have been working on a format that is an XML document
> and uses HTML 4 for the messages. I hope to have this fully XHTML 1.1
> compatible if I (or anyone else out there) can figure out W3C's nearly
> worthless documentation.
I have generally not had many problems with the W3C documentation
content, but have a few gripes about often not actually being able to
FIND what I am looking for. ::grumble::
> The last step will be to define a DTD so that the extra tags are in an
> XHTML 1.1 module. Does ANYONE OUT THERE know how to do this? The W3C
> documentation may completely describe it programatically, but is
> nearly worthless in telling you how to actually do something with
> it!!!!
You can "extend" the XHTML DTD by using an "!ENTITY" in the Fire
DTD that points to the XHTML DTD. Alternately, you could grab the
XHTML DTD, modify it to include the custom tags, and include it with
Fire or put it online--although this method is generally frowned upon.
Thirdly, you can use separate XML namespaces: one for the XHTML stuff,
another for the custom Fire stuff. (If putting a DTD online, you may
want want to remember to put a version number somewhere in the filename
or directory name so that future changes won't clash with earlier
revisions.)
> Lastly, if it is possible to get the new tags in an XHTML 1.1 module,
> I will likely add "<html
> xmlns...><head><title>sometitle</title></head><body>" before the log
> tag and "</body></html>" at the end in order to make it real XHTML.
This sounds like the best way to do it. If XHTML is the default
namespace, and Fire is a second namespace (possibly with the prefix
"f:" just to keep the file size down), it is effectively a well-formed
HTML file with extra XML defining certain data fields. Log parsers
could ignore the <head> and traverse into the <body> until it found the
<f:log> element. You would have to remember to close not only the
</f:log>, but also the </body></html>, as well. This would be valid
XHTML and still maintain Fire's fields, but I honestly am not sure how
a browser would interpret the multiple namespaces--whether it would
ignore or include tags in Fire's namespace. My guess is that browsers
would do the same thing they do with unknown tags in normal HTML
(non-XHTML) files: just ignore the tag, but keep the containing text.
-Brian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)
iD8DBQFAbwiJ0dKNWt3rpSURAkt6AJ43Mdenm0HREzbGssV5oXMrF5dzrACg6yuF
PhwRJgaD3wfLj0mJf4Gsugc=
=yQdr
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click