Comments for WeSay News http://www.wesay.org/blogs Thu, 29 Jul 2010 15:52:17 +0000 http://wordpress.org/?v=2.6.5 Comment on StopWatch by Brayden Sanchez http://www.wesay.org/blogs/2006/06/16/stopwatch/#comment-10857 Brayden Sanchez Sat, 10 Jul 2010 07:16:36 +0000 http://blogs.wesayhome.org/2006/06/16/stopwatch/#comment-10857 we have a 5 year old General Electic air conditioner at home, GE makes some of the finest air conditioners out ther.:'` we have a 5 year old General Electic air conditioner at home, GE makes some of the finest air conditioners out ther.:’`

]]> Comment on Merging LIFT dictionary files by Ken Zook http://www.wesay.org/blogs/2010/01/21/merging-lift-dictionary-files/#comment-10805 Ken Zook Fri, 25 Jun 2010 14:53:24 +0000 http://www.wesay.org/blogs/2010/01/21/merging-lift-dictionary-files/#comment-10805 A LIFT file from Flex and WeSay store unique identifiers (GUIDs) on each entry and sense. At this point Flex will only attempt to merge entries or senses that have identical GUIDs. When a LIFT file is imported, Flex tries to merge data with matching GUIDs. If a definition or other field is missing in the database, but is present in the LIFT file, it will be added to the database. If any extra items for sequences (e.g., semantic domains, senses, examples) exist in the LIFT file, they will be added to whatever is already present in the database. If a field is present in the database but not in the LIFT file, the field will not be changed in the database. Thus you cannot use a LIFT import to remove anything from the database. If a field has different non-empty content in the database than in the LIFT file, then the import process uses one of three settings you choose at the beginning of the import. 1) The field is not changed in the database, thus skipping the LIFT field. 2) The field in the database is replaced with the field from the LIFT file. 3) A duplicate entry or sense will be created so that you can see the contents later and merge them manually. If entries or senses in the LIFT file do not have identical GUIDs, then the entire entry or sense is added to the database. Thus, if two users develop lexicons independently, a LIFT import will typically have many duplicate entries or senses since the GUIDs will all be different. Likewise, if a LIFT file is created by some other program such as Paratext, Lexique Pro, or Solid, the LIFT file will likely not have GUIDs, but even if it does, they would be entirely different, so the import would simply import all the data as separate entries with no attempt to merge. Another option can speed up import by trusting the modification dates on entries. If the modification dates for an entry are the same in the database and the LIFT file, the entry is automatically skipped without trying to analyze and merge all of the fields in the entry. A LIFT file from Flex and WeSay store unique identifiers (GUIDs) on each entry and sense. At this point Flex will only attempt to merge entries or senses that have identical GUIDs. When a LIFT file is imported, Flex tries to merge data with matching GUIDs. If a definition or other field is missing in the database, but is present in the LIFT file, it will be added to the database. If any extra items for sequences (e.g., semantic domains, senses, examples) exist in the LIFT file, they will be added to whatever is already present in the database. If a field is present in the database but not in the LIFT file, the field will not be changed in the database. Thus you cannot use a LIFT import to remove anything from the database. If a field has different non-empty content in the database than in the LIFT file, then the import process uses one of three settings you choose at the beginning of the import.
1) The field is not changed in the database, thus skipping the LIFT field.
2) The field in the database is replaced with the field from the LIFT file.
3) A duplicate entry or sense will be created so that you can see the contents later and merge them manually.
If entries or senses in the LIFT file do not have identical GUIDs, then the entire entry or sense is added to the database. Thus, if two users develop lexicons independently, a LIFT import will typically have many duplicate entries or senses since the GUIDs will all be different. Likewise, if a LIFT file is created by some other program such as Paratext, Lexique Pro, or Solid, the LIFT file will likely not have GUIDs, but even if it does, they would be entirely different, so the import would simply import all the data as separate entries with no attempt to merge.
Another option can speed up import by trusting the modification dates on entries. If the modification dates for an entry are the same in the database and the LIFT file, the entry is automatically skipped without trying to analyze and merge all of the fields in the entry.

]]> Comment on StopWatch by Noah James http://www.wesay.org/blogs/2006/06/16/stopwatch/#comment-10476 Noah James Thu, 13 May 2010 19:53:29 +0000 http://blogs.wesayhome.org/2006/06/16/stopwatch/#comment-10476 in our place, the weather could turn out to be uncomfortably humid that is why we bought an air conditioner at home to reduce h--* in our place, the weather could turn out to be uncomfortably humid that is why we bought an air conditioner at home to reduce h–*

]]> Comment on Merging LIFT dictionary files by Jeff Shrum http://www.wesay.org/blogs/2010/01/21/merging-lift-dictionary-files/#comment-10431 Jeff Shrum Sun, 09 May 2010 21:08:21 +0000 http://www.wesay.org/blogs/2010/01/21/merging-lift-dictionary-files/#comment-10431 I did try and import Wesay LIFT files in Flex 6.0.1. I later heard that these import problems were fixed in Flex 6.0.3. The file is too large for me to download so I am waiting for someone to had carry the installer file to me later in the month. Then I will be able to see if the newer version works better with LIFT files. I did try and import Wesay LIFT files in Flex 6.0.1. I later heard that these import problems were fixed in Flex 6.0.3. The file is too large for me to download so I am waiting for someone to had carry the installer file to me later in the month. Then I will be able to see if the newer version works better with LIFT files.

]]> Comment on More control over “missing info” tasks by John Hatton http://www.wesay.org/blogs/2009/06/22/more-control-over-missing-info-tasks/#comment-9276 John Hatton Sat, 13 Feb 2010 02:25:11 +0000 http://www.wesay.org/blogs/2009/06/22/more-control-over-missing-info-tasks/#comment-9276 @Daniel, I'm glad things are going well for you. If you're doing the LanguageDepot thing, I'm guessing you meant to comment on the following blog post, related to collaboration? @Daniel,
I’m glad things are going well for you. If you’re doing the LanguageDepot thing, I’m guessing you meant to comment on the following blog post, related to collaboration?

]]> Comment on More control over “missing info” tasks by Daniel Owens http://www.wesay.org/blogs/2009/06/22/more-control-over-missing-info-tasks/#comment-9265 Daniel Owens Fri, 12 Feb 2010 13:01:52 +0000 http://www.wesay.org/blogs/2009/06/22/more-control-over-missing-info-tasks/#comment-9265 I set up the TExT Hebrew lexicon, and your instructions are clear and accurate. LanguageDepot.org responded very quickly to my request, and it was simple to get up and running. So far I am extremely happy with this. Thanks so much for this great tool! If I have any snags I will let you know. I set up the TExT Hebrew lexicon, and your instructions are clear and accurate. LanguageDepot.org responded very quickly to my request, and it was simple to get up and running. So far I am extremely happy with this. Thanks so much for this great tool! If I have any snags I will let you know.

]]> Comment on Merging LIFT dictionary files by John Hatton http://www.wesay.org/blogs/2010/01/21/merging-lift-dictionary-files/#comment-9067 John Hatton Thu, 28 Jan 2010 22:39:59 +0000 http://www.wesay.org/blogs/2010/01/21/merging-lift-dictionary-files/#comment-9067 Richard, thanks for writing. FLEx does attempt to merge the items together, if they came from the same source. That is, I think, if you enter a word "xyz" and I separately enter the same word, it's not going to merge them. But in the common case where, say, you add a Part Of Speech to xyz, and I add a new sense, it will merge these changes together. About the "trust entry modification times" option, the FLEx documentation says it is for speeding up the import: "When selected, date and time metadata are compared between the current file and the import file. If the date/time stamps are identical for an entry, then no additional comparison is done." Since WeSay always updates the modified date, this is a safe thing to enable. In contrast, if you ran the LIFT file through a CC table or did a Search/Replace from Notepad, then it would *not* be safe to enable it, because although the data on the entries would be changed, the modified dates would be unchanged. Richard,
thanks for writing. FLEx does attempt to merge the items together, if they came from the same source. That is, I think, if you enter a word “xyz” and I separately enter the same word, it’s not going to merge them. But in the common case where, say, you add a Part Of Speech to xyz, and I add a new sense, it will merge these changes together.

