Difference between revisions of "Bug Reports 2009 - 2013"

  The most annoying bug is the following: When one annotates it makes a lot of sense to keep taps of the most recently annotated
   tokens. However, as soon as one has one token-tap open, the second token one opens cannot be saved anymore. Even if one now
   starts to close all previously opened token-taps, it remains impossible to save the token that one just had worked on. :( 
  (Dorothee 17:21, 20 December 2008 (CET))                                        

 Bugs creeping in with the Lazy Annotation 
  This bug is new and came with the Lazy Annotation Mode: it seems as if saving is not always possible - it is kind of off and on.
  As was reported to me from one of the TypeCraft classes connected to a course at Dragvoll saving was not possible until the LAM-button was 
  unmarked. Then saving was possible again. Sorry nothing reproducible yet (Dorothee 18:00, 27 November 2008 (CET)) :(
  
  I started to work on a long sentence and tried to add construction tags, but could not use that functionality. Pressed button *CHANGE* for 
  construction parameters, but nothing happened, then I also noticed that I cannot save the sentence. That was on the day LAM was introduced. Have not
  encountered that bug again (Dorothee 18:00, 27 November 2008 (CET))

  I guess there was some cook-up having to do with the change of domain that we did around the same time. 
  Yet there is a real bug which arises when one opens a certain number of token tags under annotation. It is only possible to save changes to
  the last token that was opened. In addition one cannot open the *Change* button that allows one to specify the construction type parameters.
  (Dorothee 16:55, 15 December 2008 (CET))

The Bug List
  1. Oh my, long phrases imported from the database into the wiki 'run' out off the browser
     window. They trail off to the right. :(
     Is there anything that can be done about that?? You can see what we mean by looking at 
     Documenting Lule Sami. 
     Well ok, it is not a bug really but it looks so incredibly ugly :( 

  2. In (1) below <:CASE> IS coming before the ILL-SG. Better is:    ILL.SG  (Kristin)
     Within the tier annotation of a TCtoken <:CASE> should not appear at all! It is meant as an indication of the grammatical category to
     which the tag belongs. Information like acc<:CASE should only be available under mousing over tags
     (Dorothee 12:05, 15 December 2008 (CET))

  3. (Ben 07 Apr 2009)  
     Deleting an unsaved text results in user-level error message "Text id cannot be null". 
     Message should be more user-friendly (or dropped entirely).

  5. (Ben 07 Apr 2009)
     Clicking OK in the "TypeCraft wants to know" box when instantiating a phrase results in an empty phrase table.
     (BMW: have fix)

  6. (Ben 07 Apr 2009)
     It is not possible to delete the final lone word in a phrase table.

  7. (Ben 07 Apr 2009)
     Phrase tabs in text editor remain after phrase has been deleted.

  8. (Ben 07 Apr 2009)
     "Search for phrases" with "Look only within phrases I can edit" checked: Java error "unexpected end of subtree".
     (BMW: have fix)

  10. (Ben 07 Apr 2009)
      "Search for phrases" with "Constr. description" instantiated: Java error 
      caused by "java.sql.SQLException: Column not found: CONSTRUCTIONDESCRIPTION"
      (BMW: have fix)

  12. (Ben 17 Apr 2009)
      Attempts to set "Publish text" to false are ignored.
      (BMW: have fix)