From: J M C. E. <jm...@ar...> - 2006-09-15 11:10:49
|
Alexander Limi wrote: > just saying that you're trying to use LinguaPlone for something it has > not been designed to do :) Yes, that already seemed clear :) But for a few sites we're currently deploying (and lacking time/resources to prepare a full alternative where fallback would be more natural) changing a few content listing interfaces to also show 'content which has not been translated to the current language' still seems a "lesser evil" (even if it ends up requiring ugly internal hacks) when compared to the trick of faking language-neutrality in multiple-language folders (such as i18nfolder): people editing content will still be able to take advantage of LP, simply learning how to manage content in the "LinguaPlone way" without a kludgy additional rule like "remember to leave untranslated documents as language-neutral!". In any case, even genuine language-neutral objects, although not rejected by the "LinguaPlone way", seem a bit hard to fully reconcile with it: a hack similar to the one I intended for fallback seems necessary to properly support language-neutral objects contained in non-language-neutral folders, making them visible in navigation trees and (public) folder content listings under all translations of their container folder [1]. This may well be expected by end users/readers (even if, for consistency with the "LP way", and lacking something like a symbolic link, the object is only seen in a single 'real' place when using content admin listings/webdav/ftp). Best regards J Esteves [1] Not trouble-free of course: one immediately has to face the possibility of annoying id collisions with objects in the other, translated, folders, so the nav link could not in general point to a "ghost object" with a similar id in the other folder; it would have instead to point to the 'real' language-neutral object in its original container folder, whatever its language. And so on. Nasty stuff... -- +351 939838775 Skype:jmcerqueira http://del.icio.us/jmce |