![]() | This project page does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||
|
| ||||||||||||
|
||||||||||||
This page has archives. Sections older than 30 days may be automatically archived by Lowercase sigmabot III when more than 2 sections are present. |
IP requested Spoken Wikipedia for that page. 176.223.186.133 (talk) 18:49, 3 January 2025 (UTC)
- And it's still not being recorded. 67.209.129.27 (talk) 18:31, 13 January 2025 (UTC)
- Patience is a virtue, you're always free to create a recording yourself! 7kk (talk) 00:26, 7 March 2025 (UTC)
How to deal with large and complicated tables
A thought of mine on how to deal with large and complicated tables such as Ed Bradley#Awards and recognition. In such cases, the spoken editor faces a challenge. Doing a complete detailed read out is laborious and at the same time very difficult for a listener to parse and usually not useful.
Different approaches could be used while dealing with tables:
- Option 1 - Summarise very broadly.
- Option 2 - Summarise very broadly. AND Give the name of the audio file where the details are completely .
- Option 3 - Group common items and summarise. AND Give the name of the audio file where the details are completely .
- Option 4 - Choose most important items to expound in full. AND Give the name of the audio file where the details are completely .
- Option 5 - Give the details completely.
One could choose any approach. However, the listener should be clear from your script that what you are saying regarding the table is your summary work and not the original text of the article.
This thought of mine arose from a question to me from M4V3R1CK32. I invite thoughts and views from others on this issue.
Ashwin Baindur (User:AshLin) (talk) 06:10, 10 March 2025 (UTC)
You must be logged in to post a comment.