<head>
<style type="text/css">
<!--
/* start of attachment style */
.ygrp-photo-title{
clear: both;
font-size: smaller;
height: 15px;
overflow: hidden;
text-align: center;
width: 75px;
}
div.ygrp-photo{
background-position: center;
background-repeat: no-repeat;
background-color: white;
border: 1px solid black;
height: 62px;
width: 62px;
}
div.photo-title
a,
div.photo-title a:active,
div.photo-title a:hover,
div.photo-title a:visited {
text-decoration: none;
}
div.attach-table div.attach-row {
clear: both;
}
div.attach-table div.attach-row div {
float: left;
/* margin: 2px;*/
}
p {
clear: both;
padding: 15px 0 3px 0;
overflow: hidden;
}
p span {
color: #628C2A;
}
div.ygrp-file {
width: 30px;
valign: middle;
}
div.attach-table div.attach-row div div a {
text-decoration: none;
}
div.attach-table div.attach-row div div span {
font-weight: normal;
}
div.ygrp-file-title {
font-weight: bold;
}
/* end of attachment style */
-->
</style>
</head>
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--#YGRP-MLMSG
{*font-size:small;
*font:x-small;}
#YGRP-MLMSG table
{font-size:inherit;}
#YGRP-MLMSG pre
{*font-size:100%;}
code
{*font-size:100%;}
#ygrp-mlmsg * {line-height:1.22em;}
#ygrp-vital a:hover{
text-decoration: underline;
}
#ygrp-sponsor .ad a:hover{
text-decoration: underline;
}
o{font-size: 0; }
div.photo-title a,
div.photo-title a:active,
div.photo-title a:hover,
div.photo-title a:visited {
text-decoration: none;
}
div.file-title a,
div.file-title a:active,
div.file-title a:hover,
div.file-title a:visited {
text-decoration: none;
}
#YGRP-MSG p
{overflow:hidden;}
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Galatia SIL";
panose-1:2 0 6 0 2 0 0 2 0 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
h1
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:0in;
page-break-after:avoid;
font-size:16.0pt;
font-family:Arial;
font-weight:bold;}
p.MsoTitle, li.MsoTitle, div.MsoTitle
{margin-top:12.0pt;
margin-right:0in;
margin-bottom:3.0pt;
margin-left:0in;
text-align:center;
font-size:24.0pt;
font-family:Arial;
font-weight:bold;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
code
{font-family:"Courier New";}
pre
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
tt
{font-family:"Courier New";}
p.Dictionaryentry, li.Dictionaryentry, div.Dictionaryentry
{margin-top:6.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
text-indent:-.5in;
punctuation-wrap:simple;
text-autospace:none;
font-size:12.0pt;
font-family:"Times New Roman";}
p.Secondarytitle, li.Secondarytitle, div.Secondarytitle
{margin-top:0in;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:0in;
text-align:center;
punctuation-wrap:simple;
text-autospace:none;
font-size:16.0pt;
font-family:"Times New Roman";
font-weight:bold;}
p.Tertiarytitle, li.Tertiarytitle, div.Tertiarytitle
{margin:0in;
margin-bottom:.0001pt;
text-align:center;
punctuation-wrap:simple;
text-autospace:none;
font-size:14.0pt;
font-family:"Times New Roman";}
span.GreekHeadword
{font-family:"Galatia SIL";
font-weight:bold;}
span.Greek
{font-family:"Galatia SIL";}
p.Block, li.Block, div.Block
{margin-top:6.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
p.Bibliography, li.Bibliography, div.Bibliography
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
text-indent:-.5in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.Style1
{font-family:"Galatia SIL";
font-weight:bold;}
span.Greekbold
{font-family:"Galatia SIL";
font-weight:bold;}
p.Dictionarysubentry, li.Dictionarysubentry, div.Dictionarysubentry
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:1.0in;
margin-bottom:.0001pt;
text-indent:-.5in;
punctuation-wrap:simple;
text-autospace:none;
font-size:12.0pt;
font-family:"Times New Roman";}
p.Title-secondary, li.Title-secondary, div.Title-secondary
{margin-top:0in;
margin-right:0in;
margin-bottom:6.0pt;
margin-left:0in;
text-align:center;
punctuation-wrap:simple;
text-autospace:none;
font-size:16.0pt;
font-family:"Times New Roman";
font-weight:bold;}
p.Title-tertiary, li.Title-tertiary, div.Title-tertiary
{margin:0in;
margin-bottom:.0001pt;
text-align:center;
punctuation-wrap:simple;
text-autospace:none;
font-size:14.0pt;
font-family:"Times New Roman";}
span.Keyword
{font-weight:bold;
text-decoration:underline;}
p.ad, li.ad, div.ad
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
p.ad1, li.ad1, div.ad1
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
p.ad2, li.ad2, div.ad2
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
p.ad3, li.ad3, div.ad3
{mso-margin-top-alt:auto;
margin-right:0in;
margin-bottom:6.25pt;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
p.replbq, li.replbq, div.replbq
{margin:2.5pt;
font-size:12.0pt;
font-family:"Times New Roman";}
p.ad4, li.ad4, div.ad4
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
p.ad5, li.ad5, div.ad5
{mso-margin-top-alt:auto;
margin-right:0in;
margin-bottom:6.25pt;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
p.ad6, li.ad6, div.ad6
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.yshortcuts1
{font-family:Verdana;
font-weight:bold;}
span.yshortcuts2
{font-family:Verdana;
color:#1E66AE;
font-weight:normal;}
span.EmailStyle48
{mso-style-type:personal-reply;
font-family:"Times New Roman";
color:blue;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1616908629;
mso-list-template-ids:1055674166;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=blue face="Times New Roman"><span
style='font-size:10.0pt;color:blue'>Hi Sebastian,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Times New Roman"><span
style='font-size:10.0pt;color:blue'>Modern dictionaries treat POS subcategories
in a separate field. For instance the Longman Dictionary of American English
puts the subcategory after the first sense number. (Their pronunciation field
is IPA which I’m too lazy to duplicate.)<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Times New Roman"><span
style='font-size:10.0pt;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Times New Roman"><span
style='font-size:10.0pt;color:blue'>liberty /’librti/ n 1 [C,U] the
freedom to do…<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Times New Roman"><span
style='font-size:10.0pt;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Times New Roman"><span
style='font-size:10.0pt;color:blue'>C = ‘count’, U = ‘uncounted’.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Times New Roman"><span
style='font-size:10.0pt;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Times New Roman"><span
style='font-size:10.0pt;color:blue'>If a verb has more than one subcategory, it
will be specified after each sense number:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Times New Roman"><span
style='font-size:10.0pt;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Times New Roman"><span
style='font-size:10.0pt;color:blue'>lighten /’laitn/ v 1 [T] to reduce
the amount… 2 [I,T] to become lighter… 4 [I,T] to reduce the weight…<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Times New Roman"><span
style='font-size:10.0pt;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Times New Roman"><span
style='font-size:10.0pt;color:blue'>T = ‘transitive’ I = ‘intransitive’<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Times New Roman"><span
style='font-size:10.0pt;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Times New Roman"><span
style='font-size:10.0pt;color:blue'>I think the reason for this is that
students are taught the meaning of ‘verb’ and ‘noun’ in
school. The subcategories are separated so that the serious student has the
information, but it isn’t going to confuse the lazy(?!) student who only
wants to know the primary category. Labels like ‘nC’ or ‘vi/t’
are less likely to communicate.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Times New Roman"><span
style='font-size:10.0pt;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Times New Roman"><span
style='font-size:10.0pt;color:blue'>MDF was great in its day, but has proven to
be (1) limited and (2) inflexible. The CC tables that it uses were far too
complicated and impossible for anyone to modify. All standards are somewhat
inflexible by their very nature. Some of the newer standards (e.g. LIFT) are
attempting to use a better model of the lexicon and to take into consideration
the wide range of linguistic typology.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Times New Roman"><span
style='font-size:10.0pt;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Times New Roman"><span
style='font-size:10.0pt;color:blue'>With MDF you have two options. (1) Hijack
an unused field that prints like you want it to. It is often difficult to find
a field that prints where and how you want it to, so this rarely works. (2)
Store your information in a custom field. Then, just before you print, modify
the database so that it will print like you want it to. This requires using
something like a CC table to merge two fields and add printer codes. You have
to be a bit of a computer guru to pull this off. You do have a third option:
(3) Use a different program. For instance FieldWorks allows you to set up POS (grammatical)
subcategories, but also allows you to specify how each subcategory will print.
Because FieldWorks uses a POS hierarchy, there is no problem with the
interlinear. Subcategories inherit from their parent category. So you can write
general rules that apply to the major categories and all the subcategories
under them. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Times New Roman"><span
style='font-size:10.0pt;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Times New Roman"><span
style='font-size:10.0pt;color:blue'>Ron Moe<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face="Times New Roman"><span
style='font-size:10.0pt;color:blue'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
lexicographylist@yahoogroups.com [mailto:lexicographylist@yahoogroups.com] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Sebastian Drude<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, March 12, 2009
6:52 PM<br>
<b><span style='font-weight:bold'>To:</span></b> Shoebox/Toolbox Field
Linguist's Toolbox; Lexicography<br>
<b><span style='font-weight:bold'>Subject:</span></b> [Lexicog] part-of-speech
subcats</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div id=ygrp-mlmsg>
<div style='float:left;z-index:1' id=ygrp-msg>
<div id=ygrp-text>
<p style='margin-bottom:12.0pt'><font size=3 face="Times New Roman"><span
style='font-size:12.0pt'>Dear Toolboxers and Lexicographers,<br>
<br>
<br>
I hope I am not abusive when I put this question forward to the toolbox and
lexicography groups (sorry for possible cross-postings)<wbr>. As others posted
in the Toolbox group only this question popped up in the process of
transferring an older idiosyncratic lexical database to the MDF standard.
I guess that some of my questions might be interesting for other users who have
similar needs or wishes, and maybe something could be included in possible
future versions of MDF.<br>
<br>
Such a case is the representation of Part-of-Speech subcategories.<br>
<br>
This post deals with Toolbox (Standard Format, MDF) databases in particular,
but I would like to know which solutions other or related technology offers (in
particular, LexiquePro). I am particularly interested in exporting from and to
Toolbox.<br>
<br>
<br>
I an older (idiosyncratic and inconsistent, but MDF-based) system, I used a
combination of the standard <b><span style='font-weight:bold'>\ps</span></b>
field (obligatory) and, in many cases, a <b><span style='font-weight:bold'>\pss</span></b>
field (<i><span style='font-style:italic'>"part of speech subcategory</span></i>",
optional). In the first I (ideally) put only abbreviations for the major
word categories -- in my case, <b><span style='font-weight:bold'>adv</span></b>(erb),
<b><span style='font-weight:bold'>id</span></b>(eophone), <b><span
style='font-weight:bold'>int</span></b>(er)<b><span style='font-weight:bold'>j</span></b>(ection),
<b><span style='font-weight:bold'>n</span></b>, <b><span style='font-weight:
bold'>num</span></b>(eral), <b><span style='font-weight:bold'>part</span></b>(icle),
<b><span style='font-weight:bold'>p</span></b>(ost)<b><span style='font-weight:
bold'>p</span></b>(osition), <b><span style='font-weight:bold'>pron</span></b>(oun),
<b><span style='font-weight:bold'>v</span></b>(erb). <br>
In the second, I put labels for subcategories, such as <b><span
style='font-weight:bold'>inal</span></b>(ienable) etc. (for nouns), <b><span
style='font-weight:bold'>dem</span></b>(onstrative)<wbr>, <b><span
style='font-weight:bold'>pers</span></b>(on) (for pronouns), <b><span
style='font-weight:bold'>i</span></b>(n)<b><span style='font-weight:bold'>tr</span></b>(ansitive),
<b><span style='font-weight:bold'>st</span></b>(ative), <b><span
style='font-weight:bold'>tr</span></b>(ansitive) (for verbs). Some of
these may hold for several major classes (cross-classificati<wbr>ons), for
instance <b><span style='font-weight:bold'>inter</span></b>(rogative) or <b><span
style='font-weight:bold'>neg</span></b>(ation) (for adverbs, pronouns,
particles,..<wbr>.).<br>
<br>
All abbreviations in both fields are obligatorily linked (jump-path) with
corresponding entries in another database, where I give the long name and
explain what exactly this label stands for and which properties these words
have.<br>
<br>
Using only MDF fields, I have only one <b><span style='font-weight:bold'>\ps</span></b>
field (<b><span style='font-weight:bold'>\pn</span></b> for national language,
ok). As far as I can see, I have several options to organize the same
information:<br>
<br>
1) one complex abbreviation in the \ps field, such as <b><span
style='font-weight:bold'>n.inal</span></b> or <b><span style='font-weight:bold'>v.tr</span></b>.<br>
<br>
2) several separate abbreviations in the <b><span style='font-weight:bold'>\ps</span></b>
field.<br>
<br>
3) main word classes in <b><span style='font-weight:bold'>\ps</span></b>, as
before, subcategories in another field.<br>
<br>
<br>
None of these fully satisfies me, for at least the following reasons:<br>
<br>
<b><i><span style='font-weight:bold;font-style:italic'>A)</span></i></b> With
(3) I have the problem to choose an appropriate field. <b><span
style='font-weight:bold'>\pd</span></b> seems to be an obvious option (many of
the subcategories are indeed relevant for the paradigm structure). However, the
subcategory abbreviation will be put at the end of the entry, and will be
formatted with a label such as "<i><span style='font-style:italic'>Parad:</span></i>",
which does not make sense or is at least counter-intuitive for those subclasses
which are of a rather semantic kind.<br>
<br>
<b><i><span style='font-weight:bold;font-style:italic'>B)</span></i></b> With
(2), I would have to add manually punctuation after the first (main) word
class. This causes potential problems for consistency, for defining range sets
etc.<br>
<br>
<b><i><span style='font-weight:bold;font-style:italic'>C)</span></i></b> (1)
and (2) are much clumsier for interlinearization, filtering and sorting. <br>
<i><span style='font-style:italic'>C1)</span></i> Interlinearization: In the
part-of-speech line the whole complex label (1) can be too much information (be
it only for formatting reasons), and (2) does not interlinearize well at all or
at least produces fields with internal spaces (if I define the data type as
"single item") which are painful for exporting to other formats such
as ELAN's <b><span style='font-weight:bold'>eaf</span></b>-files.<br>
<i><span style='font-style:italic'>C2)</span></i> Filters that make reference
to word classes will be much more difficult to formulate correctly.<br>
<i><span style='font-style:italic'>C3)</span></i> Sorting: Sometimes, I just
want to sort by major word classes, searching, say, for verbs ending in a
certain letter. Depending on the number of combined subcategories, I will have
many internally alphabetically ordered groups of verbs.<br clear=all>
<br>
<b><i><span style='font-weight:bold;font-style:italic'>D)</span></i></b> With
(1), I would create many complex labels which are to administer and which are,
in the printed dictionary, much less esthetical and easy to read than separate
abbreviations. True, many subcategories only apply only to one major word
class anyway; but this does not hold for others such as <b><span
style='font-weight:bold'>inter</span></b> or <b><span style='font-weight:bold'>neg</span></b>
(see above).<br>
<br>
<br>
I guess that a solution can be set up using appropriate cc-tables or some other
mechanism doing replacements with regular expressions, or by splitting fields
automatically for sort, jump, interlinearization and similar functions, or by
joining fields (as the MDF <b><span style='font-weight:bold'>\ps</span></b> and
my <b><span style='font-weight:bold'>\pss</span></b> field), for formatting and
printing. <br>
But this still has the disadvantage of being difficult set up generally and in
a sustainable way, and to have to keep track of different versions of the
'same' database for different purposes.<br>
<br>
<br>
How do you all represent and organize this kind of information? <br>
What would you recommend?<br>
<br>
With your solution, what happens if you export MDF databases to LexiquePro,
LEXUS or other formats, and back to Toolbox?<br>
<br>
Thank you in advance<br>
<br>
Sebastian<br>
<br>
-- <br>
| Sebastian Drude (Linguist)<br>
| <a href="mailto:Sebastian.Drude@fu-berlin.de" target="_blank">Sebastian.Drude@<wbr>fu-berlin.<wbr>de</a>
& <a href="mailto:Sebastian.Drude@googlemail.com" target="_blank">Sebastian.Drude@<wbr>googlemail.<wbr>com</a><br>
| <a href="http://www.germanistik.fu-berlin.de/il/pers/drude-en.html"
target="_blank">http://www.germanis<wbr>tik.fu-berlin.<wbr>de/il/pers/<wbr>drude-en.<wbr>html</a><o:p></o:p></span></font></p>
</div>
<!-- |**|begin egp html banner|**| -->
<br>
<br>
<!-- |**|end egp html banner|**| -->
<div width="1" style="color: white; clear: both;"/>__._,_.___</div>
<!-- Start Recommendations -->
<!-- End Recommendations -->
<!-- |**|begin egp html banner|**| -->
<img src="http://geo.yahoo.com/serv?s=97476590/grpId=11682781/grpspId=1709195911/msgId=4922/stime=1236974892" width="1" height="1"> <br>
<!-- |**|end egp html banner|**| -->
<!-- |**|begin egp html banner|**| -->
<br>
<div style="font-family: verdana; font-size: 77%; border-top: 1px solid #666; padding: 5px 0;" >
Your email settings: Individual Email|Traditional <br>
<a href="http://groups.yahoo.com/group/lexicographylist/join;_ylc=X3oDMTJncHRuMDAzBF9TAzk3NDc2NTkwBGdycElkAzExNjgyNzgxBGdycHNwSWQDMTcwOTE5NTkxMQRzZWMDZnRyBHNsawNzdG5ncwRzdGltZQMxMjM2OTc0ODky">Change settings via the Web</a> (Yahoo! ID required) <br>
Change settings via email: <a href="mailto:lexicographylist-digest@yahoogroups.com?subject=Email Delivery: Digest">Switch delivery to Daily Digest</a> | <a href = "mailto:lexicographylist-fullfeatured@yahoogroups.com?subject=Change Delivery Format: Fully Featured">Switch to Fully Featured</a> <br>
<a href="http://groups.yahoo.com/group/lexicographylist;_ylc=X3oDMTJlazlvcDd0BF9TAzk3NDc2NTkwBGdycElkAzExNjgyNzgxBGdycHNwSWQDMTcwOTE5NTkxMQRzZWMDZnRyBHNsawNocGYEc3RpbWUDMTIzNjk3NDg5Mg--">
Visit Your Group
</a> |
<a href="http://docs.yahoo.com/info/terms/">
Yahoo! Groups Terms of Use
</a> |
<a href="mailto:lexicographylist-unsubscribe@yahoogroups.com?subject=Unsubscribe">
Unsubscribe
</a>
<br>
</div>
<br>
<!-- |**|end egp html banner|**| -->
<div style="color: white; clear: both;"/>__,_._,___</div>
</body>
</html>
<!--End group email -->
<P><FONT SIZE=2 FACE="Arial">No virus found in this incoming message.<BR>
Checked by AVG - www.avg.com<BR>
Version: 8.0.237 / Virus Database: 270.11.10/1995 - Release Date: 03/12/09 10:38:00<BR>
</FONT></P>