Why do you need to use the "/"...? Why can't you just use an underscore, "_".

Example:

database.nsf/pages/en_about?opendocument

database.nsf/pages/de_about?opendocument

This way you don't have to use the "?opendocument". Could use ".html".

Example:

database.nsf/pages/en_about.html

database.nsf/pages/de_about.html

Another thing that you can do is to use a multi-value field for the index. This field will store the language names for the document. (e.g. en_about.html; de_about.html). All you need to do is to get the view to display it as seperate entries!

You can then:

1) Use 1 document to store all the languages. Then use 1 form to display the different language in the document (i.e. The URL path will hold the language!)

OR

2) Use your seperate documents in the view. Then use 1 form to display the document.

Hope that helps

Patrick Niland

Considered folders ?

Mark

There's a reason I don't want to use the query string. It's essential for this site that Google indexes it properly. For this reason I want avoid anything after the ? as much as I can. It's generally thought that Google doesn't like pages with Query strings as it thinks they are dynamic and not worth indexing.

{Link}

Why not just use the query string?

(e.g. ?opendocument&lang=en )

Works perfect!

You have to use one document to store all languages. This is useful to manage content for your site, as you can require the user to enter all languages for the document.

Also, you can put error recovery in the documents if you want. (i.e. If a document only has an English version and the user is navigating in French, then you can display the English version).

Ok, so the form to display this will have to do a bit of computation, but your website will always have the correct amount of webpages, although not all languages! (i.e. What if your site navigation links to a language document that the user has not created???)

You should try these links (NOTE: Built this website about 3 years ago... Uses the same mechanism above).

{Link}

{Link}

{Link}

{Link}

Later

Patrick

database.nsf/pages/about.en

database.nsf/pages/about.de

No slash - no stress ;)

Create two columns:

Column 1: Categorised by language.

Column 2: Sorted by Title.

You might need to make sure the view's "Collapse all .. " setting isn't enabled - it depends on the situation.

Perhaps there's something else causing the problem.

What you could do is render the english and the other languages all on one page and hide DIVs depending on the browser language info. I do this with:

{Link}

A javascript detects the browserlanguage and loads the appropriate style sheet which only displays the right language. Advantages:

- simpler structure of your website for maintenance

- better indexing by Google

- all languages of one page can be edited in one form

- easy switch of users between languages on the same page