QuerySelectorAll 1.9

The "querySelectorAll" compiled as 32-bit executable file for Windows platform (Win32), but versions of 64-bit Windows are also able to run this 32-bit application.

This is a way to execute CSS selector against the specified html files. Print the html items matching a pattern (group of CSS selectors).
	QuerySelectorAll 1.9 for Win32/Win64
	Print the html items matching a pattern (group of CSS
	QuerySelectorAll.exe [OPTIONS] CSS_SELECTOR [FILE...]
	Prints a list of the elements within the HTML files
	(using depth-first pre-order traversal of the document's
	nodes) that match the specified group of selectors.
	If the selectors string contains a CSS pseudo-element,
	the returned list will be empty.
		Print a usage message briefly summarizing these
		command-line options, then exit.
		Print the version number of grep to the standard
		output stream. This version number should be
		included	in all bug reports (see below).
		Verbose mode.  Causes tool to print debugging
		messages about its progress.
	-m param	
		Suppress default output mode! Usually there is
		stdout mode (0), but you can use other supported
		modes such as: (1) Save only one output file
		'_all.lst' with all the collected matches. (2)
		Save search matches from one file into new file,
		using filename the source file and predefined
		extension '.lst' as template to specify the target
		file. (3) Save each item into separated files
		(filename+counter+.lst). (4) Save each item into
		separated files (counter+.lst). (5) Make _index.lst
		an ordered list from A tags. Matched items will
		be cleaned on the strip_tags(), but (6) mode
		don't use it.
		Add the file name before each group: <!--****%s-->
	-i param	
		Set the input character encoding for parsing
		markup (output is always utf8). Values include:
		ascii, latin1, raw, utf8, iso2022, mac, win1251,
		win1252, utf16le, utf16be, utf16, big5 and shiftjis.
		Case in-sensitive. For unsupported encodings,
		use an external utility to convert to and from
	Reporting Bugs
		Email bug reports to author,
		The bug tracker located at

Responsive Order Process