Bug#402567: apache2: BRF files support

[Samuel Thibault <samuel.thibault@ens-lyon.org>]

Thijs Kinkhorst, le Sat 13 Jan 2007 22:44:53 +0100, a écrit :
> On Sat, 2007-01-13 at 19:07 +0100, Samuel Thibault wrote:
> > The problem is that upstream seems to consider that such issue should
> > rather be handled by distributions, or even administrators.
> 
> Upstream does not talk about distributions.

But it tells it's not their affair, so what remains is distribution and
administrator :)

> I subscribe to their argument that if there's no predefined listings
> for any mime type, adding one for .brf would require very convincing
> arguments why it's different.

"If there's not predefined listings" indeed.  But debian still has some,
and I guess (and even hope) that in the future it will keep having some.

> > « Why I'm asking this to be the default for brf files is that people who
> > run websites which propose .brf files will probably _not_ be skilled
> > enough for knowing that to let visitors read them very easily, they
> > should add the mime.types entry and the charset entry (remember that
> > their area is accessibility, not computer administration). »
> 
> This would go for any specialistic file type to be added. And building
> an accessible website requires technical skills aswell...

Not the same as knowing that BRF files can be opened very easily with
proper mime type and charset announcement.  Note that official IETF
record is quite recent, and I fear that people won't realize it's
available until quite some time.  If Debian could contribute to
advertising it, that would help a lot.

Remember that accessibility is not only a specialistic issue, it's
a place where people have really _difficulties_ just doing everyday
things.

Samuel