Solid

07/26/2010

08:53 AM Bug #454: hierarchy difference with FLEx

Beth Bryson wrote: > > lx bayar > se mambayar > bw Ind > ps n > .... > st rn > dt 17/Jul/2009 > The thing is that looks perfectly ambiguous and legal both ways to me. Although if taking the ps under lx then that leaves the se being... Cambell Prince

07/21/2010

01:26 AM Bug #454: hierarchy difference with FLEx

Here is the corrected image that goes with the above post. Timothy Armstrong

07/20/2010

04:05 AM Bug #455: random crash? On "SuperToolTipWindow"

I got this crash as described in the attached crash report. But when I did pretty much the same thing a second time, it didn't crash. Don't know what the problem was. Reporting it just in case it's useful.... Beth Bryson

03:49 AM Bug #454: hierarchy difference with FLEx

Here is a tiny database with just this record in it, plus the SOLID settings I used. Beth Bryson

03:43 AM Bug #454: hierarchy difference with FLEx

I'm not totally sure what the issue here is, but there is a discrepancy between how SOLID is treating this and how FLEx is treating it. It would be helpful if SOLID could help me figure out what FLEx was going to do with this. In SOLID, I said... Beth Bryson

03:24 AM Bug #261: Dont delete header info in data file

Beth Bryson wrote: > It would also be helpful if you left the blank lines before the lx fields. I know, not all that many people open Toolbox files, but some do. The scenario for this is like this: - I have worked on a file in SOLID. I... Beth Bryson

03:19 AM Bug #261: Dont delete header info in data file

Beth Bryson wrote: > I think this is quite important, and hopefully it wouldn't be that hard to do? It would also be helpful if you left the blank lines before the \lx fields. I know, not all that many people open Toolbox files, but some do. Beth Bryson

06/02/2010

11:11 PM Feature #438: Need a quick fix for renaming markers found under a specified parent marker

