\\ncontent not translated
';\n\nvar options = {\n // ...snip...\n};\n\nvar errors = I18nLint.scan(context, options);\n```\n\nThe scan function can also accept a `fileName` parameter:\n\n```javascript\nvar I18nLint = require('i18n-lint');\n\nvar stdin = '';\n\n// Read stdin stream\n// ...snip...\n\n// Once stdin has finished...\nvar errors = I18nLint(context, options, 'stdin');\n```\n\nThis allows more meaningful output when the reporters print a filename.\n\n#### Options\n\nOptions are passed as an object, as the second parameter to `i18n-lint`.\n\n##### `templateDelimiters`\n###### type: `Array`, default: `[]`\n\nSpecify the start and end template delimiters which the source files use. We can specify\nmultiple delimiters if needed. For example, when linting EJS files:\n\n```javascript\n I18nLint('file.ejs', {\n templateDelimiters: [['<%', '%>']]\n });\n```\n\n##### `attributes`\n###### type: `Array`, default: `['alt', 'placeholder', 'title']`\n\nSpecify which HTML attributes to check when searching for hardcoded strings.\n\n##### `ignoreTags`\n###### type: `Array`, default: `['style', 'script', 'pre', 'code']`\n\nAn array of tags which should be ignored when searching for hardcoded strings.\n\n#### Using Reporters\n\nWhen using `i18n-lint` as a library, you can still use the reporters:\n\n```javascript\nconsole.log(I18nLint.reporters);\n// {\n// default: [Function]\n// }\n\nvar reporter = I18nLint.reporters.default;\nvar errors = I18nLint('file.html', {});\n\nreporter(errors);\n```\n\nThere are currently 3 built-in reporters: `default`, `unix` and `json`.\n\nTo use other reporters, simply require them:\n\n```javascript\nvar I18nLint = require('i18n-lint');\nvar reporter = require('i18n-lint-awesome-reporter');\n\nreporter(I18nLint('file.html', {}));\n```\n\n#### Error Format\n\n```javascript\n{\n file: '', // string, file which contains the errors,\n error: {\n id: String, // usually '(error)'\n code: String, // warning code (see Warning Numbers)\n reason: String, // message describing the error\n evidence: RegExp, // with the offending text in match groups\n line: Number, // line number of the error\n character: Number, // column where evidence begins\n scope: String // where the error was found\n }\n}\n```\n\n### Grunt\n\nThere is a grunt task which wraps `i18n-lint`'s functionality, which\ncan be found at