too many template for multilanguage?

[pumuklee]

hi

if i have a site structure somethisng like this:
english
--e1
--e2
german
--g1
--g2
french
--f1
--f2

and the basic templates are the same for german english and french
but in cmsms
it meens that i need also other template for this languages because the menu? where i must to specify to put just the german or english menu on the page...
and this i must insert directly in the template
something like this
{menu startpage...level...}

any ideea?how can i handle this with the same template?

thanks

[Basss]

A trick I once used:

At the first level put the homepages per language
Put your English pages under the English homepage, The Ger under Ger and so on.

Like this:

Eng----E1
      |--E2---E21
      |      |--E22
      |      |--E23-----E231
      |      |         |--E232
      |      |--E24
      |      |--E25
      |--E3

Ger----G1
      |--G2
      |--G3

Fra----F1
      |--F2
      |--F3

There's an option in CMSMS to use multiple menus, starting at varying levels and depths.
For example a horizontal menu bar for the first level, only one deep.
Put in a vertical menu left or right, starting at the second level (so not showing the language page)

That would result in this on the page:


__CMS____________________________________________________________Eng__Ger__Fra__

Eng----E1
      |--E2---E21
      |      |--E22
      |      |--E23-----E231
      |      |         |--E232
      |      |--E24
      |      |--E25
      |--E3

It works - even with Russian

On the other hand,
One could think of tinkering the sniplets, metas and headings to different languages.
This in the end would mean multiple language specific page layouts.

But then again ... the menu works.

[pumuklee]

yes you has right

but the question is
i need to make separate template for german english...
because i must insert the menu code in the template
so that for example
in german template comes:

{menu startpage=german level...}

in english:
{menu start_element=english level...}

...
how can i handle this with one template?
so that the start_element must come dinamically