Mc MacH Mach chesnuts

Mc MacH Mach chesnuts

Post by Chris Brow » Fri, 05 Dec 2008 09:16:41


moving on from simple proper based calcs, and having implemented
SmarterProper, the problem still remains of how to handle:

MacSomething and Machinski

Anyone ideas on how to deal with this, other than removing all auto
enter calc formatting?

Mc MacH Mach chesnuts

Post by Hans Besje » Fri, 05 Dec 2008 10:11:22

And your question is what exactly?

Hans Besjes


Mc MacH Mach chesnuts

Post by Ursu » Sat, 06 Dec 2008 06:04:58

You can't. A machine can not know difference between MacIntosh and
Macintosh, which both a valid spellings. Rely on user input.

Keep well, ursus

"Chris Brown" < XXXX@XXXXX.COM > schreef in bericht

Mc MacH Mach chesnuts

Post by Chris Brow » Sat, 06 Dec 2008 07:21:56

thanks to all.

As Lynn suggested human intelligence was what I was hoping for; but
applied after the initial auto enter result from a custom function.

Agree with Grip, a proper calc is never going to be right all the time;
but if the cf could enter an initial suggestion, with the field then
allowing the user to correct the auto entry; that would be ideal.

Lyn, as for the apostrophe , van etc variations, the SmarterProper cf
seems quite flexible.

I was expecting that using the cf as an aec , and checking 'do not
replace existing value if any' would allow:

typing in the name,
the cf then forces its format
with a now existing entry, the user can correct the capitalisation,
without the cf re-triggering.

But FM !

If there is no existing value, when the first entry is made, when does
FM think it is going to apply the aec other than the first entry? I have
been converting calcs to aec as a general approach in a number of
solution revisions for the last 12 months, though probably always
unchecking the do not replace . So I am familiar with aec, but this just
doesn't compute in the cortex at the moment.