Pierre M. wrote:
Hello DeMZed and all,
I hope I understand you well.
Assuming
-you are thinking about the multilang implementation for CMSms,
-you are noting monolanguage is hardcoded today (only one content flavor, stored in one column),
-you would like each content to be tagged by language and allow every content to be available in any number of languages (allowed by storage in rows),
then I'm happy a nice multilanguage implementation is at least
being designed. Good work
Pierre M.
You assume well and thanks for the link
After several hours, it seems that multilanguage hard coding is very implented in the code...
RonnyK has certanily understood this before me, and thus, his solution is the cheapest.
Pierre M. wrote:
I would like CMSms to be multilingual (you can search for my commitment to this in these forums). This is why I like what katon and jsmonzani have made so far. I'd like to stress the "single negociated tree" design pattern because I think it is best of all worlds :
-Pretty URLs aren't touched. You still make the rewriting you want and have the URL you want.
-TCN is automatic and user friendly (and your browser is allready configured for it - all browsers, in fact).
-Universality : no need for cookie hacking, just actual HTTP headers.
-It keeps CMSms simplicity : the templates are not modified. CMSms just serves the requested flavour of the same content bloc. In the admin, we can add as many flavours as we like, just tagging them with "en", "fr", "es", "it", "de", "ru"...
-As it is HTTP implemented, it is webserver cache friendly.
I'd like it be done the web way, the simple way, the CMSms way.
It's a great idea, that my way of think ...
Pierre M. wrote:katon once began the work. Now jsmonzani has made steps to resurect it. I'm respectfully suggesting to work with the devs at the core level rather than at the templating hack level. I wish fun coding days to all people involved.
Yeah, sure, but time is money even in Open Source world ! That's why, like others, I try to quickly do this...
But even if I master PHP, breaking down CMSMS to input multilanguage support is an long and entire task which needs perfect knowing of the application...
I mean : hacking CMS MS to introduce "single negociated tree" and all the good design rules we like, it hurts too much CMS design to be kept as a hack : it MUST be a coordinate task, not done with a Lucky-Luke-Lonesome-Developper style !
