hmLoadTopic({
hmKeywords:"grammar,grammar using,syntax highlighting",
hmTitle:"Grammars",
hmDescription:"A file format specification can include a grammar definition, used for syntax highlighting, and to help define which differences are important.",
hmPrevLink:"file_formats.html",
hmNextLink:"dlgreport.html",
hmParentLink:"file_formats.html",
hmBreadCrumbs:"<a href=\"using_bc.html\">Using Beyond Compare<\/a> &gt; <a href=\"file_formats.html\">File Formats<\/a>",
hmTitlePath:"Using Beyond Compare > File Formats > Grammars",
hmHeader:"<h1 class=\"p_Heading1\"><span class=\"f_Heading1\">Grammars<\/span><\/h1>\n\r",
hmBody:"<p class=\"p_Normal\">A file format specification can include a grammar definition, used for syntax highlighting, and to help define which differences are important.<\/p>\n\r<p class=\"p_Normal\">For example, our standard file format for C\/C++ source code includes a grammar that recognizes keywords, comments, and literal strings.  By <a href=\"rules_vs_file_formats.html\" class=\"topiclink\">flagging differences in comments as unimportant<\/a>, you can better concentrate on important differences.<\/p>\n\r<p class=\"p_Normal\">A grammar definition in Beyond Compare is fairly simplistic.  It does not support nested or context-specific definitions, so it doesn\'t handle tagged languages like HTML and PHP very well.<\/p>\n\r<p class=\"p_Normal\">To edit a grammar, pick <span class=\"f_Command\">Tools &gt; File Formats<\/span> <img style=\"margin:0;width:1.0000rem;height:1.0000rem;border:none\" src=\".\/images\/fileformatmanager.png\"\/> and find the appropriate file format.  Switch to the <span class=\"f_Command\">Grammar<\/span> tab and <a href=\"dlgtextgrammaritem.html\" class=\"topiclink\">edit the grammar items<\/a>.<\/p>\n\r"
})
