On Friday 28 January 2011 06:43, Alexander Thurgood wrote: > ... driving me nuts ...
Alex, on the German project we had the discussion about using Translation Tabs at all. Problems we encountered: - if using Translation Tab, you get a translated page inside of the original domain - if including this translated page (as SubsiteVirtualPage) into your national domain, you have 2 instances of the same page. Relative links do not work anymore from the included page. So you have to always use absolute links in such pages, which brings the problem that they are not updated automatically by the CMS. - the original page tree navigation entries might follow a different logic than your national, but you cannot change navi entries in the translated page (only in the included). So you end up with two different Navigation structures in both instances. As the latter was a usability NOGO, we ended up in setting up all pages in our own national space. Thereby we lose the translation hints on every single page. As translated pages and national pages have a n:m relation, the only possibility (I don't know if this can be implemented) I see is to set up translation pages as Redirects to corresponding national pages and vice versa, but there seems to be no support for this in the CMS, so doing all this manually is not manageable. So we ended up with a completely national page tree. A prominent link to translations might be a good idea, though (in www there is a 1st level navi entry pointing to "International Sites"). Nino -- Unsubscribe instructions: E-mail to [email protected] List archive: http://listarchives.libreoffice.org/www/website/ *** All posts to this list are publicly archived for eternity ***
