Documentation tasks

by Alex Limi — last modified Jul 06, 2007 02:59 PM
These things need to be documented for LinguaPlone 2.0.
  • Content Policies
    • Fully translated (filters, aims to be complete)
    • Partially translated (filtering, but does not aim to be complete)
    • "Press Release" translations (no filtering)
  • Current major problems
    • Default page translation (needs to translate the folder + the default page)
    • Neutral folders/content - don't work when not in root (new index?)
    • Keeping UI and content languages in sync
    • Permissions of translations/canonical must not affect the other content (essentially, when things look for its translations, it does not have the permission, and the document is unusable)
  • Features
    • Select what is the global canonical language (this content will be the only stuff that gets the translate link)
    • Show non-existent translations or not
    • Lock the UI language (cut/paste use case, only for logged-in, personal prefs)
    • Allow any language (press release use case)
    • Remove left/right columns when translating (more space for split screen)
    • Support reassigning which document is the canonical
    • Manually assign what content is a translation of another
    • Proxy objects (for partially translated sites) - if you have content without body text, it references the canonical object if that has body text
    • Annotate the translationOf reference with the revision number of the canonical doc now that we have versioning
    • When canonical content is changed, produce a diff, mail the translator (maybe also a mailing list pref in the central config)
    • Unfinished translations portlet