On 16.12.2004 16:17 Uhr, Hannes Gassert wrote:
Hi folks,
Using the cocoon i18n schema obviously sounds pretty reasonable, it was
my first thought on how to internationalize BXE, too.
And Chregu, I'm amazed how simple already your experimental code looks,
that's cool.
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..
IMHO, not my problem.
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..
Yep, for example with xinclude... Have one master file, which xincludes
smaller subfiles. If you need everything, load the masterfile, if you
need only subparts of it, load a subfile (for BXE for example). Pretty
easy to do on the server side (with a decent XML processor, of course)
Anyway, I'd hope it'll become a bit easier to sell BXE down here in the
French speaking regions with this feature :)
I'll try to add the i18n in the next few days to bxe 1.1. Then, I would
be more than happy if people could help out finding all the strings in
BXE and replace them with the appropriate i18n calls. And of course,
providing translations .
So thanks a lot, good to see bugging you about some feature does help
indeed :)
You were not the only one ;)
chregu
Regards,
Hannes
--
christian stocker | Bitflux GmbH | schoeneggstrasse 5 | ch-8004 zurich
phone +41 1 240 56 70 | mobile +41 76 561 88 60 | fax +41 1 240 56 71
http://www.bitflux.ch | chregu@xxxxxxxxxx | gnupg-keyid 0x5CE1DECB
--
bx-editor-dev mailing list
bx-editor-dev@xxxxxxxxxxxxxxxx
http://lists.bitflux.ch/cgi-bin/listinfo/bx-editor-dev
|
