We have just migrated to Onesky, and imported a lot of source phrases and translations from a legacy solution in order to start using Onesky and are realising some of the quality issues we have now that we have started using glossaries, character lengths, etc. Also keep finding texts where whitespace and placeholders and such don't match up.
Unfortunately, Onesky doesn't make it easy for us to find these issues in our existing translations. This would be really helpful for pinpoint what strings might need to be re-translated. My suggestions (any of these will make my life a lot easier):
- Highlighting phrases that do not adhere to source formatting (whitespace, linebreaks, placeholders, maybe even character count) in a similar way to "Needs revising".
- Ability to filter to phrases in a language that do not contain required glossary terms (i.e. where the glossary term, in our case, has been wrongly translated)
- More accurately displaying whitespace characters (line breaks, etc). Onesky does not differnentiate for us when a \n has been used and where the return character has been used, for example, because our existing translations were imported from Excel.
Please sign in to leave a comment.