Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
[wiki] Assignment: Multilingual Publishing
This could be cross-referenced in Feature Requests or Plugins, but since I’m really proposing a bit of planning on the subject, here, if it’s ever to make it into core, I figure Docs is a good place. So, the point then, is to invite minds to the planning effort of what should be one of the most important abilities of Textpattern — the ability to easily publish content in more than one language.
This is likely going to mean different things to different people, which is why the planning spot in TextBook is proposed. Feel free to share your thoughts here as well.
Consider the following exchange between Sencer and I as for food for thought:
<strong>S:</strong> To varying languages in the admin/public side, it’s really only 1-2 lines of PHP to load another language file and one can easily write a plugin to embed the code in templates.
<strong>D:</strong> Just need a little clarification…Do you mean to imply this 1-2 lines would allow a team of international authors for a given site to see the admin side in their own languages (respective to the individual), like what is talked of here.
<strong>S:</strong> That is one possibility. It’s also just as easy to put a few lines in templates or forms that will load the respective language (though for consistency it’s probably best to do this before any language-strings are placed/called
in the templates). Then language could be dependent on forms, urls, sections etc.
<strong>D:</strong> …or are you suggesting something more significant, where a given author can easily choose (say from a dropdown list) from two or more actively installed languages in which a particular article is to be drafted and published. If the latter, holy-smokes, that’s huge. I’ll have my two lines of code please. ;)
<strong>S:</strong> We can’t quite do magic yet. ;) Of course choosing a section/category or form-override might do some of what you need. The question is always: which concrete behaviour/results should be changed in which circumstances.
Consider this: <code><txp:php>$GLOBALS[‘textarray’]=load_lang(‘en-gb’);</txp:php></code>. This will load a language of your liking. Imagine some conditionals or a smart plugin around that, and you can see that already some interesting things are possible with little effort.
…
Huzzah!
So folks, what could be some interesting things, and how should it work? Let’s dream big first, and then get realistic as we find we need to.
Offline