Maxime Petazzoni wrote:
Hi,
Last week, we've been discussing what mod_mbox should output (XML+XSLT
or XHTML?) and we seemed to settle our minds on a simple XHTML output
for the interface, plus of course the XML backend for AJAX
sub-requests.
Still, someone on the #apache-modules IRC channel
There's no reason the strings have to be hard coded into the C code.
You can pull them out into some sort of language specific file, just
like any other C program that worries about i18n.
This would mean more file I/O every time mod_mbox runs, and maybe
using an external library such as
translations seems like
a bad idea.
* use variables for strings and a sub XSL defining this variables
depending on the language.
This is, at least in my mind, not going to be one bit faster than using
(cached) gettext.
FWIW, I'm not too worried about i18n and mod_mbox. It's only
, and having to push xsl changes to n translations seems like
a bad idea.
Absolutely. I know this, but I needed to present all solutions that
came to me.
FWIW, I'm not too worried about i18n and mod_mbox. It's only the
interface changing language anyway.
Of course, but if we want it, it would
