SDL Trados Studio
SDL Trados GroupShare
SDL Trados Business Manager
SDL Trados Live
SDL Speech to Text
SDL Managed Translation - Enterprise
Translation Management Connectors
SDL LiveContent S1000D
SDL Contenta S1000D
SDL Tridion Docs
SDL Tridion Sites
SDL Content Assistant
SDL Machine Translation Cloud
SDL Machine Translation Connectors
SDL Machine Translation Edge
Tridion Docs Developers
SDL User Experience
Language Products - GCS Internal Community
SDL Community Internal Group
SDL Access Customer Portal
SDL Professional Services
SDL Training & Certification
Language Technology Partner Group
SDL Academic Partners
SDL Enterprise Technology Partners
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic SDL Tridion Docs User Group
SDL Tridion UK Meetup
SDL Tridion User Group New England
SDL Tridion West Coast User Group
SDL WorldServer User Group
Tridion Docs Europe & APAC User Group
Tridion User Group Benelux
Tridion User Group Ohio Valley
SDL MultiTerm Ideas
SDL Passolo Ideas
SDL Trados GroupShare Ideas
SDL Trados Studio Ideas
SDL Machine Translation Cloud Ideas
SDL Machine Translation Edge Ideas
SDL Language Cloud TMS Ideas
SDL Language Cloud Terminology Ideas
SDL Language Cloud Online Editor Ideas
SDL Managed Translation - Enterprise Ideas
SDL TMS Ideas
SDL WorldServer Ideas
SDL Tridion Docs Ideas
SDL Tridion Sites Ideas
SDL LiveContent S1000D Ideas
SDL Contenta S1000D
SDL XPP Ideas
Events & Webinars
To SDL Documentation
To SDL Support
What's New in SDL
Detecting language please wait for.......
Could you please point me to the best practise document/guidelines for encoding; I can't see to find one? For the encoding of the source content, we would always recommend have the "Scan" step as part of the workflow as this will correctly identify the correct encoding. For the encoding of the target content, you just need to make sure you have the correct setting in the configuration.
Why is the default encoding set to default (this name really doesn’t describe what it does), when the best practice is to apply UTF8 encoding?
Suggestion: Update default encoding to be UTF8, as per industry best practices.
Forgetting to change "Default" into "utf-8" on the Encoding page of a Config, very often leads to target HTML or XML files being converted from "utf-8" to "windows-1252", even if you have a SCAN stage in your workflow. And we get a lot of client complaints because of this. "Codepage" was the default encoding in the 1980's, before Unicode was invented, but we switched to a new millenium now!
Unfortunately I don't have any document to confirm that.
However I can say we all always set source and target encodings for all non-object file types to UTF-8.
This is a common practice and sometimes if forgotten it remains unnoticed until client gets back to us with complaints.
Therefore I also think it would be great if UTF-8 was set automatically instead of Default.
If for some reason someone would need different encoding (which would probably be 1% of all cases) then he'd manually change them.