> From: Sherlock, Ric <[EMAIL PROTECTED]>
>
> ---Oleg Kobchenko wrote:
> > This already looks much better.
> > A few things about egpage2a.html though:
> >
> > * white space is important, it must be symmetrical,
> if
> > fact I much prefer the same white space treatment
> as
> > in the original dictionary HTML
>
> Are you referring to the vertical whitespace around the
> names? There shouldn't be any problem adjusting the CSS
> to provide the desired white space, but of course personal
> preferences will come in to play. I have made a formatting
> change that I think improves the visual clarity of the
> page.
> http://www.massey.ac.nz/~rsherloc/jdict/egpage2a.html
I actually meant white space in the source HTML,
ie indentation, etc. Sorry for confusion.
But the rendered spacing is also important. I think
original Dictionary, as well as keiapl.info have good
taste in spacing, which is good to be preserved.
> However it might be better for us to try and come to a
> consensus on the structural markup first before we get
> bogged down on these ;-).
>
> > * I gather, <!--top jump start--> and
> <divid="Header">
> > should be mutually exclusive
>
> > * I am not sure <divid="Examples">
> has much merit,
> > with <P> addition, the rest of the page can
> be just
> > thought as part of the body.
> >
> > * The same refers to
> <divid="Content">.
> > It could also be just part of body.
>
> By removing all these divs it would no longer be possible
> to specifically target tags (<a> <li> <p>
> etc) in the Header vs the Content, and distinguishing
> different tag formatting for pdefn vs Examples would be
> more awkward. I would argue that the Header, Content,
> Examples, Exercises and Footer divs add enough benefit, for
> a small increase in complexity, to be retained.
Why if we keep the Header and Footer DIVs?
While others would be top-level, but without enclosure
inside Content, Examples etc.
> > * THEAD is a kind of "row group", but it
> that has
> > only one element is not a group. So TR
> id="..." is more
> > appropriate here.
>
> A list cannot have 1 element? ;-)
> Another option would be to use
> <tr><th></th><th></th></tr>?
> (see updated page).
Yes TH is an even better approach.
> > * separation of symbol and ranks is too fussy. Either
> putting
> > them all in one TD with a class or id, or at most
> separating
> > just symbol and ranks together in spans:
> > <span
> id="sym">^</span><span
> id="rank">0 0 0</span>
> > but this is too much, as they could be easily split
> by space.
>
> To me they are logically different elements and it would
> therefore be better to separate them using markup even if
> they are not separated visually. If you were going to
> create an index for the pages, should the index entry be
> "^" or "^ 0 0 0" ?
XPath: substring-before(//[EMAIL PROTECTED]'symrank'], ' ')
>
> > I think just TD would suffice
> > <TD id="sym">^ 0 0 0</TD>
>
> I'm not sure how to include that TD in the table so
> that the columns still work? Maybe insert an extra row at
> the top and colspan it across all columns?
I believe it is better to keep it simple and return to
the original two tables:
<table id="SymHead" width="100%"><tr>
<th id="MonadName" align="left" width="33%">Example</th>
<th id="SymRank" align="center" width="34%">^ 0 0 0</th>
<th id="DyadName" align="right" width="33%">Example</th>
</table>
<table id="SymDef" width="100%"><tr>
<td id="MonadDef" width="49%">Description of <tt>x</tt> ...</td>
<td id="Spacer" width="1%"> </td>
<td id="DyadDef" width="50%">Description of <tt>y</tt> ...</td>
</table>
(Possibly widths and alignment placed in CSS).
> > Also to identify the page, HEAD/TITLE is used.
>
> Agreed.
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
