CafeTran

> neural Machine Translation algorithms (e.g. Google Translate and DeepL), which are heuristic by their nature

Well, I do human translation. And maybe this is why a text pretranslated with fuzzies or MT alone does not make a good job.

> there is far less work spotting any 3-letter upper-case spelling mistakes, not to mention low probability of making them, than adding such words to user's spell checker dictionary

Indeed this is a good example for heuristics, but it is far from being reality for the daily routine.

> but I don't remember seeing a spelling error in 3-letter upper case words in real texts

Maybe this was before texts were translated with the latest CafeTran feature. As written above, you sacrifice a basic feature for most users against a comfort feature for very few users. What a pity.

Agree entirely with tre, etc. – having this non-configurable and on by default is a disaster waiting to happen.

"you sacrifice a basic feature for most users against a comfort feature for very few users" is exactly right. It's not just another odd design choice, it's utterly stupid.

About Task > List words with unknown spelling, I like the easy way to add these to the user dictionary, but miss a way to easily copy / list in text mode and/or quickly filter target segments.

Reasoning for the last one (filtering target segments, which, to be fair, can be achieved by just providing  an easy copy text feature): Sometimes, I wish to review the unknown spelling in context before deciding what to do.

Maybe an Edit user's spelling dictionary button (along with one  to open unknown words list in text mode?) could make sense here.

---

About the 3-letter upper case rule, I don't have an opinion, for now at least.

You are right, it does. When an in-context review of the unknown spellings is needed, I'll take that route instead. Thanks!

> Doesn't QA > Check spelling in targets segments do the job?

No. The 'List words with unknown spelling' works much faster, as it shows errors only once (very handy e.g. in case of names or words with many occurrences and that you do not want to retain in any list - just imagine a text with 10 K words and 100 occurrences of such a name or a given term) and side by side (e.g. to find a wrongly spelled name). Unfortunately this feature is actually broken.

> Sometimes, I wish to review the unknown spelling in context before deciding what to do.

List words with unknown spelling > mark word > Search with Strg-F3

Unfortunately, when marking the word sometimes the paragraph mark is being copied as a kind of character into the search bar, so that the search returns no results (this has already been reported longer ago)

Hard work to convince you, though you should take "he won't do such a stupid thing" as a compliment.

The fact that we users of a software program can have direct interaction with its developer, is a rare and  great feature.

Yes, right.

Next issue: The buttons in the "List words with unknown spelling" tab

This is the look on Mac (with the new update they are visible now)

• the list view should be kept (else it is "Show words with unknown spelling")
  
• this kind of view is quite confusing 
  
• the words are longer than the buttons (not very helpful for spelling errors), even when only having < 20 letters
  
• perhaps the design should be adapted to the frequent words list* (a more consistent GUI also means a simpler GUI)
  
• anyway, external buttons would leave the possibility to put in more features: "find"/"filter"/"filter with context" (hello Jean!) etc.
  
• the possibility of consult the list and filter with one keystroke (in the simple sense of "where is this?") has gone …

> CTRL key + click to search the misspelled word in target segments.

It works really nice, thanks!

> - Saving notes in external .xliff or .xlf files that follow XLIFF 1.2 specification. 

I just finished a MemoQ project, and was about to create a post entry because it seems Notes cannot be removed in MemoQ packages (and probably mqxliff files as well) via the Task > Remove notes.

I've tested with the new build first (since the announcement states Notes have been tweaked on some xliff types), but I can confirm CT still won't remove Notes on MemoQ projects via the Task menu. I can tell you, it's a pain when you have to rinse and repeat 77 times...

I've also noticed the Pink notes background has been replaced by a Green one. Nice touch!

Where do I change the color background for the glossary pane for shade alternate rows? I'll try to use this green color there as well. :-)

Jean

… and there is no button to undo a click (that with this configuration might happen faster) …

• maybe instead of graying out, a green dot or asterisc could be placed (without getting up hope that a kind of list returns)
  
• independent from the further ado, a quicklink (floating at the top or the bottom of the right side) to the user dic would be fine (e.g. for undoing, searching etc.))
  

Many thanks! Matchboard and glossary background colours too have changed, right? It's better now.