> * Need to convert rfc8222 to xml/html
>
> I haven't found anything substantial via searching. My next step is to
> go spelunking in MailManager code and other python-webmail packages. If
> anyone knows good trees in this forest, please clue me in.
>
Do you mean 2822? or 822? 8222 doesn't exist
--On Tuesday, July 4, 2006 9:44 PM +0200 emf wrote:
> I am determined to provide some JavaScript in the 'standard'
> interface, as it will make for enhanced ease-of-use for those sighted
> people using a modern browser.
Hi Ethan,
It says in 6.3 of WCAG 1.0 to "Ensure that pages are usable when
If mailman would be able to write an xml representation of
each message to a separate file, that would be wonderful.
Then one would be able to use xlst stylesheets to make
custom archives. I hacked something like this together for
an on-line class. The workflow was:
(1) mailman writes each mess
(Mailman 2.1.8)
Probably trivial; probably my misunderstanding. But...
... at the end of "Approve.py" is some code to detect multiple passes
through a list ("x-beenthere" etc.).
But "Approve.py" is about handling passwords, whereas loop-detection has
no relation to such authentication issues.
On Tue, 2006-07-04 at 15:44 -0400, emf wrote:
> In order to provide interfaces to archives, I believe I must perform
> some intermediary manipulation; my goal is to get the information
> contained within the .mbox files mailman generates into ElementTrees and
> other objects so as to represent t
emf wrote:
> Gentlebeings,
>
> I have read a depressing and recent article suggesting that DOM
> manipulations are invisible to most screen readers [1]. There are some
> workarounds suggested in [2], but for the most part it looks like
> dangerous territory.
Silly me, I didn't include the link
Laura Carlson wrote:
> Heavyweight DOM scripting, often results in inaccessible content,
The main point I'm driving at is *any* dom manipulation - heavy, light,
fat-free, or decaf - appears to be invisible to the screen reading user
unless I do it "downstream" of the focused text. I'm talking
On 7/5/06 11:26 AM, "emf" <[EMAIL PROTECTED]> wrote:
> The problem I face is not when JavaScript is not active, the problem is
> when JavaScript *is* active *and* behaves correctly - i.e. performs the
> dom modification I've told it to - but the browser/screen reader doesn't
> bother to tell the u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 5, 2006, at 10:26 AM, David Lee wrote:
> (Mailman 2.1.8)
>
> Probably trivial; probably my misunderstanding. But...
>
> ... at the end of "Approve.py" is some code to detect multiple passes
> through a list ("x-beenthere" etc.).
>
> But "Appro
--On Wednesday, July 5, 2006 8:54 PM +0200 emf wrote:
> Are you suggesting I provide *no* link for the
> screen-reader-with-javascript client and let them at some point
> figure out that they're not seeing what's going on and thus turn off
> javascript?
>
> That seems like a worse solution.
I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you want to get a taste of the things I'm going to check in soon,
please see:
http://wiki.list.org/x/vg
- -Barry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (Darwin)
iQCVAwUBRKwk5nEjvBPtnXfVAQJnOQP+KM/W9bVSRGXmhJkzJOQJHZiMSUNYn4s8
WZ+D
Laura Carlson wrote:
> --On Wednesday, July 5, 2006 8:54 PM +0200 emf wrote:
>
>> Are you suggesting I provide *no* link for the
>> screen-reader-with-javascript client and let them at some point
>> figure out that they're not seeing what's going on and thus turn off
>> javascript?
>>
>> That see
John Dennis wrote:
> It's not at all clear to me that mailman should be responsible for
> archiving.
While I am somewhat in agreement, the current situation is that
archiving comes bundled with mailman and represents a significant
weakness in its current web UI. Not doing anything about the web
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 5, 2006, at 6:37 PM, emf wrote:
>> I seem to
>> recall this is also Barry's preference who noted the existing
>> pipermail
>> was only a stop-gap solution so there would be some default archiver,
>> but it was never the intention Mailman woul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 4, 2006, at 3:44 PM, emf wrote:
> Here's where I'm at, grouped functionally:
>
> * Need to convert rfc8222 to xml/html
>
> I haven't found anything substantial via searching. My next step is to
> go spelunking in MailManager code and other pyth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 4, 2006, at 5:33 PM, Brad Knowles wrote:
> Don't ignore non-Python solutions.
My main problem with non-Python solutions /as a default for Mailman/
is that it complicates distribution and packaging. It means that
we'll have additional depe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 5, 2006, at 12:30 AM, Mark Sapiro wrote:
> Also there is a related issue if A posts, B replies, A replies off
> list
> to B, and B replies on list. If threading relies solely on References:
> or In-Reply-To:, and either A's or B's MUA generat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jul 5, 2006, at 10:01 AM, Hans G. Ehrbar wrote:
> If mailman would be able to write an xml representation of
> each message to a separate file, that would be wonderful.
> Then one would be able to use xlst stylesheets to make
> custom archives.
It
>
>There is MSAA, Microsoft Active Accessibility, and a replacement with Vista, I
>believe, but don't remember what it is called. Don't know if they can be used
>by style sheets, but inquiry to [EMAIL PROTECTED] might be in order.
>
>Dave
>
>At 12:45 PM 7/4/2006, you wrote:
>>Gentlebeings,
>>
>
>
>I believe there is a "screen reader present" flag in Windows, don't know any
>more than that.
>
>Dave
>
>At 12:59 PM 7/4/2006, you wrote:
>>Ethan wrote:
>>
>>> Note that this would be in *addition* to the ability to get a JS-free
>>> version of the interface by using a different URL prefix for
>
>I believe that the W3C standards require that Javascript and other components
>fail gracefully, so the point could be made, for things link Lynx and Links
>that a graceful degrade would also take care of us screen reader users.
>Anything specific you write for us, while appreciated, is also
On 7/5/06 4:30 PM, "Barry Warsaw" <[EMAIL PROTECTED]> wrote:
> I'm thinking something along the lines of sha1 hashing Message-ID and
> perhaps Date. RFC 2822 $3.6 says that the only required headers are
> the origination date (Date:) and originator address fields (From: and
> possibly Sender: and
That assertion is not true, to my knowledge -- and I am a screen reader user.
Because it does work with a lot of things, and does offer improved
functionality, it is rare to turn Javascript off.
David Andrews
At 01:54 PM 7/5/2006, John W. Baxter wrote:
>On 7/5/06 11:26 AM, "emf" <[EMAIL PROTEC
I have installed a mirror of Wikipedia in my site here :
http://encyclopedia.meta99.com/
But i have some problems. I never used MediaWiki in past and i'm a newbie.
Can you help me ?
1) Some pages has strange words that don't exists in Wikipedia-
For example the "Cats" page and the "Dogs page" :
h
I MADE AN ERROR WITH ANOTHER MAILING LIST
I have posted the message in
mailman-developers@python.org and not in
[EMAIL PROTECTED]
PARDON ME
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailm
25 matches
Mail list logo
