Should I start to build my site already in 0.9.7

I know, but I need One document and many language versions for it. For example: multilingual pictures gallery (I think it is not right to upload up to 100 photos for every langauge) any ideas?

Yes, thanks  . Could you explain, how can I do the same thing for the MaxiGallery snippet (title and description fields)? I need to show different language versions for every image in gallery, but I don’t want to have a lot of copies of one image.

And how can I hide predefined (content, pagetitle, ect ) fields from admin interface and show only TVs (for simple and friendlly user-interface)

I did this for a billingual (English/Spanish) website with hundreds of images in many galleries. I added Spanish Title and Spanish Description fields to the database tables and hacked those into the MaxiGallery snippet. Then I just manage the galleries from the English side of the site but display them on both sides (MG has a parameter for displaying a gallery created on another document).

Thank U very much. I’ll try it

Quote from: beast_drc at Mar 01, 2008, 08:35 AM

I know, but I need One document and many language versions for it. For example: multilingual pictures gallery (I think it is not right to upload up to 100 photos for every langauge) any ideas?

Internationalization features in the future MODx may help you setup translation workflow, or divide sections of the site into logical language sections that override system settings, or allow you to write a component that renders different content based on user preferences, but it’s not going to provide you one document with many language versions of each content piece (i.e. document content, TV’s, chunks, etc.). Today’s i18n standards reject that approach and instead recommend that you provide unique URI’s for each document targeted at a specific language; support for getting users to the right page is the problem to solve.

There are times when you want multi-lingual content to render at the same time at the same URI, and that’s a different problem (a single page with unique content areas being shown in various languages), and you are welcome to come up with solutions that use a one page/many languages approach to solving a multi-lingual site requirement, but I don’t think i18n features in MODx are going to be one document/many languages out of the box the way you are thinking.

I’ve a few custom apps that need to have all language users going to one page. I have that document outside of the main language groups (hidden from the main menu system in an unpublished folder), and have the snippets involved use external language files, with placeholders for the content.

The language cookie keeps the user in his own language group as he moves in and out of the main areas; all links are generated using the language cookie value, which is simply the document ID of the main language group’s folder originally selected by the user.