Repository files navigation

Supports CSS file deduping, common style rule extraction and more (more detailed description below).

CssDeDup depends onExCSS to parse CSS documents. A big thanks to Tyler Brinks for writing ExCSS.

Linq2Css is a just wrapper around ExCSS, which is intented to provide more uniform access to the relevant properties, as well as hide irrelevant properties which are only a concern of the parser.

Unfortunately, a CSS document isnt just a collection of style rules, all defined at the same scope. There are constructs such as at-rules and conditional at-rules, within which style rules can be contained.NOTE: Version 1.0 handles style rules at the document level ONLY, and effectively ignores CSS rules nested under at-rules, such as @media. Deduped CSS documents that are written out to disk will re-serialize these constructs as-is or as functionally-equivalent CSS. So they are 'handled' in that sense,but their rules do not participate in de-duplication.

• Detailed explaination
  • Terminology
  • Functions
    • A. Exact Matching
    • B. CSS Rule Name Wildcard Matching
    • C. Fuzzy Property Value Matching
• Usage Examples

To better help explain things, lets define some terminology first:

.danger-text {   color: red;}

The text above is a CSS style'rule'.

"danger-text" is the'rule name'.

"color" is the'property'

"red" is the'property value'.

Now we may proceed with the descriptions...

CssDeDup has 3 different Functions:

• A. Exact Matching (CSS Rule Name & Properties must match exactly)
• B. CSS Rule Name Wildcard Matching (Only properties must match; CSS rule name can be anything)
• (Planned)C. Fuzzy Property Value Matching; NOTE: Not implemented yet.

All three features take two css documents as input.

It parses them into two collections of css rules.NOTE: Once again, these are the CSS style rules defined at the document level. @media-nested rules do not participate in deduplication for version 1.0.

It then finds "matching" css rules and extracts any css rules it finds to be a match into a third CSS document.

This considers two css rules a match if they match ALL 3 of the following criteria:

1. The rule name
2. The set of properties being set
3. The property values

So the css rule would have to be basically a copy-paste-identical match to be considered a match (minus case, whitespace and non-functional differences).

This does #2 and #3 from the list above, but ignores #1.

The CSS rule name can be anything.

This would ignore #1, #2 would have to match exactly, and #3 would have to 'match' according to fuzzy logic.

Examples of fuzzy logic matching on CSS property values:

• Two px values are within +-3 px of each other.
• Two colors are perceptually near-identical.

The best way to define the set of fuzzy logic rules to use is as of yet stil undecided. Create a suggestion/feature request 'issue' if you have some thoughts on this.

CssDeDup.exe nameandproperties --in1="C:\inetpub\wwwroot\NewsWebsite\default.css" --in2="C:\inetpub\wwwroot\AdminWebsite\default.css" --out="C:\Temp\CSS\CommonStyles_News-Admin.css"

• Optionnameandproperties performs functionA. Exact Matching from above.
• Takes 3 arguments: Two in files (--in1 & --in2) and one out file (--out)

CssDeDup.exe properties --in1="C:\inetpub\wwwroot\AdminWebsite\default.css" --in2="C:\inetpub\wwwroot\Old_AdminWebsite\default.css" --out="C:\Temp\CSS\CommonStyles_Admin-OldAdmin.css"

• Optionproperties performs functionB. CSS Rule Name Wildcard Matching from above.
• Takes 3 arguments: Two in files (--in1 & --in2) and one out file (--out)