About the “trust entry modification times” option, the FLEx documentation says it is for speeding up the import:
“When selected, date and time metadata are compared between the current file and the import file. If the date/time stamps are identical for an entry, then no additional comparison is done.”

Since WeSay always updates the modified date, this is a safe thing to enable. In contrast, if you ran the LIFT file through a CC table or did a Search/Replace from Notepad, then it would *not* be safe to enable it, because although the data on the entries would be changed, the modified dates would be unchanged.

]]> Comment on Merging LIFT dictionary files by Richard Gravina http://www.wesay.org/blogs/2010/01/21/merging-lift-dictionary-files/#comment-9056 Richard Gravina Thu, 28 Jan 2010 09:39:29 +0000 http://www.wesay.org/blogs/2010/01/21/merging-lift-dictionary-files/#comment-9056 I've imported several LIFT files from WeSay into FLEx. One question I have is what happens when two people have modified the same entry. For example, one person may have added a grammatical category where the other has left it blank. The second may have put in an example sentence. And they may both have put in slightly different definitions. When FLEx imports the LIFT file, does it combine the information from the two versions, or does it just take one and leave the other? What effect do the different import options have? I’ve imported several LIFT files from WeSay into FLEx. One question I have is what happens when two people have modified the same entry. For example, one person may have added a grammatical category where the other has left it blank. The second may have put in an example sentence. And they may both have put in slightly different definitions.

When FLEx imports the LIFT file, does it combine the information from the two versions, or does it just take one and leave the other? What effect do the different import options have?

]]> Comment on Merging LIFT dictionary files by WeSay News » Testing the New WeSay Collaboration Features http://www.wesay.org/blogs/2010/01/21/merging-lift-dictionary-files/#comment-9010 WeSay News » Testing the New WeSay Collaboration Features Thu, 21 Jan 2010 07:29:25 +0000 http://www.wesay.org/blogs/2010/01/21/merging-lift-dictionary-files/#comment-9010 [...] If there are multiple copies of the dictionary out there, you need to do that for each one of them.  That is, get the project, remove it from their computer.  You have an extra step in this case, which is to merge the entries together.  Read these instructions on merging LIFT files. [...] [...] If there are multiple copies of the dictionary out there, you need to do that for each one of them.  That is, get the project, remove it from their computer.  You have an extra step in this case, which is to merge the entries together.  Read these instructions on merging LIFT files. [...]

]]> Comment on Collecting audio with WeSay by online stock trading advice http://www.wesay.org/blogs/2009/01/07/collecting-audio-with-wesay/#comment-8886 online stock trading advice Mon, 11 Jan 2010 03:43:57 +0000 http://www.wesay.org/blogs/2009/01/07/collecting-audio-with-wesay/#comment-8886 what a great site and informative posts, I will add a backlink and bookmark your site. Keep up the good work! I'm Out! :) what a great site and informative posts, I will add a backlink and bookmark your site. Keep up the good work!

I’m Out! :)

]]>