[sane-standard] sane standard proposals (4) "translation"

[Johannes Berg]

--=-J62ha2La8FisfEQdrpKc
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

The SANE standard specifies how backends should mark their strings for
translation, and that frontends are responsible for actually translating
the messages.

I think it is unfair to ask each frontend to be able to translate all
strings that could possibly occur, and this is also impossible if you
deploy a new scanner backend on a network server without updating client
software.

Therefore, I propose that translations be associated to the backends by
way of naming files ("/some/where/de/coolscan2.mo") and that an API be
added to access these translations from a frontend, without knowing
about the strings itself.

Also, this functionality should be added to the networking protocol so
that older clients (frontends) can still function properly with newly
deployed backends.

Clients are of course encouraged to cache translations.

johannes

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

-----BEGIN PGP SIGNATURE-----
Comment: Johannes Berg (SIP Solutions)

iQIVAwUAQWnWqqVg1VMiehFYAQJLuRAAs+vyXZfKWS+2aZFuaHZL2tk5LHoRCieX
o7P24YVAY+BSJ9HuVQH06qZPkiOOPNr0ZrXSGKcydZe9/awIxDCQ5tdJenBBg8EK
4uIPfu//OXZlP8yrn5CbhEHG7NzAduYLjs9RS/LpWQWehXlOGFxP5L1mrIUp/Jo5
fyhNVjz/EJqzxu7f5p9Z9zlgg1/8Mza0ubMPtNqps7JiZdDTbJjM2rfTNHhJA8Ys
aXyyVZ0UC6TEUKsnvQel58ZvBFhMxtYk4815DzEmiJSaFKEfbwqbH8uNzFGSFqY2
IZP0+xDhWYvh0gqPOQDeI1dSOm/HAbQ35f0n83AuRR7d3jzGNj2273pDXgbJlDk6
HpVH/UTleODTDiNy5/qUCCuZe9vJ5LzRIEBdF1vIKRP2HyfBOTEutyfcfBZgYR9X
WajTdf9TC4OTLWuZ3fTNZpwxlXhwQoHmbIhtEVgu4J81OQI66pjuiI5yCI1/diT5
AzIV2E3tT+U/cLRomwjPF0wU1jfC/HjM8md4yh1+7WcWOLfDZE+ghdIliVxuHYoZ
6MhXKbc84jEbXqwguBKSJhoKhr4E17I+Ar5C+dIK2akH+BFVnTug/p74ssYpY7nx
WrSGq7NNVmlYGynxIqHJl+qTdyKvOX1IMtM/2VOA/EByDWo+bPTDc5jy2tiiJPOb
iGtzbxSsl5Y=
=PYHA
-----END PGP SIGNATURE-----

--=-J62ha2La8FisfEQdrpKc--