1
cjarolim
Re: Discussion: How best to make CONTENT multilingual
  • 2003/11/5 10:43

  • cjarolim

  • Just popping in

  • Posts: 3

  • Since: 2003/6/2 5


Hi svaha,

thanks for the snippet.

Looks cool and If I may I'd be happy to use your code in one of my upcoming projects, too.

I also will have to consider, how to support more than one editors (i.e., for each language one, maybe for each topic another one). They should be prompted automaticly, when there is a change in a language to adapt it to their's. And some 'editor in chief' function should be there, too. Mixing a project management tool with an CVS and XOOPS... But this might get a bit too complicated from where we are now.


Thanks anyways!



Christian Jarolim
--
//jarolim.com
//The Label on Line



2
cjarolim
Re: Discussion: How best to make CONTENT multilingual
  • 2003/11/5 10:31

  • cjarolim

  • Just popping in

  • Posts: 3

  • Since: 2003/6/2 5


Quote:
I'd prefer a spacial (admin) module, where the languages a user - with translation rights - has selected are listed. On this page there should beclear indications about what contens is available, and what needs to be translated. Some sort of tree-structure would probably be usefull.


Hmmm...
Good point, right.

have to think about this. At the Heffterhof Website (that's the site I've mentioned) there is just one person in chief of editing content, the community-functionality was turned off (but will become active again, as soon as the customer's got all of his content on line). That makes things quite easy....

Cheers! Christian Jarolim



3
cjarolim
Re: Discussion: How best to make CONTENT multilingual
  • 2003/11/3 13:01

  • cjarolim

  • Just popping in

  • Posts: 3

  • Since: 2003/6/2 5


Thanks for starting this discussion! I just launched a xoops-site (old but quite stable / version 1.3) with more than 1 language and found it quite hard to do that without
1) having too much to do (grin) with setup and administration
2) confusing my customer
3) being able to upgrade XOOPS if wanted

So I set up three independend XOOPS installations (german, english, and - not yet translated, approved, and linked, but on line - italian)

This is no solution for the question you asked above, but it was the quickliest way to make three out of one (the german version was there for about half a year before the customer wanted more...)

Following the conversation, I'd prefer a strict separation of languages in the database. Even with two languages, only, the content-administration with this bracket based solution might become a bit confusing for those who do this task not on a regular base.

But: How about adapting the storyform.inc (...and related, of course) in the news/admin folder to prompt one language-version of the form after the other when one updates a text?

It would be quite clear, what happens next, no customer would have to mess with the brackets and my lazy me would get a quite easy to set up and maintain multilingual website...

Cheers!


Christian Jarolim
mailto:christian@jarolim.com




TopTop



Login

Who's Online

218 user(s) are online (139 user(s) are browsing Support Forums)


Members: 0


Guests: 218


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits