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.
Hey Jake....
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