--nextPart42446719.QY1oOx6p0S
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable

On Thursday 06 May 2010, Rolf Eike Beer wrote:
> Hi,
>=20
> I'm just trying to get the last feature bits of KGpg for 4.5
> polished. One thing I did not pay any attention to is a text
> template the user should enter if he sends an automated mail. The
> idea is that KGpg will sign a bunch of ids at once and will send a
> mail out with the signed id using the text. Within the text there
> should be some placeholders to make the text less static.
>=20
> A very simple example could be:
>=20
> =3D=3D snip =3D=3D
> Hi %IDNAME,
>=20
> I'm sending you your key %KEYID.
>=20
> Have fun with it.
> %MYNAME
> =3D=3D snap =3D=3D
>=20
> And then I would so some simple search and replace on those variables
> and replace them with the texts for that particular id. This would
> basically be what you can see with in the mail templates of KMail
> for example.
>=20
> My questions are:
>=20
> -is it a good idea to make the placeholder names itself translatable?
> So this would be %MEINNAME instead of %MYNAME in German. In KMail
> those names are not translated. I don't mind but for non-English
> people that looks a bit strange and they may not even know what
> %QUOTE is.

I don't think it's a good idea to translate the placeholders. If you=20
really want to translate them then you should still store the template=20
with the untranslated placeholders. Otherwise, the templates will stop=20
working as soon as the user switches to another language. Also=20
exchanging templates with other users will be problematic.


Regards,
Ingo

--nextPart42446719.QY1oOx6p0S
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)

iEYEABECAAYFAkvjF64ACgkQGnR+RTDgudgReACfb5SGWyevBKXzne922drPoH/A
QmgAnifVHBzyJfbB3l2Ky1SWXnbfj4/D
=0rLu
-----END PGP SIGNATURE-----

--nextPart42446719.QY1oOx6p0S--