Subject:SS passing invalid CALS table as valid Author:John Accardi Date:13 Dec 2006 06:53 AM
Why isn't SS recognizing that the attached table is invalid?
(AdeptEdit is correctly catching it.) When I used this bad table in the DITA-OT 1.3, I also got fo errors. When I fixed the table (as per AdeptEdit) DITA processing was fine. (BTW, SS did also claim the fixed table was also valid; it just has trouble calling the bad one bad.)
Is there a patch for SS I can apply to make its validator smarter on this CALS issue?