Recommandé
Recommandé
Contenu connexe
Similaire à Manage Multilingual Sites
Similaire à Manage Multilingual Sites (20)
Dernier
Dernier (20)
Manage Multilingual Sites
- 3. Managing multilingual sites by Sasha Vinčić Valentine Web Systems
- 4. Agenda Short history Pitfalls and use cases Tools and solutions
- 5. Around 2005 LinguaPlone made translations easy external translations with XLIFFMarshall (drag-n-drop)
- 6. Plone speaks and more
- 7. Localization vs Translation
- 8. Each language adds a new dimension Site structure Logic Content
- 11. Missing page
- 12. Missing page strategies first available parent not available in your language not show the link at all
- 13. Translating content translations inside Plone external translations
- 14. External translation XLIFFMarshall exports & imports in XLIFF External tools: Trados, MS Word
- 15. External translation pitfalls Translators - paid by word Links / Images Outdated content
- 16. Paid by word <a href=”” title=”Hello world” >Hello</a> <a href=”” titel=”Hej världen” >Hej</a>
- 17. Links / images links are not translated translation aware resolveUid - translates links mark links with language
- 18. marked links
- 19. Outdated original has changed after export valentine.linguaflow
- 20. valentine.linguaflow keeps track of translation related changes automatic/manual (in)validation of translations “export all invalid translations”
- 21. XLIFF management
- 26. More features valentine.linguaflow synchronize workflow state effective date expiration date local roles sync collection criterias (automatic)
- 27. More features
- 28. Language of the CMS Editors don’t know all languages The system is not content CMS langauge use one language member preferred language
- 29. More tips language specific search /en/search /sv/search language specific contact-info /sv/contact-info
- 31. h
- 32. Sasha Vinčić sasha.vincic at valentinewebsystems.se twitter.com/vincic valentinewebsystems.com/en twitter.com/valentineweb
Notes de l'éditeur
- 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&#x2019;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