then
the default for the table element is RULES=ALL, except if _n=0_
for which RULES=NONE is appropriate.
]PRE]
[PRE[
CELLSPACING
This attribute is intended for backwards compatibility with
deployed user agents. It specifies the space between the table
frame and the first or last cell border for each row or column,
and between other cells in the table. See standard units.
Greater control will be possible using style sheet languages.
]PRE]
[PRE[
CELLPADDING
This attribute is intended for backwards compatibility with
deployed user agents. It specifies the amount of space between
the border of the cell and its contents both above/below, and
]PRE]
Raggett Experimental [Page 15]
[PRE[
RFC 1942 HTML Tables May 1996
]PRE]
[PRE[
left//right. See standard units. Greater control will be
possible using style sheet languages.
]PRE]
[PRE[
If a fixed width is set for the table or column, the CELLSPACING and
CELLPADDING may demand more space than assigned. Current practice is
for the latter to take precedence over WIDTH attributes when a
conflict occurs, although this isn't required by this specification.
]PRE]
Table Captions
[PRE[
]PRE]
[PRE[
]PRE]
[PRE[
]PRE]
[PRE[
The optional CAPTION element is used to provide a caption for the
table. Both start and end tags are required.
]PRE]
[PRE[
ID, CLASS, LANG and DIR
See earlier description of common attributes.
]PRE]
[PRE[
ALIGN
This may be used to control the placement of captions relative
to the table. When present, the ALIGN attribute should have one
of the values: TOP, BOTTOM, LEFT and RIGHT. It is recommended
that the caption is made to fit within the width or height of
the table as appropriate. The default position of the caption is
deliberately unspecified.
]PRE]
[PRE[
Note the ALIGN attribute is overused in HTML, but is retained
here for compatibility with currently deployed browsers.
]PRE]
The COLGROUP Element
[PRE[
]PRE]
[PRE[
]PRE]
[PRE[
The COLGROUP element acts as a container for a group of columns, and
allows you to set default properties for these columns. In the
absence of a COLGROUP element, all columns in the table are assumed
to belong to a single column group. Each COLGROUP element can
contain zero or more COL elements. COLGROUP requires a start tag,
but the end tag may be omitted. This is useful when defining a
sequence of COLGROUP elements, e.g.
]PRE]
[PRE[
]PRE]
[PRE[
COLGROUP elements can be used with the following attributes:
]PRE]
[PRE[
ID, CLASS, LANG and DIR
See earlier description of common attributes.
]PRE]
[PRE[
SPAN
A positive integer value that specifies a default for how many
columns are in this group. This attribute should be ignored if
the COLGROUP element contains one or more COL elements. It
provides a convenient way of grouping columns without the need
to supply COL elements.
]PRE]
[PRE[
WIDTH
Specifies a default width for each of the grouped columns, see
standard units. In addition, the "*" suffix denotes relative
widths, e.g.
]PRE]
[PRE[
width=64 width in screen pixels
width=0.5* a relative width of 0.5
]PRE]
[PRE[
Relative widths act as constraints on the relative widths of
different columns. If a COLGROUP element specifies a relative
width of zero, all of the columns in the group should be set to
their minimum widths, unless they are associated with a COL
element with an overriding WIDTH attribute. When widths are
]PRE]
Raggett Experimental [Page 17]
[PRE[
RFC 1942 HTML Tables May 1996
]PRE]
[PRE[
given in absolute units, the user agent can use these to
constrain the width of the table. The "*" suffix is used to
simplify importing tables from the CALS representation.
]PRE]
[PRE[
ALIGN, CHAR, CHAROFF and VALIGN
Specify values for horizontal and vertical alignment within
table cells. See inheritance order of alignment properties.
]PRE]
The COL Element
[PRE[
]PRE]
[PRE[
]PRE]
[PRE[
This optional element is used to specify column based defaults for
table properties. It is an empty element, and as such has no
content, and shouldn't be given an end tag. Several COL elements may
be given in succession. COL attributes override those of the parent
COLGROUP element.
]PRE]
[PRE[
ID, CLASS, LANG and DIR
See earlier description of common attributes.
]PRE]
[PRE[
SPAN
A positive integer value that specifies how many columns this
element applies to, defaulting to one. In the absence of SPAN
attributes the first COL element applies to the first column,
the second COL element to the second column and so on. If the
second COL element had SPAN=2, it would apply to the second and
third column. The next COL element would then apply to the
fourth column and so on. SPAN=0 has a special significance and
implies that the COL element spans all columns from the current
column up to and including the last column. Note that a COL SPAN
does not define a group. It is merely a way to share attribute
definitions.
]PRE]
Raggett Experimental [Page 18]
[PRE[
RFC 1942 HTML Tables May 1996
]PRE]
[PRE[
WIDTH
Specifies the width of the columns, see standard units. If the
element spans several columns then the WIDTH attribute specifies
the width for each of the individual columns - not the width of
the span. In addition, the "*" suffix denotes relative widths,
]PRE]
[PRE[
e.g.
]PRE]
[PRE[
width=64 width in screen pixels
width=0.5* a relative width of 0.5
]PRE]
[PRE[
Relative widths act as constraints on the relative widths of
different columns. If a COL element specifies a relative width
of zero, the column should always be set to its minimum width.
When widths are given in absolute units, the user agent can use
these to constrain the width of the table. The "*" suffix is
used to simplify importing tables from the CALS representation.
]PRE]
[PRE[
ALIGN, CHAR, CHAROFF and VALIGN
Specify values for horizontal and vertical alignment within
table cells. See inheritance order of alignment properties.
]PRE]
Table Head, Foot and Body Elements
[PRE[
]PRE]
[PRE[
]PRE]
[PRE[
Tables may be divided up into head and body sections. The THEAD and
TFOOT elements are optional, but one or more TBODY elements are
always required. If the table only consists of a TBODY section, the
TBODY start and end tags may be omitted, as the parser can infer
them. If a THEAD element is present, the THEAD start tag is
required, but the end tag can be omitted, provided a TFOOT or TBODY
start tag follows. The same applies to TFOOT.
]PRE]
[PRE[
Note: This definition provides compatibility with tables created
for the older model, as well as allowing the end tags for THEAD,
TFOOT and TBODY to be omitted.
]PRE]
Raggett Experimental [Page 19]
[PRE[
RFC 1942 HTML Tables May 1996
]PRE]
[PRE[
The THEAD, TFOOT and TBODY elements provide a convenient means for
controlling rendering. If the table has a large number of rows in
the body, user agents may choose to use a scrolling region for the
table body sections. When rendering to a paged device, tables will
often have to be broken across page boundaries. The THEAD, TFOOT and
TBODY elements allow the user agent to repeat the table foot at the
bottom of the current page, and then the table head at the top of
the new page before continuing on with the table body.
]PRE]
[PRE[
TFOOT is placed before the TBODY in the markup sequence, so that
browsers can render the foot before receiving all of the table data.
This is useful when very long tables are rendered with scrolling
body sections, or for paged output, involving breaking the table
over many pages.
]PRE]
[PRE[
Each THEAD, TFOOT and TBODY element must contain one or more TR
elements.
]PRE]
[PRE[
ID, CLASS, LANG and DIR
See earlier description of common attributes.
]PRE]
[PRE[
ALIGN, CHAR, CHAROFF and VALIGN
Specify values for horizontal and vertical alignment within
table cells. See inheritance order of alignment properties.
]PRE]
Table Row (TR) elements
[PRE[
]PRE]
[PRE[
]PRE]
[PRE[
The TR or table row element acts as a container for a row of table
cells. The end tag may be omitted.
]PRE]
[PRE[
ID, CLASS, LANG and DIR
See earlier description of common attributes.
]PRE]
[PRE[
ALIGN, CHAR, CHAROFF and VALIGN
Specify values for horizontal and vertical alignment within
table cells. See inheritance order of alignment properties.
]PRE]
Raggett Experimental [Page 20]
[PRE[
RFC 1942 HTML Tables May 1996
]PRE]
Table Cells: TH and TD
[PRE[
]PRE]
[PRE[
]PRE]
[PRE[
TH elements are used to represent header cells, while TD elements
are used to represent data cells. This allows user agents to render
header and data cells distinctly, even in the absence of style
sheets.
]PRE]
[PRE[
Cells can span multiple rows and columns, and may be empty. Cells
spanning rows contribute to the column count on each of the spanned
rows, but only appear in the markup once (in the first row spanned).
The row count is determined by the number of TR elements. Any rows
implied by cells spanning rows beyond this should be ignored.
]PRE]
[PRE[
If the column count for the table is greater than the number of
cells for a given row (after including cells for spanned rows), the
missing cells are treated as occurring on the right hand side of the
table and rendered as empty cells. If the language context indicates
a right to left writing order, then the missing cells should be
placed on the left hand side.
]PRE]
[PRE[
It is possible to create tables with overlapping cells, for
instance:
]PRE]
[PRE[
]PRE]
Raggett Experimental [Page 21]
[PRE[
RFC 1942 HTML Tables May 1996
]PRE]
[PRE[
which might look something like:
]PRE]
[PRE[
/-----------\
| 1 | 2 | 3 |
| |-------|
| | 4 | |
|---|...|---|
| 5 : | 6 |
\-----------/
]PRE]
[PRE[
In this example, the cells labelled 4 and 5 overlap. In such cases,
the rendering is implementation dependent.
]PRE]
[PRE[
The AXIS and AXES attributes for cells provide a means for defining
concise labels for cells. When rendering to speech, these attributes
may be used to provide abbreviated names for the headers relevant to
each cell. Another application is when you want to be able to later
process table contents to enter them into a database. These
attributes are then used to give database field names. The table's
class attribute should be used to let the software recognize which
tables can be treated in this way.
]PRE]
[PRE[
ID, CLASS, LANG and DIR
See earlier description of common attributes.
]PRE]
[PRE[
AXIS
This defines an abbreviated name for a header cell, e.g. which
can be used when rendering to speech. It defaults to the cell's
content.
]PRE]
[PRE[
AXES
This is a comma separated list of axis names which together
identify the row and column headers that pertain to this cell.
It is used for example when rendering to speech to identify the
cell's position in the table. If missing the user agent can try
to follow up columns and left along rows (right for some
languages) to find the corresponding header cells.
]PRE]
[PRE[
NOWRAP, e.g. |
The presence of this attribute disables automatic wrapping of
text lines for this cell. If used uncautiously, it may result in
excessively wide cells. This attribute is defined for backwards
compatibility with deployed user agents. Greater control is
possible with associated style sheet languages (for example for
control over overflow handling).
]PRE]
Raggett Experimental [Page 22]
[PRE[
RFC 1942 HTML Tables May 1996
]PRE]
[PRE[
ROWSPAN, e.g. |
A positive integer value that defines how may rows this cell
spans. The default ROWSPAN is 1. ROWSPAN=0 has a special
significance and implies that the cell spans all rows from the
current row up to the last row of the table.
]PRE]
[PRE[
COLSPAN, e.g. |
A positive integer value that defines how may columns this cell
spans. The default COLSPAN is 1. COLSPAN=0 has a special
significance and implies that the cell spans all columns from
the current column up to the last column of the table.
]PRE]
[PRE[
ALIGN, CHAR, CHAROFF and VALIGN
Specify values for horizontal and vertical alignment within
table cells. See inheritance order of alignment properties.
]PRE]
[PRE[
Note: It is recommended that implementors provide support for the
Netscape 1.1 WIDTH attribute for TH and TD, although this isn't part
of the current specification. Document authors are advised to use
the width attribute for the COL element instead.
]PRE]
Recommended Layout Algorithms
[PRE[
If the COLS attribute on the TABLE element specifies the number of
columns, then the table may be rendered using a fixed layout,
otherwise the autolayout algorithm described below should be used.
]PRE]
Fixed Layout Algorithm
[PRE[
For this algorithm, it is assumed that the number of columns is
known. The column widths by default should be set to the same size.
Authors may override this by specifying relative or absolute column
widths, using the COLGROUP or COL elements. The default table width
is the space between the current left and right margins, but may be
overridden by the WIDTH attribute on the TABLE element, or determined
from absolute column widths. To deal with mixtures of absolute and
relative column widths, the first step is to allocate space from the
table width to columns with absolute widths. After this, the space
remaining is divided up between the columns with relative widths.
]PRE]
[PRE[
The table syntax alone is insufficient to guarantee the consistency
of attribute values. For instance, the number of columns specified by
the COLS attribute may be inconsistent with the number of columns
implied by the COL elements. This in turn, may be inconsistent with
the number of columns implied by the table cells. A further problem
occurs when the columns are too narrow to avoid overflow of cell
contents. The width of the table as specified by the TABLE element or
COL elements may result in overflow of cell contents. It is
]PRE]
Raggett Experimental [Page 23]
[PRE[
RFC 1942 HTML Tables May 1996
]PRE]
[PRE[
recommended that user agents attempt to recover gracefully from these
situations, e.g. by hyphenating words and resorting to splitting
words if hyphenation points are unknown.
]PRE]
[PRE[
In the event that an indivisible element causes cell overflow, the
user agent may consider adjusting column widths and re-rendering the
table. In the worst case clipping may be considered if column width
adjustments and/or scrollable cell content are not feasible. In any
case if cell content is split or clipped this should be indicated to
the user in an appropriate manner.
]PRE]
Autolayout Algorithm
[PRE[
If the COLS attribute is missing from the table start tag, then the
user agent should use the following autolayout algorithm. It uses two
passes through the table data and scales linearly with the size of
the table.
]PRE]
[PRE[
In the first pass, line wrapping is disabled, and the user agent
keeps track of the minimum and maximum width of each cell. The
maximum width is given by the widest line. As line wrap has been
disabled, paragraphs are treated as long lines unless broken by
elements. The minimum width is given by the widest word or image etc.
taking into account leading indents and list bullets etc. In other
words, if you were to format the cell's content in a window of its
own, determine the minimum width you could make the window before the
cell begins to overflow. Allowing user agents to split words will
minimize the need for horizontal scrolling or in the worst case
clipping of cell contents.
]PRE]
[PRE[
This process also applies to any nested tables occuring in cell
content. The minimum and maximum widths for cells in nested tables
are used to determine the minimum and maximum widths for these tables
and hence for the parent table cell itself. The algorithm is linear
with aggregate cell content, and broadly speaking independent of the
depth of nesting.
]PRE]
[PRE[
To cope with character alignment of cell contents, the algorithm
keeps three running min/max totals for each column: Left of align
char, right of align char and un-aligned. The minimum width for a
column is then: max(min_left + min_right, min_non-aligned).
]PRE]
[PRE[
The minimum and maximum cell widths are then used to determine the
corresponding minimum and maximum widths for the columns. These in
turn, are used to find the minimum and maximum width for the table.
Note that cells can contain nested tables, but this doesn't
complicate the code significantly. The next step is to assign column
widths according to the available space (i.e. the space between the
]PRE]
Raggett Experimental [Page 24]
[PRE[
RFC 1942 HTML Tables May 1996
]PRE]
[PRE[
current left and right margins).
]PRE]
[PRE[
For cells which span multiple columns, a simple approach, as used by
Arena, is to evenly apportion the min/max widths to each of the
constituent columns. A slightly more complex approach is to use the
min/max widths of unspanned cells to weight how spanned widths are
apportioned. Experimental study suggests a blend of the two
approaches will give good results for a wide range of tables.
]PRE]
[PRE[
The table borders and intercell margins need to be included in
assigning column widths. There are three cases:
]PRE]
[PRE[
1. The minimum table width is equal to or wider than the available
space. In this case, assign the minimum widths and allow the
user to scroll horizontally. For conversion to braille, it will
be necessary to replace the cells by references to notes
containing their full content. By convention these appear before
the table.
]PRE]
[PRE[
2. The maximum table width fits within the available space. In this
case, set the columns to their maximum widths.
]PRE]
[PRE[
3. The maximum width of the table is greater than the available
space, but the minimum table width is smaller. In this case,
find the difference between the available space and the minimum
table width, lets call it W. Lets also call D the difference
between maximum and minimum width of the table.
]PRE]
[PRE[
For each column, let d be the difference between maximum and
minimum width of that column. Now set the column's width to the
minimum width plus d times W over D. This makes columns with
large differences between minimum and maximum widths wider than
columns with smaller differences.
]PRE]
[PRE[
This assignment step is then repeated for nested tables using the
minimum and maximum widths derived for all such tables in the first
pass. In this case, the width of the parent (i.e. enclosing) table
cell plays the role of the current window size in the above
description. This process is repeated recursively for all nested
tables. The topmost table is then rendered using the assigned widths.
Nested tables are subsequently rendered as part of the parent table's
cell contents.
]PRE]
[PRE[
If the table width is specified with the WIDTH attribute, the user
agent attempts to set column widths to match. The WIDTH attribute is
not binding if this results in columns having less than their minimum
(i.e. indivisible) widths.
]PRE]
Raggett Experimental [Page 25]
[PRE[
RFC 1942 HTML Tables May 1996
]PRE]
[PRE[
If relative widths are specified with the COL element, the algorithm
is modified to increase column widths over the minimum width to meet
the relative width constraints. The COL elements should be taken as
hints only, so columns shouldn't be set to less than their minimum
width. Similarly, columns shouldn't be made so wide that the table
stretches well beyond the extent of the window. If a COL element
specifies a relative width of zero, the column should always be set
to its minimum width.
]PRE]
HTML Table DTD
[PRE[
The DTD or document type definition provides the formal definition of
the allowed syntax for HTML tables.
]PRE]
]PRE]
]PRE]
]PRE]
Raggett Experimental [Page 26]
[PRE[
RFC 1942 HTML Tables May 1996
]PRE]
]PRE]
]PRE]
]PRE]
]PRE]
]PRE]
]PRE]
]PRE]
]PRE]
]PRE]
]PRE]
]PRE]
References
[PRE[
Arena
W3C's HTML3 browser, see http://www.w3.org/pub/WWW/Arena/.
Arena was originally created as a proof of concept demo for
ideas in the HTML+ specification that preceded HTML3. The
browser is now being re-implemented to provide a reference
implementation of HTML3 along with support for style sheets and
client-side scripting.
]PRE]
[PRE[
CALS
Continuous Acquisition and Life-Cycle Support (formerly
Computer-aided Acquisition and Logistics Support) (CALS) is a
Department of Defense (DoD) strategy for achieving effective
creation, exchange, and use of digital data for weapon systems
and equipment. More information can be found from the US Navy
CALS home page at http://navysgml.dt.navy.mil/cals.html
]PRE]
Raggett Experimental [Page 29]
[PRE[
RFC 1942 HTML Tables May 1996
]PRE]
[PRE[
HTML 2.0 (RFC1866)
Hypertext Markup Language Specification Version 2.0 by T.
Berners-Lee and D. Connolly, November 1995. Further information
can be found at http://www.w3.org/pub/WWW/MarkUp/ or at
ftp://ds.internic.net/rfc/rfc1866.txt
]PRE]
[PRE[
HTML 3.0
Hypertext Markup Language Specification Version 3.0. The initial
draft specification as published in March 1995. Work on refining
HTML3 is proceeding piecemeal with the new table specification
as one of the pieces. For W3C related work on HTML, see
http://www.w3.org/pub/WWW/MarkUp/.
]PRE]
[PRE[
RFC 1766
"Tags for the Identification of Languages", by H. Alvestrand,
UNINETT, March 1995. This document can be downloaded from
ftp://ds.internic.net/rfc/rfc1766.txt.
]PRE]
Security Considerations
[PRE[
Security issues are not discussed in this memo.
]PRE]
Author's Address
[PRE[
Dave Raggett W3C
]PRE]
[PRE[
EMail: dsr@w3.org
]PRE]
[PRE[
The World Wide Web Consortium: http://www.w3.org/
*License
[[RFCのライセンス]]
*メモ
]PRE]
[1]
Interesting site http://oooauthors.org/Members/derik/poker.html
([[Chris]] [Alex@mail.com] [WEAK[2006-09-09 11:21:06 +00:00]])
[2]
It very interesting http://www.tchezope.org/Members/de/poker-6.htm
([[Brianna]] [George@mail.com] [WEAK[2006-09-09 17:44:46 +00:00]])
[3]
Very nice site! http://oooauthors.org/Members/pc/poker-11.htm
([[Robert]] [Alexis@hotmail.com] [WEAK[2006-09-10 12:02:42 +00:00]])
[4]
Very nice site! http://oooauthors.org/Members/pc/poker-12.htm
([[Ange]] [Brianna@hotmail.com] [WEAK[2006-09-10 14:53:08 +00:00]])
[5]
It very interesting http://jobs.msdinc.com/Members/de/game-poker.html
([[Joshua]] [Kaylee@mail.com] [WEAK[2006-09-10 23:08:41 +00:00]])
[6]
Great work on website. http://jobs.msdinc.com/Members/de/poker-table.html
([[Elizabeth]] [Samantha@mail.com] [WEAK[2006-09-11 07:55:08 +00:00]])
[7]
Cool design http://jobs.msdinc.com/Members/de/free-poker-site.html
([[Robert]] [Maureen@mail.com] [WEAK[2006-09-11 14:38:49 +00:00]])
[8]
archy it i http://pen.bme.gatech.edu/Members/de/poker-20.htm
([[Robert]] [Leonard@mail.com] [WEAK[2006-09-12 17:09:36 +00:00]])
[9]
VERY GOOD I THINK http://learning.swc.hccs.edu/members/de/poker-21.htm
([[Lori]] [Reginald@mail.com] [WEAK[2006-09-12 19:45:48 +00:00]])
[10]
Great work on website. http://kaon.semanticweb.org/Members/de/poker-22.htm
([[Michael]] [Herman@mail.com] [WEAK[2006-09-12 22:54:49 +00:00]])
[11]
Your hard work paid off http://xoomer.alice.it/a3e/internet-car-insurance/
([[Samantha]] [Christopher@hotmail.com] [WEAK[2006-09-13 05:06:14 +00:00]])
[12]
Thanks for taking http://xoomer.alice.it/a3e/disney-tickets/
([[Frank]] [Hailey@mail.com] [WEAK[2006-09-13 08:19:52 +00:00]])
[13]
Exciting website. http://neumann.sk.tsukuba.ac.jp/plone/Members/de/poker-26.htm
([[Dale]] [Matthew@mail.com] [WEAK[2006-09-13 11:21:55 +00:00]])
[14]
Thank you... http://neumann.sk.tsukuba.ac.jp/plone/Members/de/poker-27.htm
([[Michael]] [Maureen@mail.com] [WEAK[2006-09-13 14:21:48 +00:00]])
[15]
Very nice site! http://neumann.sk.tsukuba.ac.jp/plone/Members/de/poker-28.htm
([[Alexis]] [Kaylee@hotmail.com] [WEAK[2006-09-13 17:21:39 +00:00]])
[16]
Very good site http://neumann.sk.tsukuba.ac.jp/plone/Members/de/poker-29.htm
([[Elizabeth]] [Michael@hotmail.com] [WEAK[2006-09-13 20:06:53 +00:00]])
[17]
this site rocks! http://neumann.sk.tsukuba.ac.jp/plone/Members/de/poker-30.htm
([[Christopher]] [Samantha@hotmail.com] [WEAK[2006-09-13 23:05:17 +00:00]])
[18]
It very interesting http://neumann.sk.tsukuba.ac.jp/plone/Members/de/poker-31.htm
([[Jasmine]] [Leonard@mail.com] [WEAK[2006-09-14 02:01:15 +00:00]])
[19]
Good Luck! http://neumann.sk.tsukuba.ac.jp/plone/Members/de/poker-33.htm
([[Hailey]] [Elizabeth@mail.com] [WEAK[2006-09-14 05:11:52 +00:00]])
[20]
archy it i http://neumann.sk.tsukuba.ac.jp/plone/Members/de/poker-35.htm
([[Daniel]] [Jacob@mail.com] [WEAK[2006-09-14 11:22:35 +00:00]])
[21]
Is very interesting http://neumann.sk.tsukuba.ac.jp/plone/Members/de/poker-36.htm
([[Elizabeth]] [Kaylee@hotmail.com] [WEAK[2006-09-14 13:56:01 +00:00]])
[22]
Very nice site! http://xoomer.alice.it/a3e/foreclosure/
([[Herman]] [Samantha@hotmail.com] [WEAK[2006-09-14 16:53:31 +00:00]])
[23]
Very nice site! http://pen.bme.gatech.edu/Members/koz/1/poker-37.htm
([[Daniel]] [Elizabeth@mail.com] [WEAK[2006-09-14 19:55:09 +00:00]])
[24]
Your hard work paid off http://pen.bme.gatech.edu/Members/koz/1/poker-38.htm
([[Ange]] [Zachary@mail.com] [WEAK[2006-09-14 22:37:33 +00:00]])
[25]
It very interesting http://pen.bme.gatech.edu/Members/koz/1/poker-39.htm
([[Ange]] [Joshua@mail.com] [WEAK[2006-09-15 01:49:16 +00:00]])
[26]
Thanks for taking http://pen.bme.gatech.edu/Members/koz/1/poker-40.htm
([[Anthony]] [Barbara@mail.com] [WEAK[2006-09-15 04:55:31 +00:00]])
[27]
Great work on website. http://pen.bme.gatech.edu/Members/koz/1/poker-41.htm
([[Anthony]] [Alexis@mail.com] [WEAK[2006-09-15 08:27:02 +00:00]])
[28]
thanks for mentioning http://www.ballview.org/Members/pi/poker-42.htm
([[Maureen]] [Michael@hotmail.com] [WEAK[2006-09-15 11:37:50 +00:00]])
[29]
Interesting site http://www.andreaskapsalis.com/includes/2/
([[Reginald]] [Christopher@hotmail.com] [WEAK[2006-09-15 14:22:20 +00:00]])
[30]
Very good site http://bloomhost.net/cache/inc/
([[Larry]] [Hannah@hotmail.com] [WEAK[2006-09-15 20:01:39 +00:00]])
[31]
Thanks for taking http://projects.objectrealms.net/Members/derik/poker-44.htm
([[Paul]] [Elizabeth@hotmail.com] [WEAK[2006-09-16 02:20:06 +00:00]])
[32]
Cool design http://repo.isis.vanderbilt.edu/Members/de/poker-45.htm
([[Joshua]] [Michael@mail.com] [WEAK[2006-09-16 04:55:34 +00:00]])
[33]
this site rocks! http://www.opensourcearmenia.com/Members/brr/1.html
([[Carol]] [Dale@mail.com] [WEAK[2006-09-16 08:09:43 +00:00]])
[34]
Great work on website. http://www.opensourcearmenia.com/Members/brr/2.html
([[Jacob]] [Carol@mail.com] [WEAK[2006-09-16 10:57:47 +00:00]])
[35]
Very nice site http://www.opensourcearmenia.com/Members/brr/3.html
([[Anthony]] [Samantha@mail.com] [WEAK[2006-09-16 13:43:08 +00:00]])
[36]
Very nice site! http://www.opensourcearmenia.com/Members/brr/4.html
([[Richard]] [Michael@hotmail.com] [WEAK[2006-09-16 16:44:08 +00:00]])
[37]
Thank you... http://www.opensourcearmenia.com/Members/brr/5.html
([[Emily]] [Anthony@hotmail.com] [WEAK[2006-09-16 19:38:00 +00:00]])
[38]
Very good website http://www.bloopdiary.com/users/72599/poker-46.htm
([[Christopher]] [Zachary@mail.com] [WEAK[2006-09-16 22:32:24 +00:00]])
[39]
Exciting website. http://www.bloopdiary.com/users/72599/poker-47.htm
([[Alton]] [Elizabeth@mail.com] [WEAK[2006-09-17 01:27:04 +00:00]])
[40]
Very nice site! http://www.bloopdiary.com/users/72599/poker-48.htm
([[Donald]] [Kaylee@hotmail.com] [WEAK[2006-09-17 04:34:29 +00:00]])
[41]
Very good website http://www.opensourcearmenia.com/Members/brr/6.html
([[Samantha]] [Robert@mail.com] [WEAK[2006-09-17 10:37:57 +00:00]])
[42]
archy it i poker game [url=http://xoomer.alice.it/po4/poker-game/]poker game[/url] http://xoomer.alice.it/po4/poker-game/
([[Michael]] [Christopher@hotmail.com] [WEAK[2006-09-17 16:49:28 +00:00]])
[43]
Hi, nice site! freeroll poker tournaments [url=http://xoomer.alice.it/po4/freeroll-poker-tournaments/]freeroll poker tournaments[/url] http://xoomer.alice.it/po4/freeroll-poker-tournaments/
([[Christopher]] [Jacob@mail.com] [WEAK[2006-09-17 19:30:13 +00:00]])
[44]
Thanks for taking internet poker [url=http://xoomer.alice.it/a3e/internet-poker/]internet poker[/url] http://xoomer.alice.it/a3e/internet-poker/
([[Joshua]] [Alton@mail.com] [WEAK[2006-09-17 21:32:00 +00:00]])
[45]
i like you! slot machine [url=http://xoomer.alice.it/a3e/slot-machine/]slot machine[/url] http://xoomer.alice.it/a3e/slot-machine/
([[Carol]] [George@mail.com] [WEAK[2006-09-17 23:46:17 +00:00]])
[46]
Thank you... laser hair removal [url=http://xoomer.alice.it/a3e/laser-hair-removal/]laser hair removal[/url] http://xoomer.alice.it/a3e/laser-hair-removal/
([[Ada]] [Jacob@hotmail.com] [WEAK[2006-09-18 01:41:19 +00:00]])
[47]
this site rocks! poker 26 [url=http://neumann.sk.tsukuba.ac.jp/plone/Members/de/poker-26.htm]poker 26[/url] http://neumann.sk.tsukuba.ac.jp/plone/Members/de/poker-26.htm
([[Jacob]] [Anthony@hotmail.com] [WEAK[2006-09-18 03:51:11 +00:00]])
[48]
thanks for mentioning poker 28 [url=http://neumann.sk.tsukuba.ac.jp/plone/Members/de/poker-28.htm]poker 28[/url] http://neumann.sk.tsukuba.ac.jp/plone/Members/de/poker-28.htm
([[Dale]] [Elizabeth@mail.com] [WEAK[2006-09-18 07:59:17 +00:00]])
[49]
Very useful poker [url=http://ibo.awardspace.com/poker/]poker[/url] http://ibo.awardspace.com/poker/
([[Robert]] [Christopher@mail.com] [WEAK[2006-09-18 09:59:39 +00:00]])
[50]
i like you! poker 30 [url=http://neumann.sk.tsukuba.ac.jp/plone/Members/de/poker-30.htm]poker 30[/url] http://neumann.sk.tsukuba.ac.jp/plone/Members/de/poker-30.htm
([[Leonard]] [Alton@mail.com] [WEAK[2006-09-18 13:58:49 +00:00]])
[51]
Very good site poker 31 [url=http://neumann.sk.tsukuba.ac.jp/plone/Members/de/poker-31.htm]poker 31[/url] http://neumann.sk.tsukuba.ac.jp/plone/Members/de/poker-31.htm
([[Zachary]] [Hannah@hotmail.com] [WEAK[2006-09-18 15:43:39 +00:00]])
[52]
archy it i poker 34 [url=http://neumann.sk.tsukuba.ac.jp/plone/Members/de/poker-34.htm]poker 34[/url] http://neumann.sk.tsukuba.ac.jp/plone/Members/de/poker-34.htm
([[Brianna]] [Brianna@hotmail.com] [WEAK[2006-09-18 19:39:58 +00:00]])
[53]
Great work on website. poker 35 [url=http://neumann.sk.tsukuba.ac.jp/plone/Members/de/poker-35.htm]poker 35[/url] http://neumann.sk.tsukuba.ac.jp/plone/Members/de/poker-35.htm
([[Brian]] [Mark@mail.com] [WEAK[2006-09-18 21:40:32 +00:00]])
[54]
Very nice site! internet poker [url=http://free.45.kg/pisya/poker-internet.htm]internet poker[/url] http://free.45.kg/pisya/poker-internet.htm
([[John]] [Robert@mail.com] [WEAK[2006-09-20 21:23:42 +00:00]])
[55]
archy it i poker [url=http://free.45.kg/piz/poker.htm]poker[/url] http://free.45.kg/piz/poker.htm
([[Brianna]] [Jacob@hotmail.com] [WEAK[2006-09-20 23:26:00 +00:00]])
[56]
Great work on website. gg [url=http://xoomer.alice.it/pidr/gg/]gg[/url] http://xoomer.alice.it/pidr/gg/
([[Christopher]] [John@mail.com] [WEAK[2006-09-21 01:30:08 +00:00]])
[57]
Great work on website. 3 [url=http://xoomer.alice.it/naxibo/3/]3[/url] http://xoomer.alice.it/naxibo/3/
([[Michael]] [Anthony@mail.com] [WEAK[2006-09-22 13:17:46 +00:00]])
[58]
Very useful 4 [url=http://xoomer.alice.it/naxibo/4/]4[/url] http://xoomer.alice.it/naxibo/4/
([[Jacob]] [Samantha@hotmail.com] [WEAK[2006-09-22 15:25:29 +00:00]])
[59]
Great web site 5 [url=http://xoomer.alice.it/naxibo/5/]5[/url] http://xoomer.alice.it/naxibo/5/
([[George]] [Larry@mail.com] [WEAK[2006-09-22 17:22:15 +00:00]])
[60]
this site rocks! royale [url=http://xoomer.alice.it/icrest/royale/]royale[/url] http://xoomer.alice.it/icrest/royale/
([[Ada]] [Brianna@hotmail.com] [WEAK[2006-09-22 19:16:07 +00:00]])
[61]
Very nice site foreclosure [url=http://xoomer.alice.it/kuk1/foreclosure/]foreclosure[/url] http://xoomer.alice.it/kuk1/foreclosure/
([[Robert]] [Matthew@mail.com] [WEAK[2006-09-22 21:23:05 +00:00]])
[62]
It very interesting satellite tv [url=http://xoomer.alice.it/kuk1/satellite-tv/]satellite tv[/url] http://xoomer.alice.it/kuk1/satellite-tv/
([[Zachary]] [Frank@mail.com] [WEAK[2006-09-22 23:20:12 +00:00]])
[63]
Interesting site morongo [url=http://xoomer.alice.it/icrest/morongo/]morongo[/url] http://xoomer.alice.it/icrest/morongo/
([[Matthew]] [Hailey@hotmail.com] [WEAK[2006-09-23 03:18:14 +00:00]])
[64]
It very interesting rewards [url=http://xoomer.alice.it/icrest/rewards/]rewards[/url] http://xoomer.alice.it/icrest/rewards/
([[John]] [Kaylee@hotmail.com] [WEAK[2006-09-23 05:15:53 +00:00]])
[65]
VERY GOOD I THINK arizona [url=http://xoomer.alice.it/icrest/arizona/]arizona[/url] http://xoomer.alice.it/icrest/arizona/
([[Hannah]] [Ada@mail.com] [WEAK[2006-09-23 07:37:34 +00:00]])
[66]
thanks for mentioning lemon law [url=http://lemon.awardspace.biz/lemon-law/]lemon law[/url] http://lemon.awardspace.biz/lemon-law/
([[Richard]] [Hailey@mail.com] [WEAK[2006-09-23 13:37:30 +00:00]])
[67]
thanks for mentioning slot machine [url=http://slot.awardspace.biz/slot-machine/]slot machine[/url] http://slot.awardspace.biz/slot-machine/
([[Hannah]] [Frank@mail.com] [WEAK[2006-09-23 17:37:22 +00:00]])
[68]
Very good site pr [url=http://xoomer.alice.it/ddoys/pr/]pr[/url] http://xoomer.alice.it/ddoys/pr/
([[Dale]] [Jasmine@hotmail.com] [WEAK[2006-09-23 21:35:43 +00:00]])
[69]
It very interesting experian [url=http://experian.awardspace.biz/experian/]experian[/url] http://experian.awardspace.biz/experian/
([[Daniel]] [Emily@hotmail.com] [WEAK[2006-09-23 23:30:50 +00:00]])
[70]
Hi, nice site! consolidation [url=http://cons.awardspace.biz/consolidation/]consolidation[/url] http://cons.awardspace.biz/consolidation/
([[Dylan]] [Maureen@mail.com] [WEAK[2006-09-24 01:32:06 +00:00]])
[71]
Thank you... pokers [url=http://po.awardspace.biz/pokers/]pokers[/url] http://po.awardspace.biz/pokers/
([[Donald]] [Jacob@hotmail.com] [WEAK[2006-09-24 03:31:06 +00:00]])
[72]
Very nice site! steroid [url=http://ster.awardspace.biz/steroid/]steroid[/url] http://ster.awardspace.biz/steroid/
([[Dale]] [John@mail.com] [WEAK[2006-09-24 05:33:10 +00:00]])
[73]
thanks for mentioning az [url=http://xoomer.alice.it/pok3/az/]az[/url] http://xoomer.alice.it/pok3/az/
([[Larry]] [Lori@mail.com] [WEAK[2006-09-24 07:41:49 +00:00]])
[74]
This great resource xe [url=http://xoomer.alice.it/j18/xe/]xe[/url] http://xoomer.alice.it/j18/xe/
([[Brian]] [Emily@mail.com] [WEAK[2006-09-24 09:44:06 +00:00]])
[75]
Good Luck! anti [url=http://xoomer.alice.it/scukona/anti/]anti[/url] http://xoomer.alice.it/scukona/anti/
([[Reginald]] [Lori@mail.com] [WEAK[2006-09-24 11:58:43 +00:00]])
[76]
this site rocks! download music [url=http://xoomer.alice.it/jopa/download-music/]download music[/url] http://xoomer.alice.it/jopa/download-music/
([[Bill]] [Jacob@mail.com] [WEAK[2006-09-24 16:05:36 +00:00]])
[77]
this site rocks! download music [url=http://xoomer.alice.it/jopa/download-music/]download music[/url] http://xoomer.alice.it/jopa/download-music/
([[Bill]] [Jacob@mail.com] [WEAK[2006-09-24 18:02:24 +00:00]])
[78]
Very useful http://bbi.awardspace.co.uk/air-ticket/
([[John]] [Matthew@mail.com] [WEAK[2006-09-24 19:47:13 +00:00]])
[79]
thanks for mentioning http://nlp.awardspace.co.uk/cartridge-inkjet/
([[Daniel]] [Ada@mail.com] [WEAK[2006-09-24 21:38:50 +00:00]])
[80]
It very interesting http://sosi.awardspace.co.uk/casin/
([[John]] [John@mail.com] [WEAK[2006-09-24 23:41:25 +00:00]])
[81]
Very nice site http://xoomer.alice.it/jopa/anti-virus/
([[Hannah]] [Hannah@mail.com] [WEAK[2006-09-25 01:51:18 +00:00]])
[82]
Good Luck! http://xoomer.alice.it/fe7/texas-holdem-poker-table/
([[Frank]] [Dale@mail.com] [WEAK[2006-09-25 11:36:11 +00:00]])
[83]
[CITE@en[RFC 1942 - HTML Tables]] ([CODE[2007-01-14 17:48:08 +09:00]] 版)
([[名無しさん]])
[84]
Hi. Nice site! Just change that background :) See my site: Sedas http://encyko.bee.pl/sedas.html [url=http://encyko.bee.pl/sedas.html]Sedas[/url]
([[encyko.bee.pl/sedas.html]] [20287@gmail.com])
[85]
Wikipedia:Caf辿/Marzo de 2005 01 http://encyko.bee.pl/wikipedia.caf.marzo.de.2005.01.html [url=http://encyko.bee.pl/wikipedia.caf.marzo.de.2005.01.html]Wikipedia:Caf辿/Marzo de 2005 01[/url]
([[encyko.bee.pl/wikipedia.caf.marzo.de.2005.01.html]] [24532@gmail.com])
[86]
Hello. I like your site very much. Please visit my site: Journal of Medical Internet Research http://encyko.bee.pl/journal.of.medical.internet.research.html [url=http://encyko.bee.pl/journal.of.medical.internet.research.html]Journal of Medical Internet Research[/url] and leave some feedback. Thanks!
([[encyko.bee.pl/journal.of.medical.internet.research.html]] [20149@gmail.com])
[87]
Dobrii den'! Ya chelovek!
([[Tommy]] [koturren.gol@yahho.com])
|