Re: Internationalisation of BXE User Interface

--===============1395558962==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-tA9r4DX04mYl44T88htV"


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

Hi folks,

Using the cocoon i18n schema obviously sounds pretty reasonable, it was
my first thought on how to internationalize BXE, too.=20
And Chregu, I'm amazed how simple already your experimental code looks,
that's cool.=20
The only thing I'm not sure of in this context is the size of the xml
file containing the string definitions. People might want to use the
same files they use for their CMS, so that file might be rather big..=20
loading it entirely into the editor might in that case not be the best
idea. If you have an idea how to solve that issue that'd be wonderful,
if not.. people that would want that can solve that information
duplication problem easily on the server side, so who cares..
Anyway, I'd hope it'll become a bit easier to sell BXE down here in the
French speaking regions with this feature :)
So thanks a lot, good to see bugging you about some feature does help
indeed :)

Regards,
Hannes

--=20
mediagonal sa // route de la fonderie 7 // ch-1700 fribourg
tel 026 422 25 11 // key id 0x9EA04604 // www.mediagonal.ch

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

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

iD8DBQBBwacKzEcScZ6gRgQRAqAiAJ9nOhEH052wPbPIL2/m8G7kD1hQKwCfbmrL
axHDESkNChSJMFVGjRmtunM=
=00ng
-----END PGP SIGNATURE-----

--=-tA9r4DX04mYl44T88htV--


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

-- 
bx-editor-dev mailing list
[email protected]
http://lists.bitflux.ch/cgi-bin/listinfo/bx-editor-dev

--===============1395558962==--