String additions to 'glib.glib-2-14'

[GNOME Status Pages <danilo gnome org>]

This is an automatic notification from status generation scripts on:
    http://l10n.gnome.org/.

There have been following string additions to module 'glib.glib-2-14':

    + "(?R or (?[+-]digits must be followed by )"
    + "DEFINE group contains more than one branch"
    + "POSIX collating elements are not supported"
    + "POSIX named classes are supported only within a class"
    + "\\ at end of pattern"
    + "\\C not allowed in lookbehind assertion"
    + "\\c at end of pattern"
    + "\\g is not followed by a braced name or an optionally braced non-zero number"
    + "assertion expected after (?("
    + "case changing escapes are not allowed here"
    + "character value in \\x{...} sequence is too large"
    + "code overflow"
    + "conditional group contains more than two branches"
    + "failed to get memory"
    + "inconsistent NEWLINE options"
    + "invalid condition (?(0)"
    + "invalid escape sequence in character class"
    + "lookbehind assertion is not fixed length"
    + "malformed \\P or \\p sequence"
    + "malformed number or name after (?("
    + "missing ) after comment"
    + "missing terminating ] for character class"
    + "missing terminator in subpattern name"
    + "nothing to repeat"
    + "number too big in {} quantifier"
    + "numbers out of order in {} quantifier"
    + "octal value is greater than \\377"
    + "overran compiling workspace"
    + "previously-checked referenced subpattern not found"
    + "range out of order in character class"
    + "recursive call could loop indefinitely"
    + "reference to non-existent subpattern"
    + "regular expression too large"
    + "repeating a DEFINE group is not allowed"
    + "subpattern name is too long (maximum 32 characters)"
    + "too many named subpatterns (maximum 10,000)"
    + "two named subpatterns have the same name"
    + "unexpected repeat"
    + "unknown POSIX class name"
    + "unknown property name after \\P or \\p"
    + "unrecognized character after (?"
    + "unrecognized character after (?<"
    + "unrecognized character after (?P"
    + "unrecognized character follows \\"

Note that this doesn't directly indicate a string freeze break, but it
might be worth investigating.