Le 28/01/11 11:23, Nino Novak a écrit : Hi Nino,
> > on the German project we had the discussion about using Translation Tabs > at all. > Guess I wasn't following the German lists closely enough, but I've noticed they tend to get bogged down in rather long discussions so I tend to skip ;-) > Problems we encountered: > > - if using Translation Tab, you get a translated page inside of the > original domain Yes. > > - 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. Ah, I hadn't encountered that problem yet. I did notice though, that I couldn't set the Related tab status to point to the original language document. > > - 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. Yes I realised that aftewards, but I thought Silverstripe was designed to be able to handle this ? > > 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. OMG, well then I would have to ask what the point of having a Translation tab is ? After all, if it is unusable, better to deactivate it and force people to have two browser pages open at the same time, one with the original and one with the ongoing translation of the original. IMHO, that is one hell of a drop down in usability though. > > 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. Redirects would be acceptable. If they work properly. Still leaves the problem of keeping up to date with changes in the original. > > 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"). > Is it just me or are there some major limitations here ? Yes, I still believe in having a language specific subproject, but failing input from contributors, or just even for the sake of having homogenous information between the subprojects, the linked translation functionality would have been really, really, useful. Alex -- 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 ***
