Hello Henri,
> Ok, good point. However, another option here would be to
> support both methods. If MidgardMultiLang is set on in
> httpd.conf (maybe it would be more intuitive to configure
> this in Midgard's Host table instead?), the Midgard would
> use the /LC/page URIs, otherwise the $midgard->locale
> could be manipulated in the PHP end.
> Would this approach cause problems with implementation?
I think no. At least I don't see big ones except multilingual sites
somewhere nn path (e.g. www.somedomain.com/path/LC/...) where we need
be careful about /path/ before /LC/, but this situation could be
controlled by Midgard-lib (when script calls mgd_get_host(), this
function should check whether requested site runs multilingual and
automatically append /LC to 'prefix' field).
In result, two approaches could be united and go into core library.
But I think that we'll have this in 2.0 because it also required
locale support at DB level (as suggested before by Carmelo). Then
mgd_get_article(), mgd_get_topic(), mgd_get_custom() will return
corresponding record relying not only on passed ID but on
$midgard->locale setting (or failing to default locale if not found
$midgard->value).
Best regards,
Alexander mailto:[EMAIL PROTECTED]
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
