Your SlideShare is downloading. ×
Manage Multilingual Sites
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Manage Multilingual Sites

2,137
views

Published on

Usecase and pitfalls with managing multilingual sites and what tools and solutions there is for Plone.

Usecase and pitfalls with managing multilingual sites and what tools and solutions there is for Plone.

Published in: Technology, Business

0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,137
On Slideshare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
28
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
  • 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
  • Transcript

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

    ×