gettext-extractor

Features

• New option transformSource for parse* methods, which allows pre-processing of source code

Breaking Changes

• The POT output format has changed a bit
  There have been a few improvements to the output - see Improvements below.
• toPotString has been renamed to getPotString
• toGettextMessages has been removed
  Use the new methods instead: getMessages, getContexts and getMessagesByContext

Features

• Support for setting PO headers
• New methods for retrieving extracted messages: getMessages, getContexts and getMessagesByContext

Improvements

• By default the Content-Type PO header is set to text/plain; charset=UTF-8
• Plurals have a msgstr[1] "" in the POT output #5
• File references are sorted alphabetically in the POT output

Bugfixes

• Prevent &, < and > from being escaped as HTML entities
• Preserve messages with empty string as text

Features

• More intelligent extraction of comments from JavaScript code

Breaking Changes

• functionCall and methodCall have been replaced by JsExtractors.callExpression
• Node.js version 6 or higher is now required
• Passing null for optional arguments will throw an error

Features

• HTML support
• More flexible extraction of call expression with JsExtractors.callExpression
• Support for glob options in parseFilesGlob
• Parse options that allow setting the starting line number and more
• Save to .pot file asynchronously with savePotFileAsync

Bugfixes

• Let TypeScript parser infer script kind from filename
  This resolves issues with TypeScript casts (like <any>) being treated
  as JSX elements which can result in missing messages.

Bugfixes

• Fix character encoding issue #1

Inital public release of the Gettext Extractor