What's the best way to use the sitemap infrastructure for a site where only some of the pages are available in a different language (translated pages) or where you have a number of pages in a different language (not translated, just different pages)?

Example pages in default language

• Home
• Services
• Service A
• Service B
• Service C
  
• Jobs
•  About us
• Our philosophy

• Services
• Service A
• Service B
• About us
• Our philosophy
  

So here the secondary language has no homepage, no jobs (jobs are only for natives) and service C is not relevant. The masterpage contains a menu that will show only one structure. You can switch by clicking a button (so the secondary language is not a submenu).

You'd need to always see the correct menu, be able to bookmark pages and see the correct language and menu and you can see only pages available in your language in the menu, except for some general pages (like search).

This has been a big challenge and I cannot find a good solution. Here's some problems I encountered. If you use a resource file for the titles in a sitemap, you will still see nodes that are not translated to your language (you see them in the original language). You need to be able to bookmark any page and see it in the correct language and see the correct menu (so the language shown can not be based on a session variable for instance). Search page can only occur once in the sitemap file, but when you're there, you need to see the menu in your language (this means splitting the sitemap at the second level is no good solution, because where would you put the search page?)

Can some of you share some experience? Thank you!
 

Have you looked into using two separate SiteMaps - one for each language? 

Yes, definitely! Here's some problems with that approach:

1. How to determine the sitemap to be used, and how or when to switch?
2. Bookmarking a page in one language (not the default language) and visiting this page later.
3. How to avoid listing pages more than once (like search or sitemap), because imho doing things more than once is a waste.

random0xff:

Yes, definitely! Here's some problems with that approach:

1. How to determine the sitemap to be used, and how or when to switch?
2. Bookmarking a page in one language (not the default language) and visiting this page later.
3. How to avoid listing pages more than once (like search or sitemap), because imho doing things more than once is a waste.

Any tips?

A couple solutions for your problems listed above: 

1. The language and sitemap could be determined through a splash page. Here's an example (http://strategis.gc.ca/) where you choose either Fench or English.
   
2. Use a query string delimiter (or even url rewriting) to identify the correct language and load the correct content. This article Creating multilingual websites - Part 1 outlines this method.
3. I'm not sure what you mean. I would use Resource Files for the page content and load it based on the current language. See the article listed above.