Low Quality Output: What to Do
If your results don't meet expectations, here's how to diagnose and address the issue.
Translation Quality Issues
Symptoms
- Awkward phrasing or "translationese"
- Inconsistent character names or terminology
- Missing sections or incomplete translation
- Formatting issues
Common Causes and Solutions
Source File Quality
Problem: Poorly formatted source files produce lower quality output.
Solutions:
- Use EPUB format when possible (best structure preservation)
- Remove headers/footers from DOCX files
- Ensure chapter breaks are clear
- Fix major typos in the original before translating
Very Long or Complex Books
Problem: Extremely long books may have consistency issues.
Solutions:
- The system builds a continuity guide, but very complex books benefit from review
- Use the Proofreading for Translations mode after translation
- Check the DOCX output and make manual edits as needed
Genre-Specific Content
Problem: Some genres have specialized terminology or style needs.
Solutions:
- Fantasy, sci-fi, and historical fiction are fully supported
- Very technical content may need manual review
- The system handles explicit content appropriately
What to Expect
- Multiple refinement passes during translation
- A consistency guide built from your manuscript
- Full refund if a translation job fails to complete
If Quality Is Genuinely Poor
- Download the DOCX and review specific issues
- Note the problems (specific passages, consistency issues)
- Contact support with:
- Job ID or book title
- Specific examples of problems
- Source file if different from what was submitted
Options may include:
- Re-translation at no cost
- Credit refund
- Manual review and correction
Proofreading Quality Issues
Symptoms
- Changes that don't improve the text
- Missing obvious errors
- Over-correction of intentional style choices
Common Causes and Solutions
Wrong Mode Selected
Problem: Using Standard mode for a translated manuscript.
Solution:
- Use Translation mode for translated texts
- It checks for translation-specific issues
Style Preferences
Problem: Proofreader "corrects" intentional stylistic choices.
Solution:
- This is expected—proofreaders flag potential issues
- Use tracked changes to accept or reject each suggestion
- The proofreader doesn't know your intentional style breaks
Continuity Not Enabled
Problem: Character or plot inconsistencies missed.
Solution:
- Enable Continuity Check for consistency analysis
- Particularly important for long novels or series
If Output Is Unusable
- Review the tracked changes - Some suggestions may be valid
- Contact support with specific examples
- Bookshift may offer re-processing or credit adjustment
Cover Quality Issues
Symptoms
- Text placement doesn't match original
- Font or style differs significantly
- Image quality degradation
- Design elements lost
Common Causes and Solutions
Low Resolution Source
Problem: Uploading a small or compressed image.
Solution:
- Always upload the highest resolution available
- Re-export from original design files
Complex Design
Problem: Very intricate designs may not translate perfectly.
Solution:
- Simpler designs translate better
- Consider using cover generation for a fresh approach
- Minor touch-ups in image editing software may be needed
Explicit Content Moderation
Problem: Cover rejected due to content.
Solution:
- Use cover generation instead
- Generation can create appropriate covers for any genre
If Output Is Unusable
- Try generation instead of translation
- Contact support if you believe there was a technical error
- Regenerate with different style hints
Transcription Quality Issues
Symptoms
- Many transcription errors
- Character names misspelled
- Missing words or sections
- Poor formatting
Common Causes and Solutions
Audio Quality
Problem: Background noise, poor recording quality, or unclear speech.
Solutions:
- Record in quiet environments
- Use a quality microphone
- Speak clearly and at consistent volume
Unusual Names or Terms
Problem: AI doesn't know your character names.
Solution:
- Add names to your project glossary before transcription
- Define preferred spellings
Very Long Recordings
Problem: Quality degrades on long sessions.
Solution:
- Use chunked mode for recordings over 30 minutes
- Break long dictation into multiple files
If Output Is Unusable
- Transcription has no automatic refunds due to variable audio quality
- Contact support if you believe there was a processing error
- Improving audio quality usually resolves issues
When to Contact Support
Always Contact Support If:
- A job fails to complete (you're entitled to a refund)
- Output is genuinely unusable due to technical issues
- You see error messages you don't understand
- Credits were deducted but you received no output
How to Contact Support
- Go to your Dashboard
- Click Messages or Contact Support
- Include:
- Job ID or book/file name
- Description of the issue
- Specific examples if possible
- What you expected vs. what you received
Response Time
- Typically within 24 hours on business days
- Faster for urgent issues (failed jobs, billing problems)
What Support May Offer
- Re-processing at no cost
- Credit refund or adjustment
- Technical guidance
- Escalation to development team for bugs