Having certain fields at various levels is perfectly acceptable, standard MDF, and people do use \nt that way, so the FLEx importer really ought to be fixed to be able to handle the \nt field (and other fields) appearing at multiple levels. (This ... J C

10:54 PM Bug #403: intervening markers vs preceding markers

As mentioned above, Solid is supposed to license multiple occurrences of a given field in either of two ways: -"One or more times together" or -"One or more times with intervening markers". although this isn't working properly yet. IDEA: Wh... J C

06/01/2010

10:43 PM Feature #343: Add MDF as a mapping, on by default

Ah, thanks. That makes sense to me now. Personally, I think it should be an editable "Description" field that typically contains the MDF name and description associated with a marker. But as groups create their own templates (A.J. is doing so f... J C

10:15 PM Feature #275: a global setting for the encoding of all fields

Related issue (of lesser importance): "need a column indicating encoding, in top-left pane" http://projects.palaso.org/issues/show/431 J C

10:14 PM Feature #431: need a column indicating encoding, in top-left pane

Actually, I just realized that this column might not be necessary IF issue #275 is resolved in the way I requested: "a global setting for the encoding of all fields" http://projects.palaso.org/issues/show/275 J C

10:01 PM Bug #269: detected markers not browsable

Note that here the primary underlying issue with Solid is this one: "Confusing differnce in what constitutes an existing marker" http://projects.palaso.org/issues/show/159 The underlying issue here with my data was simply bad data--bogus recor... J C

08:13 PM Feature #343: Add MDF as a mapping, on by default

The 2 letter markers used in dictionaries are not particularly clear in their meaning. So I think the suggestion is to have a fuller text representation of what the marker actually is, and also indicate if it is 'standard' MDF marker vs a user def... Cambell Prince

07:40 PM Bug #435: Allow for a constraint: "entry level fields may not interrupt sense level fields"

When there is a field that I have said is an Entry level field, and it comes in the middle of fields that are Sense level fields, SOLID assumes that it does belong to the Entry, and that the next Sense field starts a new Sense. However, it may si... Beth Bryson

07:27 PM Bug #432: Templates need to match the official standards more precisely

In addition to having one that accurately reflects the MDF Alternate hierarchy, I think it would be important to have one that reflects FLEx's interpretation of the MDF hierarchy, which is different. (Specifically, \ps is a sibling of \ge and \de... Beth Bryson

07:24 PM Feature #431: need a column indicating encoding, in top-left pane

This would be helpful. Beth Bryson

07:24 PM Bug #427: alternate hierarchy should default to multiple ps per sn

Personally, I *don't* think this should be changed. It doesn't match real language to have more than one POS per sense. My interpretation of the MDF alternate hierarchy is simply that \ps is required to be specified for each sense, and if it's... Beth Bryson

07:17 PM Bug #426: Not even an English writing system exists by default

1. Apparently the "eng" problem got fixed along the way... And they have fixed FLEx import to recognize when data is coming in with the "eng" abbreviation. 2. In case it matters for anything, the 8 "Internationalization languages" are: Englis... Beth Bryson

07:09 PM Bug #403: intervening markers vs preceding markers

I agree. As it is, it just feels like the middle button just doesn't work, and some of the functionality that is needed just isn't there. Beth Bryson

07:04 PM Bug #326: Find dialog remember last input

Is this the same as #273? Beth Bryson

07:04 PM Feature #325: Inferred count in marker settings

It would be *really* helpful to have a way to quickly scroll through all of the inferred \sn fields, or all the inferred \ps fields, etc. Yes, this would be *very* good, to increase confidence before applying the "make real" command. Beth Bryson

07:02 PM Feature #284: auto scroll problem field into view

This would be really helpful. Beth Bryson

07:01 PM Feature #275: a global setting for the encoding of all fields

This would be helpful. Beth Bryson

07:00 PM Bug #159: Confusing differnce in what constitutes an existing marker

I think it would be good if you could show the records that have the empty markers. Is there a way to have two kinds of counts? Number of times the marker occurs, and number that are empty? Like FLEx does in its import report. I'm more c... Beth Bryson

06:59 PM Bug #269: detected markers not browsable

This would be really helpful to have fixed, or some way easily find the smushed markers, so they could be fixed in some other editor. Beth Bryson

06:57 PM Bug #261: Dont delete header info in data file

I think this is quite important, and hopefully it wouldn't be that hard to do? Beth Bryson

06:56 PM Bug #260: Mark preceding tag red

Well, I guess it depends somewhat on who the audience is. I have gotten accustomed in other domains to looking higher up for an error that is flagged lower down. I think this is something SOLID users can be taught. Often it's not the immediatel... Beth Bryson

06:46 PM Bug #172: Break up reversal parst when exporting to lift

Hmm, interesting. 1. I think FLEx now *does* interpret the semicolon to mean it should make separate reversals. So this may not be needed for the \re field. 2. But something might be needed for \ge. Or does JohnH have a "quick fix" or othe... Beth Bryson

06:33 PM Bug #170: Make template handle normal \pn useage

Yeah, I think FLEx doesn't currently have a way to import POS in more than one language. Usually I harvest the info ahead of time, and then pre-set the categories in FLEx. Then I only import one language of the POS fields. When there is a one-t... Beth Bryson

06:28 PM Bug #147: Change name in structure dialog

I'm not sure what's wanted here, but I saw what Jon describes: - If I backspace over a marker name until the focus box is empty, when I try to click somewhere else, it says, "Marker name cannot be empty". Or I can change the name. - If I ju... Beth Bryson

06:22 PM Bug #66: Some markers in FLEx but not in MDF book

There are also some markers that FLEx treats differently from MDF. For instance, \ue is a free-form field in MDF, but in LinguaLinks it is a range set. FLEx imports it to a List Choice field, so I tend not to map it to the default--I tend to map... Beth Bryson

04:59 PM Bug #432: Templates need to match the official standards more precisely

Yes, I'm planning on doing this if I do the template fixing. But to do a complete review and fixup requires - making a data file containing all the markers, - carefully reading the MDF documentation and sometimes comparing with Toolbox, and -... J C

08:29 AM Bug #432: Templates need to match the official standards more precisely

The templates are simply solid files themselves stored in C:\Program Files\Solid\templates. So you can create templates of your own by simply creating a solid file (using solid) that you like. If you feel that it is more standard than the one th... Cambell Prince

05/31/2010

11:24 PM Feature #433: Help: add the user manual to Solid, or at least add a link

I only just discovered that there's a manual for Solid! I just stumbled onto the link for it at the Palaso site, but I don't think it was announced on the Palaso blog and I don't see it included in Solid in any way. I think it should be added to t... J C

09:07 PM Bug #427: alternate hierarchy should default to multiple ps per sn

On second thought, I've created a more-generically-named issue for tracking problems with the templates: http://projects.palaso.org/issues/show/432 ("Templates need to match the official standards more precisely") J C

09:04 PM Feature #255: Show marker hierarchy

Handling the following issue may result in good hierarchical documentation for the MDF standard(s): http://projects.palaso.org/issues/show/432 It's likely that a document will eventually be attached there which could also serve as a good start... J C

09:01 PM Bug #432: Templates need to match the official standards more precisely

The templates that ship with Solid (MDF standard and MDF alternate, in particular) do not precisely match the official documentation for those standards, as far as I can tell. I think we need to work together with the "owners" of the MDF standard ... J C

08:51 PM Feature #431: need a column indicating encoding, in top-left pane

Currently, it's easy to overlook the fact that one or two fields are set to the wrong encoding. Most of the time, mixed-encoding is a bad thing, but Solid's defaults can easily lead to a template that's accidentally set up for mixed encoding... J C

05:12 PM Feature #254: Make all \sn fields empty except for the ones that should be published

Also, this quick fix or a similar one should probably give the option of renumbering all \sn fields, correcting any manual numbering errors that may have crept in. J C

05:10 PM Bug #427: alternate hierarchy should default to multiple ps per sn

See also: http://projects.palaso.org/issues/show/170 http://projects.palaso.org/issues/show/171 Maybe we should document all suggested template changes here (in issue 427)? J C

05:09 PM Bug #170: Make template handle normal \pn useage

See also: http://projects.palaso.org/issues/show/427 http://projects.palaso.org/issues/show/171 Maybe we should document all suggested template changes under issue 427? J C

05:09 PM Bug #171: In alternate hierarchy template, let \sd have lx as a parent

See also: http://projects.palaso.org/issues/show/427 http://projects.palaso.org/issues/show/170 Maybe we should document all suggested template changes under issue 427? J C

05:02 PM Feature #343: Add MDF as a mapping, on by default

I don't really understand this issue. Could you please clarify a bit what it is you're suggesting there? -J J C

04:31 PM Bug #427: alternate hierarchy should default to multiple ps per sn

The larger issue here is the fact that "MDF Unicode" and "MDF Alternate Unicode" aren't 100% correct with regard to the official MDF standard, as far as I can tell. I think we need to work together with one of the "owners" of the MDF standard in o... J C

04:22 PM Bug #425: Make Markers Real quick fix sometimes does nothing

This is a bigger problem than I originally thought, affecting ordinary edits too, rather than just that quick fix. For example, if I edit something in the right pane (like appending "zz" to a lexeme form) and then immediately run a quick fix (like... J C

05/30/2010

04:23 AM Revision 359: Add Palaso intellisense xml files

Add Palaso intellisense xml files hatton

03:34 AM Revision 358: Updated for latest Palaso, moved to .net 3.5

Updated for latest Palaso, moved to .net 3.5 hatton

05/29/2010

09:18 PM Bug #426: Not even an English writing system exists by default

Jon, When I run SOLID, I see that it shows all the writing systems I've set up in the Windows Language and Keyboard settings: English, Icelandic, and Arabic. When you do it, I'd expect you'd see "English" and "Indonesian". Can you check again a... john hatton

05/10/2010

11:50 PM Bug #426: Not even an English writing system exists by default

Ken Z just told me the following: "If you have people use SOLID to make LIFT files, make sure it uses correct 2-letter writing system codes or it can get Flex messed up on import. A prime example is eng should be en." This is all the more reaso... J C

05/09/2010

04:05 AM Bug #427: alternate hierarchy should default to multiple ps per sn

My understanding is that the whole point of the alternate hierarchy in MDF is that you can have a single sense with multiple parts of speech, although this goes against prevailing theory. So, I don't see why Solid's default for an alternate DB is ... J C

05/08/2010

11:54 PM Bug #426: Not even an English writing system exists by default

Out of the box, Solid doesn't have a single writing system predefined--not even English. Since English is part of the MDF standard, I would think it at least should be included. Instead, I had to manually create it type "Eng" "English" "en", and a... J C

10:55 PM Bug #269: detected markers not browsable

This issue is the same as #159. -Jon J C

10:54 PM Bug #159: Confusing differnce in what constitutes an existing marker

This issue is the same as #269. -Jon J C

10:51 PM Bug #266: Solid ignores font size

This appears to have been fixed. Both font and size are applied when I change them. -Jon Win7 Solid 0.11.350.0 J C

10:45 PM Bug #261: Dont delete header info in data file

I think this bug fix should be given top priority since this is causing a bit of data loss. Some users won't know what to do when reopening the file in Toolbox and may end up choosing the wrong database type. -Jon J C

10:40 PM Bug #259 (Closed): Indicate out of date stats

I think this was my idea, and I'm fine with closing it, so I just did. -Jon J C

10:36 PM Bug #171: In alternate hierarchy template, let \sd have lx as a parent

Maybe this is a shorthand for saying "all of the senses of this word share this semantic domain", but is this really a standard? I thought the only difference with the alt hierarchy was the relative ordering of ps and sn. Since only senses can hav... J C

10:31 PM Bug #170: Make template handle normal \pn useage

But when importing such things (part of speech, semantic domain) into FLEx, isn't it usually best to stick with one analysis language (usually English) and not even bother to import the other? Given that assumption, perhaps pn should be a sister o... J C

10:24 PM Bug #159: Confusing differnce in what constitutes an existing marker

Yes, this is inconsistent. I'm not sure I like the idea of switching to a non-empty count, because other fields besides sn can be empty yet important: ps, rf, and even something like ge (if it is set up to imply sn, for instance). Also, an empty f... J C

10:18 PM Bug #147: Change name in structure dialog

This seems to have been fixed. I now get an error message saying that the parent field cannot be empty. So instead of backspacing over the characters, selecting the marker and hitting the Delete key works. Someone should verify this on XP and Vist... J C

10:05 PM Bug #425: Make Markers Real quick fix sometimes does nothing

First of all, kudos to you all (or "onyas" as those on the little island west of NZ say) for generalizing the Make Markers Real quickfix. That's a nice improvement! I did notice however, that nothing seems to happen after I click the blue link.... J C

08:00 PM Bug #176: LIFT export not valid with current LIFT schema.

Are there plans to finish the LIFT export feature soon? One reason I'm interested in this feature is because Solid is better than the FLEx importer at understanding fields such as \st and \lf and the notes fields. These are fields which can occur ... J C

07:57 PM Bug #403: intervening markers vs preceding markers

I was just about to add a ticket for this exact issue. Instead I'd just like to agree 100% with what Allan has written here. -Jon J C