• Like
  • Save

Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Manage multilingual sites

  • 1,344 views
Uploaded on

Managing multilingual sites - the caveats and the tips.

Managing multilingual sites - the caveats and the tips.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,344
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
3

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide






  • Plone has good and easy translation support for long time
  • Plone is translated in many languages


  • Site structure - no problem when fully translated
    Logic - if not fully translated, you need logic what to show
    Always avoid mixing languages
  • first available parent
    not available in your language
    not show the link at all
  • lingua plone language bar - hides when no translations
    larger websites you tend to show language selection all the time
  • one selection - pointing to the top of each language - bad
    one selection pointing to the first available parent
    not available in your language
    not show the link at all


  • inside plone is good for smaller websites
    external translations - good for larger websites and when there is professional translators who use own tools
  • XLIFF - XML standard
    XLIFF - XML Localization Interchange File Format
    Trados, one of the largest translation tools


  • In proper XLIFF the HTML is escaped.
    Anyone see why this translator got to much pay?
    Preserved HTML only shows content that should be translated.
    Preserved HTML is Tidy up before the export to be XHTML compliant.
  • Use resolveUid for internal content.
    Translation aware resolveuid will create the link to the translation.
  • Example of marked english link from swedish translation.




  • xliff translations form
    Export: select source language, recursive, only invalid translations, Preserve HTML, save export info
    Import: Select file, override target language since translators don’t change it Dump to .po file (developer feature)
    Synchronize workflow - same state on translation as on original.
  • Top linguaflow,
    nochange transitions
    link to the export
    bellow normal default workflow


  • Top contains information for estimating the budget. Wordcount, character count, pages.
    Title contains path source -> target language and time of export.
    Bellow contains information about the settings for this export and a button to rexport.
  • Top contains information for estimating the budget. Wordcount, character count, pages.
    Title contains path source -> target language and time of export.
    Bellow contains information about the settings for this export and a button to rexport.


  • custom manage translation form
    always synchronizing from original




  • slc.xliff exporter, one file per content and zip file.
    c.c.linguatarget - rules tom moving/copying translations when original is moved/copied








Transcript

  • 1. Managing multilingual sites
  • 2. Managing multilingual sites by Sasha Vinčić Valentine Web Systems
  • 3. Agenda Short history Pitfalls and use cases Tools and solutions
  • 4. Around 2005 LinguaPlone made translations easy external translations with XLIFFMarshall (drag-n-drop)
  • 5. Plone speaks and more
  • 6. Localization vs Translation
  • 7. Each language adds a new dimension Site structure Logic Content
  • 8. Site structure
  • 9. Translated structure
  • 10. Missing page
  • 11. Missing page strategies first available parent not available in your language not show the link at all
  • 12. Translating content translations inside Plone external translations
  • 13. External translation XLIFFMarshall exports & imports in XLIFF External tools: Trados, MS Word
  • 14. External translation pitfalls Translators - paid by word Links / Images Outdated content
  • 15. Paid by word <a href=”” title=”Hello world” >Hello</a> <a href=”” titel=”Hej världen” >Hej</a>
  • 16. Links / images links are not translated translation aware resolveUid - translates links mark links with language
  • 17. marked links
  • 18. Outdated original has changed after export valentine.linguaflow
  • 19. valentine.linguaflow keeps track of translation related changes automatic/manual (in)validation of translations “export all invalid translations”
  • 20. XLIFF management
  • 21. Multi workflow history
  • 22. Export information
  • 23. Export information
  • 24. Export information
  • 25. More features valentine.linguaflow synchronize workflow state effective date expiration date local roles sync collection criterias (automatic)
  • 26. More features
  • 27. Language of the CMS Editors don’t know all languages The system is not content CMS langauge use one language member preferred language
  • 28. More tips language specific search /en/search /sv/search language specific contact-info /sv/contact-info
  • 29. Other tools slc.xliff Syslab collective.contentrules.linguatarget eea.sitestructurediff
  • 30. eea.sitestructurediff
  • 31. code svn.plone.org/svn/collective/ Products.XLIFFMarshall svn.plone.org/svn/collective/ valentine.linguaflow svn.eionet.europa.eu/projects/Zope/ browser/trunk/eea.sitestructurediff
  • 32. http://valentinewebsystems.com/en/ sasha.vincic@valentinewebsystems.se twitter.com/vincic
  • 33. Managing multilingual sites