I'm going to, hopefully, correct some errors, sliding them across Pete's
desk for approval, in preparation for a spellchecker eksperiment.
Someone once said the wise words:
"Succinct is verbose for terse."
Regardless, I'll think a little out loud and anyone can join in or ignore
me.
I've hatched a rather ugly plan to try to implement the spellchecking. It
ends up being rather messy what with the code that doesn't compile and all.
I've still got some documentation to read so this "plan" of mine is still
on the drawing board.
I don't have the actual code that produced this library. All I can do is
"DUMPBIN /EXPORTS" it, giving me a complete list of exported functions and
their arguments.
You'd think it would be easy to just create an interface between the uses
of SPELL32.DLL and the HUNSPELL API but it turns out a certain Mr. Murphy
have had his cigar in the works.
It is sometimes difficult, bordering on impossible, to discern / gleen a
functions' inner workings from it's name. Even when held up against the
actual code.
As it works (read: functions) now, several places a CDialog is instantiated
only to be used as a utility class. Also, the current DLL seems to be
dishing out sessions (think superfluous book-keeping on both sides). To
make matters worse this session system is sometimes bypassed directly.
Here you'd maybe argue: then implement sessions for it, no big deal! But
the master architects, it seems, thought to use these session IDs in other
contexts as well. I strongly suspect that there isn't an architectural
structure to the code. Things looks more tagged on as an afterthought. Not
unusual in projects this size.
My modus operandi will thus be to remove existing portions of the spelling
code and see how I can fix the inexorably created errors using HUNSPELL.
For this however, I'd like the error count down to a more manageable
number. Hence my intention of removing errors. I see several places where
this should be possible. If the number of errors goes up or down as a
result remains to be seen. Coding is wonderful in this respect. :)
I'll also see if I can get a real UTF-8 version of HUNSPELL compiled. I'd
like to see some wchar_ts in there....
I'm going to, hopefully, correct some errors, sliding them across Pete's
desk for approval, in preparation for a spellchecker eksperiment.
Someone once said the wise words:
"Succinct is verbose for terse."
Regardless, I'll think a little out loud and anyone can join in or ignore
me.
I've hatched a rather ugly plan to try to implement the spellchecking. It
ends up being rather messy what with the code that doesn't compile and all.
I've still got some documentation to read so this "plan" of mine is still
on the drawing board.
I don't have the actual code that produced this library. All I can do is
"DUMPBIN /EXPORTS" it, giving me a complete list of exported functions and
their arguments.
You'd think it would be easy to just create an interface between the uses
of SPELL32.DLL and the HUNSPELL API but it turns out a certain Mr. Murphy
have had his cigar in the works.
It is sometimes difficult, bordering on impossible, to discern / gleen a
functions' inner workings from it's name. Even when held up against the
actual code.
As it works (read: functions) now, several places a CDialog is
instantiated only to be used as a utility class. Also, the current DLL
seems to be dishing out sessions (think superfluous book-keeping on both
sides). To make matters worse this session system is sometimes bypassed
directly.
Here you'd maybe argue: then implement sessions for it, no big deal! But
the master architects, it seems, thought to use these session IDs in other
contexts as well. I strongly suspect that there isn't an architectural
structure to the code. Things looks more tagged on as an afterthought. Not
unusual in projects this size.
My modus operandi will thus be to remove existing portions of the spelling
code and see how I can fix the inexorably created errors using HUNSPELL.
For this however, I'd like the error count down to a more manageable
number. Hence my intention of removing errors. I see several places where
this should be possible. If the number of errors goes up or down as a
result remains to be seen. Coding is wonderful in this respect. :)
I'll also see if I can get a real UTF-8 version of HUNSPELL compiled. I'd
like to see some wchar_ts in there....
I'm going to, hopefully, correct some errors, sliding them across Pete's
desk for approval, in preparation for a spellchecker eksperiment.
Someone once said the wise words:
"Succinct is verbose for terse."
Regardless, I'll think a little out loud and anyone can join in or ignore
me.
I've hatched a rather ugly plan to try to implement the spellchecking. It
ends up being rather messy what with the code that doesn't compile and all.
I've still got some documentation to read so this "plan" of mine is still
on the drawing board.
I don't have the actual code that produced this library. All I can do is
"DUMPBIN /EXPORTS" it, giving me a complete list of exported functions and
their arguments.
You'd think it would be easy to just create an interface between the uses
of SPELL32.DLL and the HUNSPELL API but it turns out a certain Mr. Murphy
have had his cigar in the works.
It is sometimes difficult, bordering on impossible, to discern / gleen a
functions' inner workings from it's name. Even when held up against the
actual code.
As it works (read: functions) now, several places a CDialog is
instantiated only to be used as a utility class. Also, the current DLL
seems to be dishing out sessions (think superfluous book-keeping on both
sides). To make matters worse this session system is sometimes bypassed
directly.
Here you'd maybe argue: then implement sessions for it, no big deal! But
the master architects, it seems, thought to use these session IDs in other
contexts as well. I strongly suspect that there isn't an architectural
structure to the code. Things looks more tagged on as an afterthought. Not
unusual in projects this size.
My modus operandi will thus be to remove existing portions of the
spelling code and see how I can fix the inexorably created errors using
HUNSPELL.
For this however, I'd like the error count down to a more manageable
number. Hence my intention of removing errors. I see several places where
this should be possible. If the number of errors goes up or down as a
result remains to be seen. Coding is wonderful in this respect. :)
I'll also see if I can get a real UTF-8 version of HUNSPELL compiled. I'd
like to see some wchar_ts in there....
That would be a eureka. In Danish it's spelled heureka and the H is
almost, but not quite, silent. Like an Hero on 4 chan.
I need a spellchecker myself.
[Obscure language lesson over]
It's originally Greek, and the way they spelled it was with a little
apostrophe (the "rough breathing sign") before the eta (their letter E).
In English, that rough breathing went away, so we have eureka without the
H. In Danish, the rough breathing graduated to an actual letter, so you
have heureka with an H.
On Saturday, October 27, 2018, sbrothy@gmail.com wrote:
(AFK)
My idea with this MO was that hopefully I'd see a pattern somewhere down
the line and have an eureka moment.
If not, unfortunately the spellchecking will be a little all over the
place. Much as it is now.
Regards
On Saturda the last ony, October 27, 2018, sbrothy@gmail.com wrote:
(AFK)
Tl:dr:
I'm going to, hopefully, correct some errors, sliding them across Pete's
desk for approval, in preparation for a spellchecker eksperiment.
Someone once said the wise words:
"Succinct is verbose for terse."
Regardless, I'll think a little out loud and anyone can join in or ignore
me.
I've hatched a rather ugly plan to try to implement the spellchecking. It
ends up being rather messy what with the code that doesn't compile and all.
I've still got some documentation to read so this "plan" of mine is still
on the drawing board.
I don't have the actual code that produced this library. All I can do is
"DUMPBIN /EXPORTS" it, giving me a complete list of exported functions and
their arguments.
You'd think it would be easy to just create an interface between the uses
of SPELL32.DLL and the HUNSPELL API but it turns out a certain Mr. Murphy
have had his cigar in the works.
It is sometimes difficult, bordering on impossible, to discern / gleen a
functions' inner workings from it's name. Even when held up against the
actual code.
As it works (read: functions) now, several places a CDialog is
instantiated only to be used as a utility class. Also, the current DLL
seems to be dishing out sessions (think superfluous book-keeping on both
sides). To make matters worse this session system is sometimes bypassed
directly.
Here you'd maybe argue: then implement sessions for it, no big deal! But
the master architects, it seems, thought to use these session IDs in other
contexts as well. I strongly suspect that there isn't an architectural
structure to the code. Things looks more tagged on as an afterthought. Not
unusual in projects this size.
My modus operandi will thus be to remove existing portions of the
spelling code and see how I can fix the inexorably created errors using
HUNSPELL.
For this however, I'd like the error count down to a more manageable
number. Hence my intention of removing errors. I see several places where
this should be possible. If the number of errors goes up or down as a
result remains to be seen. Coding is wonderful in this respect. :)
I'll also see if I can get a real UTF-8 version of HUNSPELL compiled. I'd
like to see some wchar_ts in there....
--
----- BEGIN TECO SIGNATURE BLOCK -----
32UD44UE97UR99UM101UA104UT106UO107UG110UL111UY114UP115UH116UI117UC$
QA:^US$QP:^US$QD:^US$QI:^US$QA:^US$QM:^UQ$QG:^UQ$QA:^UQ$QP:^UQ$
QE:^UQ$QO:^UU$QC:^UU$QH:^UU$QI:^UU$QD:^UU$QM:^UI$QY:^UI$QD:^UI$
QT:^UI$QR:^UI$QR:^UB$QL:^UB$QY:^UB$QI:^UB$QT:^UB$GI-5CGUGS-5CGB10CGQ0JT$$
----- END TECO SIGNATURE BLOCK -----
(Don't forget: ^ in TECO means just that, and $ means press the Esc key!)
It's originally Greek, and the way they spelled it was with a little
apostrophe (the "rough breathing sign") before the eta (their letter E).
In English, that rough breathing went away, so we have eureka without the
H. In Danish, the rough breathing graduated to an actual letter, so you
have heureka with an H.
So it's really you dishing out obscure language lessons, huh? Then explain
to me what the difference is between Greek and Polytonic Greek. :)
On Sun, 28 Oct 2018 at 04:27, Soren Bro sbrothy@users.sourceforge.net
wrote:
(AFK)
That would be a eureka. In Danish it's spelled heureka and the H is
almost, but not quite, silent. Like an Hero on 4 chan.
I need a spellchecker myself.
[Obscure language lesson over]
It's originally Greek, and the way they spelled it was with a little
apostrophe (the "rough breathing sign") before the eta (their letter E).
In English, that rough breathing went away, so we have eureka without the
H. In Danish, the rough breathing graduated to an actual letter, so you
have heureka with an H.
On Saturday, October 27, 2018, sbrothy@gmail.com wrote:
(AFK)
My idea with this MO was that hopefully I'd see a pattern somewhere down
the line and have an eureka moment.
If not, unfortunately the spellchecking will be a little all over the
place. Much as it is now.
Regards
On Saturda the last ony, October 27, 2018, sbrothy@gmail.com wrote:
(AFK)
Tl:dr:
I'm going to, hopefully, correct some errors, sliding them across Pete's
desk for approval, in preparation for a spellchecker eksperiment.
Someone once said the wise words:
"Succinct is verbose for terse."
Regardless, I'll think a little out loud and anyone can join in or ignore
me.
I've hatched a rather ugly plan to try to implement the spellchecking. It
ends up being rather messy what with the code that doesn't compile and all.
I've still got some documentation to read so this "plan" of mine is still
on the drawing board.
I don't have the actual code that produced this library. All I can do is
"DUMPBIN /EXPORTS" it, giving me a complete list of exported functions and
their arguments.
You'd think it would be easy to just create an interface between the uses
of SPELL32.DLL and the HUNSPELL API but it turns out a certain Mr. Murphy
have had his cigar in the works.
It is sometimes difficult, bordering on impossible, to discern / gleen a
functions' inner workings from it's name. Even when held up against the
actual code.
As it works (read: functions) now, several places a CDialog is
instantiated only to be used as a utility class. Also, the current DLL
seems to be dishing out sessions (think superfluous book-keeping on both
sides). To make matters worse this session system is sometimes bypassed
directly.
Here you'd maybe argue: then implement sessions for it, no big deal! But
the master architects, it seems, thought to use these session IDs in other
contexts as well. I strongly suspect that there isn't an architectural
structure to the code. Things looks more tagged on as an afterthought. Not
unusual in projects this size.
My modus operandi will thus be to remove existing portions of the
spelling code and see how I can fix the inexorably created errors using
HUNSPELL.
For this however, I'd like the error count down to a more manageable
number. Hence my intention of removing errors. I see several places where
this should be possible. If the number of errors goes up or down as a
result remains to be seen. Coding is wonderful in this respect. :)
I'll also see if I can get a real UTF-8 version of HUNSPELL compiled. I'd
like to see some wchar_ts in there....
--
----- BEGIN TECO SIGNATURE BLOCK -----
32UD44UE97UR99UM101UA104UT106UO107UG110UL111UY114UP115UH116UI117UC$
QA:^US$QP:^US$QD:^US$QI:^US$QA:^US$QM:^UQ$QG:^UQ$QA:^UQ$QP:^UQ$
QE:^UQ$QO:^UU$QC:^UU$QH:^UU$QI:^UU$QD:^UU$QM:^UI$QY:^UI$QD:^UI$
QT:^UI$QR:^UI$QR:^UB$QL:^UB$QY:^UB$QI:^UB$QT:^UB$GI-5CGUGS-5CGB10CGQ0JT$$
----- END TECO SIGNATURE BLOCK -----
(Don't forget: ^ in TECO means just that, and $ means press the Esc key!)
It's originally Greek, and the way they spelled it was with a little
apostrophe (the "rough breathing sign") before the eta (their letter E).
In English, that rough breathing went away, so we have eureka without the
H. In Danish, the rough breathing graduated to an actual letter, so you
have heureka with an H.
So it's really you dishing out obscure language lessons, huh? Then explain
to me what the difference is between Greek and Polytonic Greek. :)
Is it something related to Nynorsk and Bokmål? :)
Hoo boy.
This'll take some explaining. Polytonic Greek is a system for encoding
Greek diacritics, many of which have become silent in modern Greeks' way of
speaking. The contrast to it would be so-called Monotonic Greek. Not that
long ago, Polytonic played havoc with computer encodings, as it often put
more than one accent on a letter---hence Polytonic. That said, someone
who writes Polytonic (mostly people who studied Ancient Greek at school)
should have no problem to read the Monotonic way, and the reverse is often
true with practice.
The more direct equivalent to Nynorsk would be the difference between
Katharevousa and Demoteke. Katharevousa is Greek that has undergone a sort
of artificial evolution from Koiné (as spoken in the Bible), free of
corrupting influences (hence the name of the dialect, which translates to clean). Demotic is Greek as actually spoken by the common peasantry and
Great Unwashed (also, hence its name, which translates to people, like in democracy). Here, we start seeing actual vocabulary differences. Note
that you can write Katharevousa in both Polytonic and Monotonic
orthography, and the same with Demotic.
I'll give you a few examples on how this works out in practice: a
Katharevousa speaker would say ichthys for fish and (h)ydor for water
(from which the English have the words ichthyology, fish + to speak
about, and hydroponic, water + work). On the other hand, a Demotic
speaker would say psari for fish and nerô for water. I'm a proud
speaker of Katharevousa, which I write with the Monotonic orthography.
English has the same sort of distinction in what we call U and non-U
forms. The U form is directly comparable to Katharevousa, and it carries
the same sort of class distinction; the Queen would never be caught dead
asking for a serviette with which to wipe her nose, and she sits on a sofa
and not a couch. Similarly, educated people lunch at mid-day and dine in
the evening, while hoi polloi eat dinner in the day-time and supper in
the evening. My usual response to someone who insists on using non-U words
is "what did the English language do to you?"
Regards.
On Sun, Oct 28, 2018 at 3:41 PM Ted Matavka nmatavka@users.sourceforge.net
wrote:
On Sun, 28 Oct 2018 at 04:27, Soren Bro sbrothy@users.sourceforge.net
wrote:
(AFK)
That would be a eureka. In Danish it's spelled heureka and the H is
almost, but not quite, silent. Like an Hero on 4 chan.
I need a spellchecker myself.
[Obscure language lesson over]
It's originally Greek, and the way they spelled it was with a little
apostrophe (the "rough breathing sign") before the eta (their letter E).
In English, that rough breathing went away, so we have eureka without the
H. In Danish, the rough breathing graduated to an actual letter, so you
have heureka with an H.
On Saturday, October 27, 2018, sbrothy@gmail.com wrote:
(AFK)
My idea with this MO was that hopefully I'd see a pattern somewhere down
the line and have an eureka moment.
If not, unfortunately the spellchecking will be a little all over the
place. Much as it is now.
Regards
On Saturda the last ony, October 27, 2018, sbrothy@gmail.com wrote:
(AFK)
Tl:dr:
I'm going to, hopefully, correct some errors, sliding them across Pete's
desk for approval, in preparation for a spellchecker eksperiment.
Someone once said the wise words:
"Succinct is verbose for terse."
Regardless, I'll think a little out loud and anyone can join in or ignore
me.
I've hatched a rather ugly plan to try to implement the spellchecking. It
ends up being rather messy what with the code that doesn't compile and all.
I've still got some documentation to read so this "plan" of mine is still
on the drawing board.
I don't have the actual code that produced this library. All I can do is
"DUMPBIN /EXPORTS" it, giving me a complete list of exported functions and
their arguments.
You'd think it would be easy to just create an interface between the uses
of SPELL32.DLL and the HUNSPELL API but it turns out a certain Mr. Murphy
have had his cigar in the works.
It is sometimes difficult, bordering on impossible, to discern / gleen a
functions' inner workings from it's name. Even when held up against the
actual code.
As it works (read: functions) now, several places a CDialog is
instantiated only to be used as a utility class. Also, the current DLL
seems to be dishing out sessions (think superfluous book-keeping on both
sides). To make matters worse this session system is sometimes bypassed
directly.
Here you'd maybe argue: then implement sessions for it, no big deal! But
the master architects, it seems, thought to use these session IDs in other
contexts as well. I strongly suspect that there isn't an architectural
structure to the code. Things looks more tagged on as an afterthought. Not
unusual in projects this size.
My modus operandi will thus be to remove existing portions of the
spelling code and see how I can fix the inexorably created errors using
HUNSPELL.
For this however, I'd like the error count down to a more manageable
number. Hence my intention of removing errors. I see several places where
this should be possible. If the number of errors goes up or down as a
result remains to be seen. Coding is wonderful in this respect. :)
I'll also see if I can get a real UTF-8 version of HUNSPELL compiled. I'd
like to see some wchar_ts in there....
--
----- BEGIN TECO SIGNATURE BLOCK -----
32UD44UE97UR99UM101UA104UT106UO107UG110UL111UY114UP115UH116UI117UC$
QA:^US$QP:^US$QD:^US$QI:^US$QA:^US$QM:^UQ$QG:^UQ$QA:^UQ$QP:^UQ$
QE:^UQ$QO:^UU$QC:^UU$QH:^UU$QI:^UU$QD:^UU$QM:^UI$QY:^UI$QD:^UI$
QT:^UI$QR:^UI$QR:^UB$QL:^UB$QY:^UB$QI:^UB$QT:^UB$GI-5CGUGS-5CGB10CGQ0JT$$
----- END TECO SIGNATURE BLOCK -----
(Don't forget: ^ in TECO means just that, and $ means press the Esc key!)
--
----- BEGIN TECO SIGNATURE BLOCK -----
32UD44UE97UR99UM101UA104UT106UO107UG110UL111UY114UP115UH116UI117UC$
QA:^US$QP:^US$QD:^US$QI:^US$QA:^US$QM:^UQ$QG:^UQ$QA:^UQ$QP:^UQ$
QE:^UQ$QO:^UU$QC:^UU$QH:^UU$QI:^UU$QD:^UU$QM:^UI$QY:^UI$QD:^UI$
QT:^UI$QR:^UI$QR:^UB$QL:^UB$QY:^UB$QI:^UB$QT:^UB$GI-5CGUGS-5CGB10CGQ0JT$$
----- END TECO SIGNATURE BLOCK -----
(Don't forget: ^ in TECO means just that, and $ means press the Esc key!)
(AFK)
Tl:dr:
I'm going to, hopefully, correct some errors, sliding them across Pete's
desk for approval, in preparation for a spellchecker eksperiment.
Someone once said the wise words:
"Succinct is verbose for terse."
Regardless, I'll think a little out loud and anyone can join in or ignore
me.
I've hatched a rather ugly plan to try to implement the spellchecking. It
ends up being rather messy what with the code that doesn't compile and all.
I've still got some documentation to read so this "plan" of mine is still
on the drawing board.
I don't have the actual code that produced this library. All I can do is
"DUMPBIN /EXPORTS" it, giving me a complete list of exported functions and
their arguments.
You'd think it would be easy to just create an interface between the uses
of SPELL32.DLL and the HUNSPELL API but it turns out a certain Mr. Murphy
have had his cigar in the works.
It is sometimes difficult, bordering on impossible, to discern / gleen a
functions' inner workings from it's name. Even when held up against the
actual code.
As it works (read: functions) now, several places a CDialog is instantiated
only to be used as a utility class. Also, the current DLL seems to be
dishing out sessions (think superfluous book-keeping on both sides). To
make matters worse this session system is sometimes bypassed directly.
Here you'd maybe argue: then implement sessions for it, no big deal! But
the master architects, it seems, thought to use these session IDs in other
contexts as well. I strongly suspect that there isn't an architectural
structure to the code. Things looks more tagged on as an afterthought. Not
unusual in projects this size.
My modus operandi will thus be to remove existing portions of the spelling
code and see how I can fix the inexorably created errors using HUNSPELL.
For this however, I'd like the error count down to a more manageable
number. Hence my intention of removing errors. I see several places where
this should be possible. If the number of errors goes up or down as a
result remains to be seen. Coding is wonderful in this respect. :)
I'll also see if I can get a real UTF-8 version of HUNSPELL compiled. I'd
like to see some wchar_ts in there....
Regards
Soren
--
Søren Bro Thygesen
(AFK)
My idea with this MO was that hopefully I'd see a pattern somewhere down
the line and have an eureka moment.
If not, unfortunately the spellchecking will be a little all over the
place. Much as it is now.
Regards
On Saturda the last ony, October 27, 2018, sbrothy@gmail.com wrote:
--
Søren Bro Thygesen
(AFK)
That would be a eureka. In Danish it's spelled heureka and the H is
almost, but not quite, silent. Like an Hero on 4 chan.
I need a spellchecker myself.
[Obscure language lesson over]
On Saturday, October 27, 2018, sbrothy@gmail.com wrote:
--
Søren Bro Thygesen
On Sun, 28 Oct 2018 at 04:27, Soren Bro sbrothy@users.sourceforge.net
wrote:
--
----- BEGIN TECO SIGNATURE BLOCK -----
32UD44UE97UR99UM101UA104UT106UO107UG110UL111UY114UP115UH116UI117UC$
QA:^US$QP:^US$QD:^US$QI:^US$QA:^US$QM:^UQ$QG:^UQ$QA:^UQ$QP:^UQ$
QE:^UQ$QO:^UU$QC:^UU$QH:^UU$QI:^UU$QD:^UU$QM:^UI$QY:^UI$QD:^UI$
QT:^UI$QR:^UI$QR:^UB$QL:^UB$QY:^UB$QI:^UB$QT:^UB$GI-5CGUGS-5CGB10CGQ0JT$$
----- END TECO SIGNATURE BLOCK -----
(Don't forget: ^ in TECO means just that, and $ means press the Esc key!)
So it's really you dishing out obscure language lessons, huh? Then explain
to me what the difference is between Greek and Polytonic Greek. :)
Is it something related to Nynorsk and Bokmål? :)
Regards.
On Sun, Oct 28, 2018 at 3:41 PM Ted Matavka nmatavka@users.sourceforge.net
wrote:
On Sun, 28 Oct 2018 at 15:55, Soren Bro sbrothy@users.sourceforge.net
wrote:
This'll take some explaining. Polytonic Greek is a system for encoding
Greek diacritics, many of which have become silent in modern Greeks' way of
speaking. The contrast to it would be so-called Monotonic Greek. Not that
long ago, Polytonic played havoc with computer encodings, as it often put
more than one accent on a letter---hence Polytonic. That said, someone
who writes Polytonic (mostly people who studied Ancient Greek at school)
should have no problem to read the Monotonic way, and the reverse is often
true with practice.
The more direct equivalent to Nynorsk would be the difference between
Katharevousa and Demoteke. Katharevousa is Greek that has undergone a sort
of artificial evolution from Koiné (as spoken in the Bible), free of
corrupting influences (hence the name of the dialect, which translates to
clean). Demotic is Greek as actually spoken by the common peasantry and
Great Unwashed (also, hence its name, which translates to people, like in
democracy). Here, we start seeing actual vocabulary differences. Note
that you can write Katharevousa in both Polytonic and Monotonic
orthography, and the same with Demotic.
I'll give you a few examples on how this works out in practice: a
Katharevousa speaker would say ichthys for fish and (h)ydor for water
(from which the English have the words ichthyology, fish + to speak
about, and hydroponic, water + work). On the other hand, a Demotic
speaker would say psari for fish and nerô for water. I'm a proud
speaker of Katharevousa, which I write with the Monotonic orthography.
English has the same sort of distinction in what we call U and non-U
forms. The U form is directly comparable to Katharevousa, and it carries
the same sort of class distinction; the Queen would never be caught dead
asking for a serviette with which to wipe her nose, and she sits on a sofa
and not a couch. Similarly, educated people lunch at mid-day and dine in
the evening, while hoi polloi eat dinner in the day-time and supper in
the evening. My usual response to someone who insists on using non-U words
is "what did the English language do to you?"
--
----- BEGIN TECO SIGNATURE BLOCK -----
32UD44UE97UR99UM101UA104UT106UO107UG110UL111UY114UP115UH116UI117UC$
QA:^US$QP:^US$QD:^US$QI:^US$QA:^US$QM:^UQ$QG:^UQ$QA:^UQ$QP:^UQ$
QE:^UQ$QO:^UU$QC:^UU$QH:^UU$QI:^UU$QD:^UU$QM:^UI$QY:^UI$QD:^UI$
QT:^UI$QR:^UI$QR:^UB$QL:^UB$QY:^UB$QI:^UB$QT:^UB$GI-5CGUGS-5CGB10CGQ0JT$$
----- END TECO SIGNATURE BLOCK -----
(Don't forget: ^ in TECO means just that, and $ means press the Esc key!)