<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:st1="urn:schemas-microsoft-com:office:smarttags" 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]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</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:"\@Arial Unicode MS";
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 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:2078547407;
mso-list-template-ids:-1931708160;}
@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'>Sebastian Drude wrote:<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'>“</span></font>I prefer very much the
simple Standard Format (text) files toolbox produces and which I can easily
manipulate with a general text editor (or CC tables).<font size=2 color=blue><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'><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 just looked at the interlinear export
options in FLEx. It appears that it primarily exports XML. But it does export
to HTML and Open Office Writer. It also has quite a few XML options, including
exporting in Word format. There is a FLEx email discussion list similar to the
Lexicography List that is very active and helpful in answering users’
questions.<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 understand your liking for small files
and for data that can be manipulated by CC tables. I’ve been using CC for
25 years, but very few people use it anymore. I still maintain my DDP list of
semantic domains in Toolbox (and my address list), but FLEx is far more
efficient in developing and editing a dictionary. I used to use CC tables to
develop and manipulate lexical data, but got very tired of my inability to
interact with what the CC tables were doing. They were also hard to write. The
Bulk Edit tools in FLEx enable me to do what I used to do with CC tables, only
now I can interact with them. They are also easier to use. (I was the one who
suggested that FLEx needed the Bulk Edit tools and I helped to design them.) However
there are some tasks that cannot be done with FLEx (or Toolbox) that can be
done with CC tables (or some other similar process such as Perl or Python).<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'>One of the best things that is happening
these days in the realm of lexicography software is the development of
standards for marking up lexical data. SIL has developed the Lexical
Information Transfer (LIFT) standard that is being used to facilitate moving
data from one software package to another. LIFT is XML. Already FLEx, WeSay,
and Lexique Pro support LIFT. It would be nice if Toolbox would be modified so
that you can export your dictionary in LIFT format. But I doubt that it will
ever happen. (See below.) There is also work going on right now on a wider (international)
scale to set up data standards so that dictionaries can be posted to the web in
a single standardized format. This will enable software designers to write
software that will work on any dictionary that is formatted using the standard.
It will also enable us to post lots of different dictionaries from different
languages on a website and search all the dictionaries for various kinds of
information. It would be nice if there were a data standard for interlinearized
text that would enable us to easily create it, work with it, and transfer it
from program to program.<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'>As far as I know, there are no plans to
further develop Toolbox. I believe the reasons are (1) it is fairly stable as
it is (it works well and has few bugs), (2) it is old technology and therefore
difficult to improve, (3) the basic design of the program has some inherent
flaws (e.g. it does not constrain the structure of the data, with the result
that every Toolbox file gets messed up over time). It is for these reasons that
various people have developed add-ons such as MDF, Lexique Pro, and SOLID to
make up for its defects.<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'>The bottom line is that every software
package does some things well, others things poorly, and other things not at
all.<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'> <st1:PersonName
w:st="on">lexicographylist@yahoogroups.com</st1:PersonName> [mailto:<st1:PersonName
w:st="on">lexicographylist@yahoogroups.com</st1:PersonName>] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Sebastian Drude<br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, March 18, 2009
12:36 PM<br>
<b><span style='font-weight:bold'>To:</span></b> <st1:PersonName w:st="on">lexicographylist@yahoogroups.com</st1:PersonName><br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [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'>Thank you Ronald and Alan,<br>
<br>
<br>
for your helpfully replying to my question. It seems, if I want to use
Toolbox the way I pretend, probably continuing to use a non-standard
(self-made) <b><span style='font-weight:bold'>\pss</span></b> field will do
best; but yes, I will have indeed to pre-process the dictionary each time I
want to print or export.<br>
<br>
I am aware of FieldWork, thank you, Ronald, and will try its import-process
a.s.a.p. Maybe that also helps to "clean" my lexical databases without
haveing to try SOLID out.<br>
<br>
I have not used FieldWork yet because I am not comfortable with a 400MB-program
(with .NET and SQL more than 880MB seems to be needed to install it all) which
saves its data solely in a relational database of several hundred MBs.<br>
I prefer very much the simple Standard Format (text) files toolbox produces and
which I can easily manipulate with a general text editor (or CC tables).<br>
<br>
Furthermore, I use ELAN <<a href="http://www.lat-mpi.eu/tools/elan"
target="_blank">http://www.lat-<wbr>mpi.eu/tools/<wbr>elan</a>> for storing
and publishing texts, which are mostly annotated media files, and ELAN accepts
(with difficulties) interlinearized SF files as import and export options. So I
rely to Toolbox for doing the interlinearization and then transfer the
annotation to EAF (ELAN Annotation Format). But FieldWork does not permit
(yet?) transcription and annotation of video files and, worse, does not provide
export capacities of interlinearized text to SF files. So, how do I get
my text data out of Fieldwork (I am not going to program an XSL stylesheet to
convert the Fieldwork-generated XML-files to SF)?<br>
<br>
Generally, I hope that Toolbox will be maintained and developed further as a
complementary tool to FieldWork.<br>
<br>
Best,<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=4925/stime=1237419709" 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=X3oDMTJnbm9nbWc4BF9TAzk3NDc2NTkwBGdycElkAzExNjgyNzgxBGdycHNwSWQDMTcwOTE5NTkxMQRzZWMDZnRyBHNsawNzdG5ncwRzdGltZQMxMjM3NDE5NzA5">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=X3oDMTJldnMyZGk3BF9TAzk3NDc2NTkwBGdycElkAzExNjgyNzgxBGdycHNwSWQDMTcwOTE5NTkxMQRzZWMDZnRyBHNsawNocGYEc3RpbWUDMTIzNzQxOTcwOQ--">
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.238 / Virus Database: 270.11.18/2009 - Release Date: 03/18/09 07:17:00<BR>
</FONT></P>