Parses your object, modifying it for defined cases that apply.
Node.js port of PDF extraction and case parser
a parser case; parser(content)
lezer-based HTML grammar
Powerful and compliant CSS selector parser.
Detect Browser, Engine, OS, CPU, and Device type/model from User-Agent data. Supports browser & node.js environment
A utility package to parse strings
A JavaScript parser
the mighty option parser used by yargs
A fast, efficient parser for multipart streams in any JavaScript environment
Node.js body parsing middleware
Simple RFC 6838 media type parser and formatter
An ESLint custom parser which leverages TypeScript ESTree
Simple, transparent parser combinators toolkit that supports any tokens
> Selector parser with built in methods for working with selector strings.
lightweight JavaScript APG parser
An AST parser for ICU MessageFormat strings
Detect Browser, Engine, OS, CPU, and Device type/model from User-Agent & Client Hints data. Supports browser & node.js environment
Range header field string parser
Super-fast alternative to Babel for when you can target modern JS runtimes
Algorithms to help you parse CSS from an array of tokens.
extracts and replaces values and IDs in URLs
Validate XML, Parse XML, Build XML without C/C++ based libraries
An inline style parser.
Alternative and more powerful gettext parser for ruby files. It covers some special cases which the normal parser can't handle
A little lexer toolkit, designed for the cases where parsers do the parsing and lexers do the lexing.
RDocF95 is an improved RDoc for generation of documents of Fortran 90/95 programs. Differences to the original one are given below. <b>Enhancement of "parser/f95.rb"</b> :: The Fortran 90/95 parse script "parser/f95.rb" (In rdoc-f95, old name "parsers/parse_f95.rb" is used yet) is modified in order to parse almost all entities of the Fortran 90/95 Standard. <b>Addition of <tt>--ignore-case</tt> option </b> :: In the Fortran 90/95 Standard, upper case letters are not distinguished from lower case letters, although original RDoc produces case-dependently cross-references of Class and Methods. When this options is specified, upper cases are not distinguished from lower cases. <b>Cross-reference of file names</b> :: Cross-reference of file names is available as well as modules, subroutines, and so on. <b>Modification of <tt>--style</tt> option</b> :: Original RDoc can not treat relative path stylesheet. Application of this patch modifies this function. <b>Conversion of TeX formula into MathML</b>:: TeX formula can be converted into MathML format with --mathml option, if <b>MathML library for Ruby version 0.6b -- 0.8</b> is installed. This library is available from {Bottega of Hiraku (only JAPANESE)}[http://www.hinet.mydns.jp/~hiraku/]. See {RDocF95::Markup::ToXHtmlTexParser}[link:classes/RDocF95/Markup/ToXHtmlTexParser.html] about format. <b>*** Caution ***</b> Documents generated with "--mathml" option are not displayed correctly according to browser and/or its setting. We have been confirmed that documents generated with "--mathml" option are displayed correctly with {Mozilla Firefox}[http://www.mozilla.org/products/firefox/] and Internet Explorer (+ {MathPlayer}[http://www.dessci.com/en/products/mathplayer/]). See {MathML Software - Browsers}[http://www.w3.org/Math/Software/mathml_software_cat_browsers.html] for other browsers. Some formats of comments in HTML document are changed to improve the analysis features. See {parse_f95.rb}[link:files/lib/rdoc-f95/parsers/parse_f95_rb.html]
This is implemented as an "external DSL" in Ruby; that is (like SQL for example), a "program" in a Ruby string is passed into some kind of parser/interpreter method. In this case, it is possible to use the result "as is" or to convert to an ordinary Ruby regular expression. Though this mini-language was conceived and implemented "for Ruby, using Ruby," in principle there is no reason it might not also be implemented in other languages such as Python or Perl. Development on this project began in mid-July 2013. As such, it is still an immature project. Syntax and semantics may change. Feel free to offer comments or suggestions.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.