Bug #269
detected markers not browsable
| Status: | New | Start: | 06/18/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | application | Spent time: | - | |
| Target version: | V1.1.x | |||
| Resolution: |
Description
I had several entries in which \lx got smushed together with its word (e.g. \lxhambei), and SOLID helpfully detected them. However, when I clicked on each marker, some of them would show up in the right-hand pane, and some wouldn't. This is disconcerting and makes it difficult to fix the problems from inside SOLID. I then opened the file up in Notepad++ and verified that the bad markers are indeed all there. Thus, it was easiest to fix them in Notepad++ (now that they'd been identified by SOLID, of course).
I've attach my (unfixed) file.
using SOLID 0.9.318.0
History
Updated by J C almost 3 years ago
I think I've figured out why/when this happens. It looks like SOLID counts all occurrences of a given marker, but ignores the empty ones when you click on the marker name and browse through the matching records. So for example, if I click on \lf, records like this one will show up:
\lx parancina
\saku no
\dt 12/May/2009
\lf lihat
\lv palola mbawu
\ln tomat
\le tomato
\ps
\sn 1
\de tomato
\dn tomat
But records like this one will not:
\lx palola mbawu
\saku no
\dt 23/Jan/2009
\lf
\lv parancina
\le tomat
\ps n
\sn 1
\dn tomat
\de tomato
\is 5.2.3.3.3
\sd Spice
I think both kinds should show up, especially since I might want to fix the second one.
Updated by J C about 2 years ago
This issue is the same as #159. -Jon
Updated by Beth Bryson almost 2 years ago
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.
Updated by J C almost 2 years ago
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 record markers--and it's easy to find out what they are in Solid by scanning the top-left pane for bogus markers. However, you should then use a separate editor to find and fix them.
This might even be necessary after #159 gets fixed, if the munged marker in question happens to be \lx, since Solid doesn't like you messing with the record marker:
"Change field to \lx and it disappears" http://projects.palaso.org/issues/show/173
-Jon
Updated by Cambell Prince over 1 year ago
- Target version set to V1.1.x
TODO: Have a look at this, not sure how we'll handle it at this stage.