Best Practices

Overview

Following these best practices will help you get the best translation quality and make the most of Antinium's features.

Writing for Translation

Write Clearly

• Use simple, clear sentences
• Avoid idioms and cultural references that don't translate well
• Be consistent with terminology
• Use active voice when possible

Structure Your Content

• Use headings and subheadings to organize content
• Break long paragraphs into shorter ones
• Use lists for multiple items
• Keep formatting consistent

Translation Quality

Always Review

Even the best AI translations benefit from human review:

• Check for accuracy and completeness
• Verify technical terms are correct
• Ensure tone matches your brand voice
• Check formatting is preserved
• Verify proper nouns and names

Use Translation Memory

Enable translation memory for documents with repeated content:

• Maintains consistency across documents
• Speeds up translation of similar content
• Especially useful for technical documentation
• Review and update memory entries regularly

Choosing the Right Style

Select the appropriate localization style for your content:

• Formal: Business documents, legal content, official communications
• Casual: Blog posts, social media, informal content
• Marketing: Product descriptions, advertisements, promotional content
• Technical: User manuals, API docs, technical documentation
• Legal: Contracts, terms of service, legal documents

Collaboration

Use Comments Effectively

• Comment on specific text selections
• Use @mentions to notify team members
• Resolve comments when addressed
• Keep conversations focused and constructive

Set Appropriate Permissions

• Give people only the permissions they need
• Use Viewer for reviewers
• Use Editor for translators
• Reserve Admin for document owners

Organization

Use Folders

Organize documents into folders:

• Group related documents together
• Use clear, descriptive folder names
• Create folders by project, language, or department
• Share folders with appropriate team members

Naming Conventions

• Use descriptive document names
• Include version numbers if needed
• Indicate language in the name (e.g., "Product Guide - ES")
• Be consistent across your workspace

Performance Tips

• Translate in sections: For very long documents, translate section by section
• Use batch operations: Translate multiple documents at once when possible
• Review during translation: Don't wait until the end to review
• Save frequently: While auto-save is enabled, manually save important milestones

Security

• Control access: Only share documents with people who need access
• Use expiration dates: Set expiration dates on shareable links
• Review permissions: Regularly audit who has access to documents
• Protect sensitive content: Use password protection for confidential documents
• Be careful with public sharing: Only make documents public when necessary

Related Topics

• Workflow Examples - See real-world workflows
• Translation in the Editor - Translation features
• Translation Memory - Maintain consistency