[Kde-accessibility] more on kmag

[JP Schnapper-Casteras]

Right, no hypen.  Kdeaccessibility sounds ok.  Why do we want to avoid =
kdeaccess?

I feel like kdeac or kdeacc won't mean anything to anyone but us.

Best,

--JP

Cell: 206-849-9032
Web: http://www.stanford.edu/~jpsc
LARS: http://trace.wisc.edu/linux
FDAWG: http://www.speechinfo.org/fdawg

-----Original Message-----
From: kde-accessibility-admin@mail.kde.org =
[mailto:kde-accessibility-admin@mail.kde.org]On Behalf Of Pupeno
Sent: Monday, December 30, 2002 4:02 PM
To: kde-accessibility@kde.org
Subject: Re: [Kde-accessibility] more on kmag

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 30 December 2002 18:50, JP Schnapper-Casteras wrote:
> Hi all, Sarang,
>         It seems like we're all in agreement about creating a new
> kde-accessibility package.
I agree about it's creation (although kttsd (now Proklam) and kacd (now
kaccess) should still go in kdebase as we discused.
About the name, other modules don't have a hyphen (-): kdelibs, kdebase,
kdeedu, kdegames, the only one with a hyphen is on that is a bit =
special,
kde-common.
So it should be kdeaccessibility instead... if that's a bit long, kdeac =
is ok
with me, kdeacc too... Olaf and Gunnar thought about other names (that I
still can't really understand, stupid me)... as we said, avoiding =
access.
Happy new year!
- --
Pupeno: pupeno@kde.org
KDE Accessibility co-maintainer
http://accessibility.kde.org
- ---
Help the hungry children of Argentina,
please go to (and make it your homepage):
http://www.porloschicos.com/servlet/PorLosChicos?comando=3Ddonar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+EN6PLr8z5XzmSDQRAvrzAJ9mHq5OoAPZWsBQoXTwOPJFOIOIAwCg0kuv
wPbD//dCrVsN3yrdlg6HNXg=3D
=3DzmwM
-----END PGP SIGNATURE-----

_______________________________________________
kde-accessibility mailing list
kde-accessibility@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-accessibility