An example will make this clear:
Define two AutoCorrect replacement strings:
|e'| -> é
|e`| -> è
Now if you AutoCorrect |e`|, it will yield é, just as if you AutoCorrect'ed |e'|.
This is with Atlantis 1.6.6.4. I don't have a copy on-hand at the moment, but I think that this worked properly with 1.6.6.3, since that was the version I used to define my AutoCorrect strings.
Jeses
Atlantis Doesn't recognize backtick properly in AutoCorrect
Hmm, I'm not in the French language, but rather English, USA. This happens across all my machines, Windows 7, 8.1, and XP.
I tried using Factory Settings, and the same behavior shows.
All other punctuation marks work correctly. It's as though Atlantis just doesn't recognize the backtick as a character for autocorrect: for instance, if I create an autocorrect entry
`a` -> atick
It will never AutoCorrect the `a`.
Is there some other debugging step I might try?
Thanks,
Jesse
I tried using Factory Settings, and the same behavior shows.
All other punctuation marks work correctly. It's as though Atlantis just doesn't recognize the backtick as a character for autocorrect: for instance, if I create an autocorrect entry
`a` -> atick
It will never AutoCorrect the `a`.
Is there some other debugging step I might try?
Thanks,
Jesse
Atlantis always worked that way. You should not use different types of apostrophes within the "Replace what" pairs of the AutoCorrect because Atlantis would still treat them as straight apostrophes.
Please read the "D" section of the Inserting characters not available directly through the keyboard Help topic. It explains how to add such "replace with" items to Atlantis.
Please read the "D" section of the Inserting characters not available directly through the keyboard Help topic. It explains how to add such "replace with" items to Atlantis.
Hi Jesse,
Why not stick with a single symbol like the underscore or the backslash for example?
As a rule, and for obvious reasons, you should use symbols that are readily available on your keyboard.
In any case, and as admin pointed out, you should stick to symbols that do not have (many) variants like the apostrophe or the quote marks. You should also avoid using symbols like the “grave accent” (your back tick) that are meant to be used in association with other characters (the so-called “spacing” or “non-spacing” Unicode characters). In other words, only use “standalone” symbols. If at all practical, you could use the “@”, “&”, “+”, “=”, or “|” signs, for example.
HTH.
Cheers,
Robert
Why not stick with a single symbol like the underscore or the backslash for example?
As a rule, and for obvious reasons, you should use symbols that are readily available on your keyboard.
In any case, and as admin pointed out, you should stick to symbols that do not have (many) variants like the apostrophe or the quote marks. You should also avoid using symbols like the “grave accent” (your back tick) that are meant to be used in association with other characters (the so-called “spacing” or “non-spacing” Unicode characters). In other words, only use “standalone” symbols. If at all practical, you could use the “@”, “&”, “+”, “=”, or “|” signs, for example.
HTH.
Cheers,
Robert