+ Forrest is still quite young, so there are known issues. + Standards compliance is a definite major goal. Please send patches + for the Forrest skin stylesheets to ensure such compliance. +

=20 + + =20 + +

HTML

+ Tested using the W3C HTML Validation Service + (validator.w3.org). The + index.html page of Forrest sites will have a link to this validato= r, + unless the user has turned this off. +

+ The "crust" skin (current forrest-= 0=2E6-dev) + validates as HTML 4.0.1 +

+ The "tigris" skin (current forrest= -0.6-dev) + validates as HTML 4.0.1 +

=20 + + =20 + +

WAI

See +Web Accessibility Initiative (WAI) + +

+ There are actually many accessibility issues with the heavy use of + tables and images. These skins are gradually being improved. +

+Bobby with WAI: +bobby.watchfire.com + +

Issues ...

+ Priority 1: alt text for images. +
Priority 2:=20 + Explic= itly + associate form controls and their labels with the LABEL element. + Perhaps we could have a label hidden with CSS?
FIXME: need to list other issues here, or attend to them.

Note

The forrest-site skin does not have any missing alt= s=2E Perhaps Bobby + does not like the trick with empty alt attributes. However, it only + complains about the two in the footer, and not about the other 40.

+Bobby with U.S. Section 508 Guidelines: +bobby.watchfire.com + +

Issues ...

The same issues as above

=20 + + =20 + +

CSS

+Jigsaw: +jigsaw.w3.org + +

Issues ...

CSS 2: No errors. Some warnings.
CSS 1: Errors: hover class, @media-print. Some warnings.
FIXME: need to list other issues here, or attend to them.

=20 + =20 +

+ +

+Core | ForrestBot | ForrestBar +

+ + +

+ +

+ =20 + +

+ + +

Documentation

+Overview +

+FAQs +

+Changes +

+Todo +

+Using Forrest +

+XML Validation +

+Menus and Linking +

+Searching +

+Default Skins +

+Skin Packages +

+Plugins +

+Views-dev +

+Our Contract +

+Standards Compliance +

Advanced Topics

+Building Forrest +

+Using DTD Catalogs +

+Sitemap Reference +

+Project sitemap +

+Plugin In= frastructure +

+Sourcetype Action +

Other versions

+Overview +

+0.8-dev +

+0.7 (current) +

+0.6 +

Upgrading

+Upgrading to 0.7 +

+Upgrading to 0.6 +

SubProjects

+ForrestBar +

+Forrestbot +

+Forrestbot We= bapp +

Reference docs

DTD documentation

+Overview +

+document-v20 +

+howto-v20 +

+faq-v20 +

+document-v13 +

+howto-v13 +

+faq-v13 +

Doc samples

+document-v13 +

+document-v20 +

Older Docs

+Forrest Primer +

+Libre +

+Dream list +

+ This is documentation for current release v0.7 + (More ...)

+ +

+ + +

+ PDF +

+ Font size:=20 + = =20 + + +

The document-v1.2 DTD

A nonsense document using all possible elements in= the current + document-v12.dtd.

+ This is documentation for current release v0.7 + (More ...)

+Changes since document-v11 +
+Sample Content +
- +Using sections +
- +Sections, the sequel +
  - +Section 2.1 +
  +
- +Showing preformatted source = code +
- +Using tables +
- +Using figures +
+

=20 + =20 +

Note

The document-v12 has been superceded by + document-v13 + =20 +

=20 + =20 + +

Changes since document-v11

+ doc-v12 enhances doc-v11 by relaxing various restrictions that were + found to be unnecessary. +

+ Links (link,jump,fork) and inline elements (br,img,icon,acronym)= are + allowed inside title. +
+ Paragraphs (p,source,note,warning,fixme), table and figure,ancho= r are + allowed inside li. +
+ Paragraphs (p,source,note,warning,fixme), lists (ol,ul,dl), tabl= e, + figure,anchor are allowed inside definition lists (dd) and table= s (td + and dh). +
+ Inline content + (strong,em,code,sub,sup,br,img,icon,acronym,link,jump,fork) is + allowed in strong and em. +

+ =20 + +

Sample Content

+Hint: See the xml source to see how the various + elements are used and see the + + DTD documentation. +

This is a simple paragraph. Most documents contain a fair amount of + paragraphs. Paragraphs are called <p&g= t;.

