Changes between Version 14 and Version 15 of ReleaseNotes/SCDB


Ignore:
Timestamp:
May 31, 2007, 10:18:54 AM (18 years ago)
Author:
/C=FR/O=CNRS/OU=UMR8607/CN=Michel Jouvin/emailAddress=jouvin@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseNotes/SCDB

    v14 v15  
    1818
    1919== New and Changed Features ==
    20 
    21 === 2.1.2 : `update.rep.templates` possible issue with empty repositories ===
    22 
    23 SCDB tools v2 including 2.1.2 has a possible issue with empty repositories (#63). This happens if you removed from the associated template everything except comment header '''and''' `structure template` line. In this case, the template is not updated and the propeprty `name` is missing. This leads to an error in SPMA functions.
    24 
    25 The easiest workaround is to also suppress the `structure template` line and update template name if the template is not namespaced.
    26 
    27 This should be fixed in 2.1.3.
    28 
    2920
    3021=== 2.1.2 : Support for repository/ namespace ===
     
    7465In addition to known problems documented here, look at [wiki:Doc/SCDB/FAQ SCDB FAQ].
    7566
     67=== 2.1.2 : update.rep.templates possible issue with empty repositories ===
     68
     69SCDB tools v2 including 2.1.2 has a possible issue with empty repositories (#63). This happens if you removed from the associated template everything except comment header '''and''' `structure template` line. In this case, the template is not updated and the propeprty `name` is missing. This leads to an error in SPMA functions.
     70
     71The easiest workaround is to also suppress the `structure template` line and update template name if the template is not namespaced.
     72
     73This should be fixed in 2.1.3.
     74
     75=== 2.0.0 : issue with accentuated characters ===
     76
     77The new PAN compiler (v7) encodes non ASCII characters in UTF-8. Unfortunatly, NCM components (particularly ncm-filecopy, and CCM are not prepared to handled properly UTF-8 encoded characters. The workaround is to remove these non ASCII characters from the templates (they are generally comments).
     78
     79This will be fixed in a future release (#17).
     80
    7681== Change Log ==
    7782