I made a preliminary page, and fleshed out some of the headers/sub-headers on the wiki page for a good Haskell Cookbook (aka NOT a PLEAC clone). Please contribute and/or fix the examples and explanations so we can make a really nice Cookbook for newbies. :) http://haskell.org/haskellwiki/Cookbook
and can I please ask anyone thinking of using special symbols to resist the temptation. Symbols such as the &160 used liberally in the Haskell wikibook are totally invisible to screen readers. I would be happy to proof read any document before it goes to the wikibook to ensure it's fully accessible to screen readers. Regards, Paul At 03:17 22/02/2007, you wrote:
I made a preliminary page, and fleshed out some of the headers/sub-headers on the wiki page for a good Haskell Cookbook (aka NOT a PLEAC clone). Please contribute and/or fix the examples and explanations so we can make a really nice Cookbook for newbies. :)
http://haskell.org/haskellwiki/Cookbook
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
I second this plea. -- Jeff On Wednesday 21 February 2007 22:34, P. R. Stanley wrote:
and can I please ask anyone thinking of using special symbols to resist the temptation. Symbols such as the &160 used liberally in the Haskell wikibook are totally invisible to screen readers. I would be happy to proof read any document before it goes to the wikibook to ensure it's fully accessible to screen readers.
Regards, Paul
At 03:17 22/02/2007, you wrote:
I made a preliminary page, and fleshed out some of the headers/sub-headers on the wiki page for a good Haskell Cookbook (aka NOT a PLEAC clone). Please contribute and/or fix the examples and explanations so we can make a really nice Cookbook for newbies. :)
http://haskell.org/haskellwiki/Cookbook
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
On Thu, 22 Feb 2007 03:34:54 +0000, you wrote:
and can I please ask anyone thinking of using special symbols to resist the temptation. Symbols such as the &160 used liberally in the Haskell wikibook are totally invisible to screen readers.
I can understand the desire to avoid special characters, but out of curiosity, what exactly is the problem with screen readers and the NO BREAK SPACE character (which is pretty ubiquitous in HTML)? Steve Schafer Fenestra Technologies Corp. http://www.fenestra.com/
Well, actually, I never cited the non-breaking space character as a problem. I'm referring to math symbols which do not get successfully translated into an intelligible symbol in the screen reader browse buffer. Regards, Paul At 17:46 23/02/2007, you wrote:
On Thu, 22 Feb 2007 03:34:54 +0000, you wrote:
and can I please ask anyone thinking of using special symbols to resist the temptation. Symbols such as the &160 used liberally in the Haskell wikibook are totally invisible to screen readers.
I can understand the desire to avoid special characters, but out of curiosity, what exactly is the problem with screen readers and the NO BREAK SPACE character (which is pretty ubiquitous in HTML)?
Steve Schafer Fenestra Technologies Corp. http://www.fenestra.com/ _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
On Fri, 23 Feb 2007 18:09:15 +0000, you wrote:
Well, actually, I never cited the non-breaking space character as a problem.
Well, actually, you did:
Symbols such as the &160 used liberally in the Haskell wikibook are totally invisible to screen readers.
= NO BREAK SPACE Which is why I asked specifically about that. Steve Schafer Fenestra Technologies Corp. http://www.fenestra.com/
So that's what it is! I wondered why alt-num-0160 only produced a space character. Still, as I said originally, it is totally invisible in the browse buffer. Anyway, are you one of the authors of the wikibook Or, are you just offering your assistance? All the best Paul At 19:03 23/02/2007, you wrote:
On Fri, 23 Feb 2007 18:09:15 +0000, you wrote:
Well, actually, I never cited the non-breaking space character as a problem.
Well, actually, you did:
Symbols such as the &160 used liberally in the Haskell wikibook are totally invisible to screen readers.
= NO BREAK SPACE
Which is why I asked specifically about that.
Steve Schafer Fenestra Technologies Corp. http://www.fenestra.com/ _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
In the wonderful tradition of a contemporaneously have-able and edible pie, one can have two versions of a page -- with lovely calculus symbols or their horribly debauched ASCII remains -- and a button to switch. Heck, one can have a Greasemonkey script to eat the page toggle that and leave the page alone. Wiki has the pie, Greasemonkey eats it. Cheers, Alexy
On Fri, 23 Feb 2007 19:42:27 +0000, you wrote:
So that's what it is! I wondered why alt-num-0160 only produced a space character. Still, as I said originally, it is totally invisible in the browse buffer. Anyway, are you one of the authors of the wikibook Or, are you just offering your assistance?
Neither, just curious. While I can see how some characters might cause problems, I couldn't understand why non-breaking spaces would. Steve Schafer Fenestra Technologies Corp. http://www.fenestra.com/
P. R. Stanley wrote:
I'm referring to math symbols which do not get successfully translated into an intelligible symbol in the screen reader browse buffer.
Is there a way to make the symbols both look right on a screen and sound right from a screen reader? E.g., <span title="big sigma">Σ</span> <!-- there's a U+03A3 in there -->
On Fri, Feb 23, 2007 at 03:07:18PM -0500, Seth Gordon wrote:
P. R. Stanley wrote:
I'm referring to math symbols which do not get successfully translated into an intelligible symbol in the screen reader browse buffer.
Is there a way to make the symbols both look right on a screen and sound right from a screen reader?
yes, by employing document translation this is often the purpose of employing docbook or another document-oriented schema - you down-translate into xhtml, pdf, ascii, etc these down-translations can often be performed with available tools down-translating for a screen reader implies maintaining some sort of association of entities to literal chars/phrase etc. its likely that users of these screen readers know the capabilities of the tools and are likely best to provide this function removing all glyphs which cannot come out of a screen reader is not a viable solution - xhtml markup adds real value for 99.9% of users.
Is there a way to make the symbols both look right on a screen and sound right from a screen reader? E.g.,
<span title="big sigma">Σ</span> <!-- there's a U+03A3 in there --> In theory the title attribute should be the adequate yet simple solution we're after. Sadly, in reality this 'aint the case. The title attribute works beautifully in list and table elements.
Having read some of the posts I've come to the conclusion that the addition of Latex source code along with the unicode stuff may be the best way forward. I am, however, still open to new ideas. So please don't hesitate to keep them coming. By the way guys, if we're straying off-topic here please feel free to drop me a line privately. Best wishes Paul
Hey everyone, we added some examples to this page. There are some topics that don't have any examples, notably: # 11 Network Programming # 12 XML * 12.1 Parsing XML # 13 Databases * 13.1 MySQL * 13.2 PostgreSQL * 13.3 SQLite # 14 FFI * 14.1 How to interface with C If anyone feels like filling up some of those sections, that would be great. -chris On 21 Feb, 2007, at 20:17 , Martin Bishop wrote:
I made a preliminary page, and fleshed out some of the headers/sub- headers on the wiki page for a good Haskell Cookbook (aka NOT a PLEAC clone). Please contribute and/or fix the examples and explanations so we can make a really nice Cookbook for newbies. :)
http://haskell.org/haskellwiki/Cookbook
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
On 2/26/07, Chris Eidhof
Hey everyone,
we added some examples to this page. There are some topics that don't have any examples, notably: # 11 Network Programming # 12 XML * 12.1 Parsing XML # 13 Databases * 13.1 MySQL * 13.2 PostgreSQL * 13.3 SQLite # 14 FFI * 14.1 How to interface with C
If anyone feels like filling up some of those sections, that would be great.
I'd also suggest adding * 4.4 Regular expressions * 4.5 Interpolation martin
participants (9)
-
Alexy Khrabrov -
brad clawsie -
Chris Eidhof -
Jefferson Heard -
Martin Bishop -
Martin DeMello -
P. R. Stanley -
Seth Gordon -
Steve Schafer