--===============0643219047==
Content-Type: multipart/signed;
  boundary="nextPart4458478.Y3XizA6TC1";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart4458478.Y3XizA6TC1
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,
I'm currently working on a wrapper library between net-snmp and qt/kde, whi=
ch=20
uses an OO interface, and QVariant, instead of the C-style APIs and unions.
I'll need this library for two projects (KNetLoad and atmosphere), and I wa=
nt=20
to make it a standalone library.
The problem is that I want to provide a simple way to convert the internal=
=20
values get from SNMP to strings (for instance the interface type for=20
routers), but some of these should be internationalized.

How internationalizing works on libraries?
Should I not use these, and instead move them to inlines, so that can be=20
included in the source of the application?

Thanks in advance,
=2D-=20
Diego "Flameeyes" Petten=F2
flameeyes@users.berlios.de - http://flameeyes.web.ctonet.it/

--nextPart4458478.Y3XizA6TC1
Content-Type: application/pgp-signature

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

iD8DBQBBrMs/e2h1+2mHVWMRAqzQAKDanB5LA/ufOnizSAVkrQ5pf2bczACgrmr1
oUD2thoALiWkbHmZ4DHPghs=
=clcy
-----END PGP SIGNATURE-----

--nextPart4458478.Y3XizA6TC1--

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

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

--===============0643219047==--