Freepages-Help-L ArchivesArchiver > Freepages-Help > 2010-02 > 1267228520
From: the cohens <>
Subject: Re: [FreeHelp] Need help formatting accessible tables
Date: Fri, 26 Feb 2010 15:55:20 -0800
I like the idea of adding nbsp's, it is a simple solution although
not pretty code.
I never heard of a separate table cell css, separate from declaring
the table in my css, which i did do. but I am declaring properties in
the tables themselves as I am testing.
And the problem is that the code I need to use to make good spacing
between page numbers and the cells above them for browsers that do
not recognize table formatting creates too much space in browsers that
can display tables.
I am skeptical that adding any css table code will eliminate the
effects of the extra br's I need to stick in for the lo fi browsers.
Barry had suggested in another context that using a div tag could
define dividing distances between elements, but I could not get my
text browser to recognize the code, I do not remember exactly what it
I decided against pre tags because I think it would be pretty
messy. If I understand them correctly, your other suggestions assume
a browser that recognizes fonts and table code, and my text browser
does not do that, nor does opera if I out it into a certain mode that
is more pda friendly, it's narrow screen mode.
where would the commas you are talking about go, anyone else know
what she is referring to with that?
On 2/26/10, <> wrote:
> For your tables: I don't always see so well ... but I couldn't see a css
> definition for table cells. You could define line height for text and left
> and right margins (% or other) for the cells. The page no. cell could be
> different, with no left margin and a wider right margin. Otherwise add the
> extra cell with as many nbsp as looks good (and if you don't have a specific
> special character, chain, replacement soft, Word does a fast job).
> Another way of forcing spacing, if your page content is definitive, is to
> look for the longest cell content and simply add a couple of nbsp after it
> ... old-fashioned but usually appears in browsers.
> If the page no. is less important and you want focus on content, put the
> first table cell into a smaller font?
> I'm not sure about browsers, but memories of data processing from long ago
> remind me that a comma may indicate that the following space should be
> ignored. If that is the problem, a long way round would be to change
> globally all the comma-spaces within table cells to comma-space space - the
> second space should be "read" by browsers ignoring the first, and the other
> browsers would normally only render 1 space.
> Alternatively, format your tables as you wish elsewhere and use the pre tag?
> (Or is that falling into desuetude?)
|Re: [FreeHelp] Need help formatting accessible tables by the cohens <>|