Yes, I should have given a reason for this ‘odd’ sounding question:
Up to now I created a multilingual website by using the S4S RWML stack suite, which allows to create a page with multiple language ‘blocks’ with the appropriate ones being served ‘on the fly’ by a PHP script depending on the current language setting. This works well, but in combination with other blog stacks, sometimes other php scripts, and for proper SEO descriptions, one runs into limitations using the ‘one page’ approach.
The other (maybe more typical) way to serve multilingual sites is to provide individual pages for each language needed. Following this approach it is relatively easy to split the project up into individual languages, all working on subfolder structures and having their own properly translated menu structure. Long story short, this is where the ‘do nothing’ menu entry would come in handy. If the user is e.g. already in the ‘English’ context, then clicking on ‘English’ menu entry doesn’t have to do anything, whereas the other entries switch to the other language context. In e.g. the German context, the ‘English’ menu entry provided within this subproject indeed switch switches to ‘English’.
Each language sub project has its own page and menu structure, and the switching between languages happens via the language menu. Each language has one menu entry pointing towards itself - this is the entry where a ‘do nothing’ would be perfect ;)