--===============0269112789==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="7ZAtKRhVyVSsbBD2"
Content-Disposition: inline


--7ZAtKRhVyVSsbBD2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Sep 14, 2004 at 07:14:35PM +0200, Ariya Hidayat wrote:
>=20
> >But that means that the translators would have to translate strings that=
=20
> >are nearly never used and where anyway you (as developer) would want the=
=20
> >output in English.
>=20
> Just to confirm, is it OK to use strings which are likely already=20
> introduced somewhere? I'd like to make test like whether the locale=20
> version of "True" is correct or not. That of course I need to check by=20
> changing the locale on my side.

Its best to always eliminate external influences (so somebody without the
translations does not get failing tests).

I suggest to extend KLocale (as DummyLocale for example) with a simple
catalog and work with i18n() from there.

--=20
Thomas Zander

--7ZAtKRhVyVSsbBD2
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBRy5yCojCW6H2z/QRAuoRAKCZTTXSJ9OAJYNOqEz10CsULzQZ7wCgk4Iq
egpMlG/6yqa+dmT7bqVKS3I=
=lfi9
-----END PGP SIGNATURE-----

--7ZAtKRhVyVSsbBD2--

--===============0269112789==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel

--===============0269112789==--