This site uses cookies.
Some of these cookies are essential to the operation of the site,
while others help to improve your experience by providing insights into how the site is being used.
For more information, please see the ProZ.com privacy policy.
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Michael Beijer United Kingdom Local time: 17:55 Member Dutch to English + ...
not yet 100% resolved
Nov 4, 2013
Hi benk,
Looks like the issue is not yet 100% resolved, as there might be reasons (mentioned by Stanislav Okhvat, the developer of Translator Tools) why using U+02BC instead of U+2019 might not be a good idea.
The issue is currently being debated in the memoQ mailing list,... See more
Hi benk,
Looks like the issue is not yet 100% resolved, as there might be reasons (mentioned by Stanislav Okhvat, the developer of Translator Tools) why using U+02BC instead of U+2019 might not be a good idea.
The contents of this post will automatically be included in the ticket generated. Please add any additional comments or explanation (optional)
Michael Beijer United Kingdom Local time: 17:55 Member Dutch to English + ...
not solved yet!
Nov 5, 2013
Oh oh, looks like this won't work after all. I just read this on the memoQ mailing list:
Max B.Today at 4:10 PM
View Source
El 05/11/2013 11:48, michael@... escribió:
> In conclusion, I think that Kilgray may want to correct the issue by
> changing the curly version of the character that automatically
> replaces the straight version to U+02BC from the current U+2019.
> However, I am n... See more
Oh oh, looks like this won't work after all. I just read this on the memoQ mailing list:
Max B.Today at 4:10 PM
View Source
El 05/11/2013 11:48, michael@... escribió:
> In conclusion, I think that Kilgray may want to correct the issue by
> changing the curly version of the character that automatically
> replaces the straight version to U+02BC from the current U+2019.
> However, I am not aware if this may create backwards-compatibility
> problems or other issues due to the fact that it's Unicode-only. I
> have systematically replaced the characters in a series of projects
> and I had no problems with the exported files in a limited series of
> trials with Word and Studio documents.
I tried using U+02BC instead of U+2019.
In memoQ, I see a square with a question mark, probably because my font
does not have this character.
The exported Word file looks OK, but there are problems with
spellchecking software:
• The Word spellchecker puts curly waves under each word with U+02BC.
• The Antidote grammar checker treats U+2019 as if it were no there at all.
If I sent out such a file to a client, she would probably wonder what is
happening.
Manage your TMs and Terms ... and boost your translation business
Are you ready for something fresh in the industry? TM-Town is a unique new site for you -- the freelance translator -- to store, manage and share translation memories (TMs) and glossaries...and potentially meet new clients on the basis of your prior work.
Pastey is an innovative desktop application that bridges the gap between human expertise and artificial intelligence. With intuitive keyboard shortcuts, Pastey transforms your source text into AI-powered draft translations.