With the <p xml:space=3D"pr= eserve"> attribute, you can declare + that whitespace should be preserved, without implying it is i= n any other + way special.

A number of in-line elements are available in the DTD, we will show them + inside an unordered list (<ul>):

Here is a simple list item (<li>= )=2E
Have you seen the use of the <code> element in the + previous item?
Also, we have <sub> and <sup> + elements to show content ^above or _below th= e text + baseline.
There is a facility to emphasize certain words using the + <em> <strong> + elements.
We can use + + <icon>s, too.
Another possibility is the <img>= element: + , + which offers the ability to refer to an image map.
We have elements for hyperlinking:=20 +
=20 + =20 +
+<link href=3D"your-project.html"> +
=20 + =20 +
Use this to + link + to another document. As per normal, this will open the new d= ocument + in the same browser window.
=20 + + =20 +
+<link href=3D"#section"> +
=20 + =20 +
Use this to + link + to the named anchor in the current document. +
=20 + + =20 +
+<link href=3D"your-project.html#images"> +
=20 + =20 +
Use this to + link + to another document and go to the named anchor. This will op= en + the new document in the same browser window. +
=20 + + =20 +
+<jump href=3D"your-project.html"> +
=20 + =20 +
Use this to + jump + to another document and optionally go to a named + anchor<= /a> + within that document. This will open the new document in the= same + browser window. So what is the difference between link and j= ump? + The jump behaves differently, in that it will replace any fr= ames + in the current window. + This is the equivalent of + <a ... target=3D"_top"> + =20 +
+ + =20 +
+<fork href=3D"your-project.html"> +
=20 + =20 +
Use this to + fork + your webbrowser to another document. This will open the docu= ment + in a new, unnamed browser window. + This is the equivalent of + <a ... target=3D"_blank"> + =20 +
=20 + =20 +
+
Oh, by the way, a definition list
<dl><= /span> was used inside + the previous list item. We could put another=20 +
- unordered list
- inside the list item
+ =20 + + =20 + + =20 + + + + =20 +
A sample nested table
Or even tables inside lists
+ =20 +

A sample nested table
Or even tables	inside lists

So far for the in-line elements, let's look at some paragraph-level + elements.

Fixme (SN)

The <fixme> e= lement is used for stuff + which still needs work. Mind the author attribute!

Note

Use the <note> element to draw attention to something, e.g. ...The <code> element is used when the author can't + express himself clearly using normal sentences ;-)

Warning

Sleep deprivation can be the result of being involv= ed in an open + source project. (a.k.a. the <warning&g= t; element).

Important

If you want your own labels for notes and warnings,= specify them + using the label attribute.

Apart from unordered lists, we have ordered lists too, of course.

Item 1
Item 2
This should be 3 if my math is still OK.

+= +

Using sections

You can use sections to put some structure in your document. For some + strange historical reason, the section title is an attribute of = the + <section> element.

+ +

Sections, the sequel

Just some second section.

+ +

Section 2.1

Which contains a subsection (2.1).

+ +

Showing preformatted source code

Enough about these sections. Let's have a look at more interesting + elements, <source> for ins= tance:

// This example is from the book _Java in a Nutshell_ =
by David Flanagan.
+          // Written by David Flanagan.  Copyright (c) 1996 O'Reilly &=
 Associates.
+          // You may study, use, modify, and distribute this example for a=
ny purpose.
+          // This example is provided WITHOUT WARRANTY either expressed or=
 implied.
+
+          import java.applet.*;    // Don't forget these import statements!
+          import java.awt.*;
+
+          public class FirstApplet extends Applet {
+          // This method displays the applet.
+          // The Graphics class is how you do all drawing in Java.
+          public void paint(Graphics g) {
+          g.drawString("Hello World", 25, 50);
+          }
+          }

Please take care to still use a sensible line-length within your + source elements.

+ +

Using tables

And now for a table:

+=20 + =20 +=20 + =20 +=20 + =20 +=20 + =20 + =20 +=20 + =20 +=20 + =20 +=20 + =20 + =20 +=20 + =20 + + =20 + + + =20 + + =20 +

Table caption
heading cell	heading cell
data cell	data cell
+ Tables can be nested +	+ =20 + + and can include most other elements, like lists + + =20 +

Not much of attributes with <table>, if you ask me.

+ +

Using figures

And a <figure> to end all of this. + Note that this can also be implemented with an + <img> element. +

+ =20 +

+ +