CafeTran

...recognition of words with the curly apostrophe (instead of the typewriter/straight apostrophe) inside.

Igor, many thanks for implementing this. It works well, that is words like "dell'Olanda" with the curly apostrophe arn't labeled as spelling errors anymore.

But, I have a question: words such as "l'iPhone" (with the curly apostrofe) are still reckognized as errors. I thought that "iPhone" was the problem, so I either added it to the spell checker dictionary and to the non-translatable list, but to no avail. What's the best way to have the word "iPhone" ignored?

Thanks

While searching for a solution I found that non-translatables can be placed in normal glossaries and should be preceded by ! (if i'm not mistaken). This is what I did, but still they are labeled as spelling errors in the grid. Is this the right way to go?

> improved display of Task > List words with unknown spelling - see the buttons to add easily the listed words to user's spell-checker dictionary.

Yay, finally. The only issue is that they are invisible, at least under Mac.

> ignoring short (fewer than 4 characters in length) upper-case words.

OMG, undo this or make this optional. Ever thought of texts or segments in upper-case only? THERE CNA BE LOTS OPF ERRORS INSIDE, ADN CTT USERS WON'T BEA ABLE TO SPOT THEM NWO WITH TEH SPELL CHECKER. 

When putting more options into the spell check function, it might be a good idea to create a tab of its own in the Preferences and letting the selection to the users, and not to hard-code these features. One more argument: The show-up of spell check engines can only be monitored by plunging into the system, this in not convenient for most users (while I don't care).

>OMG, undo this or make this optional. Ever thought of texts or segments in upper-case only? THERE CNA BE LOTS OPF ERRORS INSIDE, ADN CTT USERS WON'T BEA ABLE TO SPOT THEM NWO WITH TEH SPELL CHECKER. 

I hope that this will be changed. It should be possible to turn it off. Even better: let the user decide to activate it and set the number of characters.

> It should be possible to turn it off.

Or better: It should be possible to turn it on (default = off). I think the experience of this feature not being turned off by default might result in traumatic experience of novices.

@alwayslockyourbike: do you see the buttons when triggering "List words with unknown spelling"?

Hi Torsten, I don't install this build until the three-letter ignoration has been solved. Can test it on the MacBook Pro at home.

I'd agree to that, but my first thought was "well, he won't do such a stupid thing" ;-)

Maybe my example was far-fetched and "stupid thing" was unfriendly, however there are the cases:

• whole texts or segments in upper-case -> spellcheck does not work properly (typos such as "ADN" or "FRO" do not seem to have any importance)
  
• texts where the acronyms that you do not want to add all acronyms to the userlist -> comfort
  

I have to agree with Torsten here. I think that this tree-letter acronym workflow is a rather rare user case. With all due respect, of course.

In my own daily work, I often translate software interfaces that contain three-letter abbreviations. It would be unpleasant if these wouldn't be checked.

Personally, I don't see any harm in adding any abbreviations (or acronyms) to the custom dictionary. It's quite simple to edit this or to use different custom dictionaries for different types of text (one for software strings, another for novels, etc.).

Catching any untranslated words that are in the custom dictionary (e.g. UNO), can be done via:

Not to forget the possibility to catch any wrong-spelled of these acronyms (some source texts – manuals – are less carefully edited than you might imagine, hey, they are only technicians).

Hi,

Igor, could you please make it an option.

I don't think the benefits of such implementation are greater than disadvantages, either.

I'm used to underlined non-translatables but not to actual typos' being ignored.

Perhaps I'm wrong but I guess three-letter acronyms even with known spelling won't be included in the auto-completion anyway, because they are too short.

                                                    Regards

                                                   Wojciech

Just a few words concerning heuristics.

If we take the correct article from Wikipedia here, you will se that the sky is not really blue. And perhaps we stumble upon the paragraph named Pitfalls. And if we follow the questions unter Trade-off, this very new feature would not have been introduced. Sorry, CafeTran is not a virus scanner. And it should not work with rules of thumb. A CAT tool needs precision and flexibility, not heuristics. This means of course also complexity (just multiply the important options in CafeTran to find out the number of possible configurations). When reading the article above, I cannot understand the latest release.