[Kde-accessibility] Patches for docs

Lauri Watts lauri@kde.org
Sun, 2 Feb 2003 14:47:39 +0100


=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 02 February 2003 09:35, Olaf Jan Schmidt wrote:
> Hi Lauri!
>
> [Lauri Watts]
>
> > I have some patches to make changes in the documentation (kmag, kmouth,
> > and kmousetool).  Some are technical in nature, and just bring the docs
> > into a state consistent with the rest of KDE documentation, these I
> > normally commit anyway.
>
> Well, we were planning to go into string freeze on Friday, but since
> translation has not started yet, I think we should until all of those
> changes are commited. Gunnar, Pupeno, is that OK?

Heh, I did these a week ago and should have asked then, but I got sidetrack=
ed. =20
Patches for review here:
http://people.fruitsalad.org/lauri/patches/

Please ask me if you have *any* questions on any of the changes.  Some of t=
hem=20
will appear needlessly picky, but are to aid translation, such as changing=
=20
<keycap>Ctrl</keycap> -> &Ctrl; because that's already translated then.

Some are to give consistent rendering, for example, book title style=20
capitalization for headings, adding <guilabel> and <quote> instead of liter=
al=20
"..". =20

I think I removed a couple of references to "left" and "right" on the scree=
n=20
because we support bi-di languages, where left is not going to be left=20
anymore, and it helps them translating.  Up and down is safe, I don't know =
of=20
any languages which render their text bottom to top :)

> Well, since we have officially a string freeze now, I think it would be
> best to commit them after approval by Gunnar or Pupeno.

There is nothing here I consider so urgent that you should break a string=20
freeze for, if there was, I should have gotten organized and fixed them=20
earlier.    If you prefer to hold them until after you've got the 1.1 relea=
se=20
out the door, that's fine with me.

> > Another question: If I work up a framework for a "KDE Accessibility
> > Guide" would the team here be interested in helping me fill in the
> > blanks.
>
> Yes, I was also planning to do something like this. Iain, are you
> interested as well?
>

Great to hear! Then I'll write as much as I can of a skeleton in the next w=
eek=20
or so.

> BTW, after the 1.0 release of kdeaccessibility, we might do a 1.1 release
> before jumping directly to 3.2, so maybe the style guide could be
> released before KDE 3.2 is ready.

That's entirely possible.  In fact, as soon as it hits CVS, it should becom=
e=20
available on docs.kde.org, so you could start referring users to it long=20
before it's distributed with a KDE or kdeaccessibility release. =20

Regards,
=2D --=20
Lauri Watts
KDE Documentation: http://i18n.kde.org/doc/
KDE on FreeBSD: http://freebsd.kde.org/
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+PSF+/gUyA7PWnacRArq7AKCTrjndAnCRx3MxWz17j62V8uGK/gCeMu6b
hFP5zYzweWAj62RC4k5Wm14=3D
=3DzFMC
=2D----END PGP SIGNATURE-----