gettext_parser 0.1.0+1

  • Readme
  • Changelog
  • Example
  • Installing
  • 86

Dart gettext mo/po parser #

Parse and compile gettext po and mo files with dart. Ported gettext-parser npm package to dartlang.

Usage #

Add dependency to pubspec.yaml

    gettext_parser: any

Import library:

import 'package:gettext_parser/gettext_parser.dart' as gettextParser;

Parse .po files: #

Map translateTable = gettextParser.po.parse(

Parse .mo files: #

Map translateTable =

Compile .po files: #

String data = gettextParser.po.compile(

Compile .mo files: #

UInt8List data =

Encoding #

gettext_parser use Encoding interface for encoding and decoding charsets from dart:convert package with utf8, base64, latin1 built-in encoders. If you need other encoding you could implement Encoding interface by your own.

Example:, encoding: latin1);
gettextParser.po.parse(buffer, encoding: latin1);

Data structure of parsed mo/po files #

Character set #

Parsed data is always in unicode but the original charset of the file can be found from the charset property.

Headers #

Headers can be found from the headers object, all keys are lowercase and the value for a key is a string. This value will also be used when compiling.

Translations #

Translations can be found from the translations object which in turn holds context objects for msgctxt. Default context can be found from translations[""].

Context objects include all the translations, where msgid value is the key. The value is an object with the following possible properties:

  • msgctxt context for this translation, if not present the default context applies
  • msgid string to be translated
  • msgid_plural the plural form of the original string (might not be present)
  • msgstr an array of translations
  • comments an object with the following properties: translator, reference, extracted, flag, previous.


  "charset": "iso-8859-1",

  "headers": {
    "content-type": "text/plain; charset=iso-8859-1",
    "plural-forms": "nplurals=2; plural=(n!=1);"

  "translations": {
    "": {
      "": {
        "msgid": "",
        "msgstr": ["Content-Type: text/plain; charset=iso-8859-1\n..."]
    "another context": {
      "%s example": {
        "msgctxt": "another context",
        "msgid": "%s example",
        "msgid_plural": "%s examples",
        "msgstr": ["% näide", "%s näidet"],
        "comments": {
          "translator": "This is regular comment",
          "reference": "/path/to/file:123"

Notice that the structure has both a headers object and a "" translation with the header string. When compiling the structure to a mo or a po file, the headers object is used to define the header. Header string in the "" translation is just for reference (includes the original unmodified data) but will not be used when compiling. So if you need to add or alter header values, use only the headers object.

License #


0.0.1 #

  • Initial version


Parse Mo Files: #

import 'package:gettext_parser/gettext_parser.dart' as gettextParser;

Map translateTable =

// with custom encoding
Map translateTable =
    encoding: latin1,

Parse Po Files: #

import 'package:gettext_parser/gettext_parser.dart' as gettextParser;

Map translateTable =

// with custom encoding
Map translateTable =
    encoding: latin1,

Use this package as a library

1. Depend on it

Add this to your package's pubspec.yaml file:

  gettext_parser: ^0.1.0+1

2. Install it

You can install packages from the command line:

with pub:

$ pub get

with Flutter:

$ flutter pub get

Alternatively, your editor might support pub get or flutter pub get. Check the docs for your editor to learn more.

3. Import it

Now in your Dart code, you can use:

import 'package:gettext_parser/gettext_parser.dart';
Describes how popular the package is relative to other packages. [more]
Code health derived from static analysis. [more]
Reflects how tidy and up-to-date the package is. [more]
Weighted score of the above. [more]
Learn more about scoring.

We analyzed this package on Jan 27, 2020, and provided a score, details, and suggestions below. Analysis was completed with status completed using:

  • Dart: 2.7.1
  • pana: 0.13.4

Health issues and suggestions

Document public APIs. (-1 points)

3 out of 3 API elements have no dartdoc comment.Providing good documentation for libraries, classes, functions, and other API elements improves code readability and helps developers find and use your API.

Fix lib/src/po/parser.dart. (-5.84 points)

Analysis of lib/src/po/parser.dart reported 12 hints, including:

line 8 col 7: Unnecessary new keyword.

line 13 col 7: Unnecessary new keyword.

line 16 col 22: Unnecessary new keyword.

line 32 col 33: Unnecessary new keyword.

line 45 col 21: Unnecessary new keyword.

Fix lib/gettext_parser.dart. (-1 points)

Analysis of lib/gettext_parser.dart reported 2 hints:

line 11 col 12: Avoid const keyword.

line 12 col 12: Avoid const keyword.

Fix lib/src/po/compiler.dart. (-0.50 points)

Analysis of lib/src/po/compiler.dart reported 1 hint:

line 38 col 14: Prefer to use whereType on iterable.

Fix additional 4 files with analysis or formatting issues.

Additional issues in the following files:

  • lib/src/models/translation.dart (Run dartfmt to format lib/src/models/translation.dart.)
  • lib/src/utils/generate_header.dart (Run dartfmt to format lib/src/utils/generate_header.dart.)
  • lib/src/utils/parse_header.dart (Run dartfmt to format lib/src/utils/parse_header.dart.)
  • lib/src/utils/upper_case_words.dart (Run dartfmt to format lib/src/utils/upper_case_words.dart.)


Package Constraint Resolved Available
Direct dependencies
Dart SDK >=2.0.0 <3.0.0
Dev dependencies
path ^1.6.2
test ^1.3.4