[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: rewrite entries processed in document order
I believe there is a slight inconsistency between rewriteSystem and delegateSystem catalog entries. With delegateSystem entries the order within the catalog entry file is not (so) important because entries with the longest match are processed first. This is not the case with rewrite entries, where the first match (in document order) is used. Of course delegate entries are different in that multiple matching entries will each contribute their file to the new catalog, whereas there can only be one successful rewrite entry. But the concept of matching entries using the longest possible match first has been introduced, and I wonder why this wasn't carried forward to rewrite entries. Regards ~Rob
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC