You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For each duplicate attribute id an error »ID "some" has already been defined« is reported. I think this is sufficient, maybe the text could be a little bit similar to what AHF itself reports for duplicate IDs.
The additional error »first occurrence of ID "some"« is misleading as it is raised for all but the first occurrence of the duplicate attribute and therefore just fills the error view.
My suggestion:
create an INFO entry for the real first occurrence of this id value (unless this is too time-consuming)
or remove that error
Thanks!
The text was updated successfully, but these errors were encountered:
focheck uses Jing for ID and IDREF checking rather than using Schematron on the theory that Jing should be faster because the checking is built into the validator.
The only way to change the Jing error messages would be to override the messages file, but getting rid of the 'first occurrence of ID "some"' messages would require modifying Jing and getting oXygen to use the modified Jing. Both are doable, but both are more work for the user than just installing an add-on.
One day, I'll find time to check whether using Jing or using an xsl:key with the Schematron is faster for ID and IDREF checking.
For each duplicate attribute id an error »ID "some" has already been defined« is reported. I think this is sufficient, maybe the text could be a little bit similar to what AHF itself reports for duplicate IDs.
The additional error »first occurrence of ID "some"« is misleading as it is raised for all but the first occurrence of the duplicate attribute and therefore just fills the error view.
My suggestion:
Thanks!
The text was updated successfully, but these errors were encountered: