[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff-comment] Errors in XLIFF 2.1 Test Suite files
Hi, Only two files in â/validâ threw warnings, the rest may have different authors. The â/invalidâ files are also problematic. Some of them contain errors not related to the intended mistake. They need to be reviewed too. When I wrote the first validation set for XLIFF 2.0, ÂI looked at the published Schematron files. They did not convince me at first; something seemed wrong. After trying to add them to my validation code, I confirmed my initial understanding. They simply donât work as intended. I donât think it is a good idea to rejoin the TC at this moment, perhaps later. Nevertheless, I can help with the Test Suite. I know that OASIS has a strong IP policy, you will have to find out if my contributions would be accepted. Regards, Rodolfo From: Bryan Schnabel <bschnabel@bschnabel.com> Hi Rodolfo, Wow, seems like whoever wrote those examples must have been very sloppy. Let's see if we can find a clue in the last warning you mentioned: WARNING: 18:21 schema_reference.4: Failed to read schema document 'file:/C:/Users/bryans/Desktop/presentations/schnabel_demos_under-construction/XLIFF2.0-utils/XLIFF2.0/xliff-core-v2.0-csprd03/schemas/xliff_core_2.0.xsd' The bad news is it looks like I made all those sloppy errors; so it will be up to me to fix them. The good news is we see just how important and practical the newly introduced Advanced Validation module turned out to be that we introduced it in XLIFF 2.1. The testing suite had undergone several rounds of validation by several XLIFF TC members before being published. It is an absolute mystery to me that this is the first indication that it contains errors. I have a proposal Rodolfo, would you rejoin the TC and help me fix these files? Your friend, Bryan On Saturday, April 6, 2019, 2:03:47 PM PDT, Rodolfo M. Raya <rmraya@maxprograms.com> wrote: Hello, There are XLIFF files with errors in the â/validâ directories of the Test Suite for XLIFF 2.1 Errors found with XLIFF Manager: core/valid/allExtensions.xlf -> Missing <sc/> element with id="1" referenced by <ec/> core/valid/withModulesAttributesInEc.xlf -> Missing <sc/> element with id="2" referenced by <ec/> core/valid/withReferences.xlf -> Invalid fragment identifier '#f=f2/u=u1/n=n1' in comment annotation modules/valid/Good-mtc_reference-lang.xlf -> Different "xml:lang" in <target> modules/valid/Good-slr_equivStorage-ec-not-isolated.xlf -> Missing <sc/> element with id="ec" referenced by <ec/> modules/valid/Good-slr_sizeInfo-not-with-sizeInfoRef.xlf -> Missing <sc/> element with id="e1" referenced by <ec/> modules/valid/Good-slr_sizeInfoRef-ec-isolated.xlf -> Missing <sc/> element with id="e1" referenced by <ec/> modules/valid/Goodslr_sizeRestriction-isolated.xlf -> Missing <sc/> element with id="i-ec-yes" referenced by <ec/> Errors found using XLIFF Schematron files: core/valid/allExtensions.xlf --> 'isolated' attribute is set to 'yes', but the corresponding 'sc' element, out of the 'unit' with 'id=2', was not found. The start code must appear before the end code, but in the same 'file'. core/valid/everything-core.xlf --> 'canDelete' attribute is set to 'no', but the corresponding element is missing in the sibling target. core/valid/withModulesAttributesInEc.xlf --> 'isolated' attribute is set to 'yes', but the corresponding 'sc' element, out of the 'unit' with 'id=1', was not found. The start code must appear before the end code, but in the same 'file'. core/valid/withNotes.xlf --> 'canCopy' attribute is not matching with the 'canCopy' attribute of the corresponding 'ec' element (out of 'unit' with 'id=1'). core/valid/withNotes_complex.xlf --> 'canCopy' attribute is not matching with the 'canCopy' attribute of the corresponding 'ec' element (out of 'unit' with 'id=1'). modules/valid/Good-slr_equivStorage-ec-not-isolated.xlf --> 'isolated' attribute is set to 'yes', but the corresponding 'sc' element, out of the 'unit' with 'id=u2', was not found. The start code must appear before the end code, but in the same 'file'. modules/valid/Good-slr_sizeInfo-not-with-sizeInfoRef.xlf --> 'isolated' attribute is set to 'yes', but the corresponding 'sc' element, out of the 'unit' with 'id=u1', was not found. The start code must appear before the end code, but in the same 'file'. modules/valid/Good-slr_sizeInfoRef-ec-isolated.xlf --> 'canCopy' attribute is not matching with the 'canCopy' attribute of the corresponding 'ec' element (out of 'unit' with 'id=sm1'). modules/valid/Goodslr_sizeRestriction-isolated.xlf --> 'isolated' attribute is set to 'yes', but the corresponding 'sc' element, out of the 'unit' with 'id=u1', was not found. The start code must appear before the end code, but in the same 'file'. modules/valid/withNotes_complex_for_ITS_Processors.xlf --> 'canCopy' attribute is not matching with the 'canCopy' attribute of the corresponding 'ec' element (out of 'unit' with 'id=1'). I got this warning in the log for a couple of files when processing with XLIFF Manager: WARNING: 18:21 schema_reference.4: Failed to read schema document 'file:/C:/Users/bryans/Desktop/presentations/schnabel_demos_under-construction/XLIFF2.0-utils/XLIFF2.0/xliff-core-v2.0-csprd03/schemas/xliff_core_2.0.xsd' Regards, Rodolfo -- Rodolfo M. Raya rmraya@maxprograms.com Maxprograms https://www.maxprograms.com |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]