emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Sebastian Rose <sebastian_rose@gmx.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: An improvement for a reading of exported HTML tables
Date: Fri, 8 May 2009 06:36:41 +0200	[thread overview]
Message-ID: <C41A76CF-2B40-445D-BD95-92FA56E4A55B@gmail.com> (raw)
In-Reply-To: <87ws8skj8l.fsf@kassiopeya.MSHEIMNETZ>


On May 7, 2009, at 5:47 PM, Sebastian Rose wrote:

> Jan Buchal <buchal@brailcom.org> writes:
>>    CD> On May 7, 2009, at 12:44 PM, Jan Buchal wrote:
>>
>>>>>>>> "CD" == Carsten Dominik <carsten.dominik@gmail.com> writes:
>>>>
>>    CD> On May 7, 2009, at 11:38 AM, Jan Buchal wrote:
>>>
>>>> Hello again,
>>>>>
>>>>> the problem is little bit complicate :-) I need <th> not in first
>>>>> row only but by every column which contain the name of row. In
>>>>> the attachment you can find the example
>>>
>>>   CD> That is currently not possible.
>>> And is it possible fix it? From the point of view of accessibility  
>>> is a
>>> bug.
>>
>>    CD> I would not call it a bug, it is a limitation. Org is not a  
>> full
>>    CD> HTML table editor, there are many things it cannot do,  
>> including
>>    CD> column and row spanning, multiline fields, you name it.
>> Unfortunately it is a bug. See please WCAG documentation.
>
>
> It's not. It's just something not implemented. And, as I see it, it
> would be complicated to implement.
>
>
> What you want seems to be this:
>
>  1. It's recommended to put the column headers into the <thead>  
> element
>     (Org-mode does this). That way column headers are re-printed on  
> every
>     page, if a table exceeds the size of one printed page.
>
>  2. It's recommended to use <th> elements in tables like this:
>
>  | Country | Number of citizens  |
>  |---------+--------------------|
>  | Germany | 84 Mio.            |
>  | France  | XXX Mio.           |
>
>  In this case it could make sense to put the country names in <th>
>  tags (see 4.). I think this is, what you wanted.
>
>
>  3. Use the caption element to describe the purpose of a
>     table. Org-mode does this.
>
>
>  4. The `scope' attribut describes, wich table cells are concerned by
>     the <th> element.
>
>     Again, our country example. This table should be handled corretly
>     by a screen reader:
>
>     <table>
>      <caption>Citizens per country</caption>
>      <thead>
>       <tr>
>        <th scope="col"> Country </th>
>        <th scope="col"> Number of citizens </th>
>       </tr>
>     </thead>
>     <tbody>
>      <tr>
>       <th scope="row"> Germany </th>
>       <td> 84 Mio. </td>
>      </tr>
>      <tr>
>       <th scope="row"> France </th>
>       <td> XXX Mio. </td>
>      </tr>
>      ...
>
>
> There are more possible values for `scope' (`colgroup' and `rowgroup')
> as well, as some additional possibilities to assign headers to cells
> (`header' and `id') in such a way, that multiple headers describe one
> cell.
>
> In our example, the headers `Germany' and `Number of citizens' would
> describe the cell `84 Mio.'.
>
>
>
> I don't see, how Org-mode could decide which headers describe wich
> cells.
>
> The most obvious thing to do would be, to
>
>
>    a) mark cells as table-headers (this is the only needed new
>       Org-syntax feature),
>    b) if in the first table row, add a  scope="col" to the <th> tag,
>    c) if in the first column, add a   scope="row"  to  the <th> tag.


OK, this is ho it works now....

Thanks

- Carsten

>
>
>
> Beacuse if we take all those possible assignments into account, we'll
> get something complicated to code, use and document...
> We would have to end with some kind of `formular' syntax, like the one
> used for the spreadsheet capabilities.
>
>
> Regards
>
>   Sebastian

  reply	other threads:[~2009-05-08  4:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-06 14:13 An improvement for a reading of exported HTML tables Giovanni Ridolfi
2009-05-06 15:28 ` Jan Buchal
2009-05-07  6:46   ` Carsten Dominik
2009-05-07  9:09     ` Jan Buchal
2009-05-07  9:38 ` Jan Buchal
2009-05-07 10:09   ` Carsten Dominik
2009-05-07 10:44     ` Jan Buchal
2009-05-07 12:29       ` Carsten Dominik
2009-05-07 13:12         ` Carsten Dominik
2009-05-07 13:43           ` Jan Buchal
2009-05-07 15:00           ` Nick Dokos
2009-05-07 16:21             ` Carsten Dominik
2009-05-07 13:31         ` Jan Buchal
2009-05-07 15:47           ` Sebastian Rose
2009-05-08  4:36             ` Carsten Dominik [this message]
2009-05-09  8:52               ` Jan Buchal
2009-05-11  5:25                 ` Carsten Dominik
2009-05-08  8:37             ` Jan Buchal
2009-05-08  9:03               ` Carsten Dominik
2009-05-08 10:39                 ` Jan Buchal
2009-05-08 14:50                   ` Nick Dokos
  -- strict thread matches above, loose matches on Subject: below --
2009-05-07  7:52 Giovanni Ridolfi
2009-05-07  8:52 ` Jan Buchal
2009-05-06 13:11 Jan Buchal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C41A76CF-2B40-445D-BD95-92FA56E4A55B@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sebastian_rose@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).