Ah, I see what you're running into! Microsoft's Translator glossaries do support phrase replacements, but they can be a bit finicky. A few things to check:
Formatting Issues in the TSV
- Make sure your TSV file is truly tab-separated (some text editors might insert spaces instead).
- Try opening the file in a plain text editor and ensure there’s exactly one tab between the source phrase and the replacement.
Case Sensitivity
- Microsoft's system can be case-sensitive sometimes. Try making your phrase replacements all lowercase and test again.
Phrase Boundaries
- Glossary replacements work best when the phrase appears as a standalone unit. If "Phrase To Replace" is embedded in a longer sentence, it might not trigger correctly.
Encoding
- Save the TSV file as UTF-8 without BOM if you haven't already. Some tools default to other encodings that might mess with how Translator reads it.
Quotes Don’t Matter
- You were right to test with and without quotes, but normally, quotes shouldn't be needed in the TSV.
Re-upload & Clear Cache
- Try re-uploading the glossary and restarting the app just in case it's caching an older version.
If none of that works, I’d test the same phrase with a simpler structure (just "test phrase" → "replacement") to see if it’s an issue with how Translator handles multi-word phrases in general.