Browsing German translation

This is a file's permissions. Programmers give these as strings, and
if one isn't valid, the program will report this. So, on Unix, they
might specify "0600" as a valid string, but "sdfksjdfk" wouldn't be
valid and would cause this error.

If there's a string in the program that needs be formatted with
%0, %1, etc, and it specifies an invalid sequence like "%z", this
error pops up to inform the programmer/translator.
"format()" is a proper name in this case (program function name)

The program runs in "stages" and as it transitions from one stage to
another, it has to report some data about what happened during the
stage. A programming bug may cause unexpected type of data to be
reported, causing this error to pop up.

The program runs in "stages" and as it transitions from one stage to
another, it has to report some data about what happened during the
stage. A programming bug may cause unexpected information to be
reported, causing this error to pop up.

The program runs in "stages", which can in many cases be revisited
by the user clicking the "Back" button. If the program has a bug
that allows the user to click "Back" on the initial stage, this
error pops up.

This happens if there's an unusual case when writing out Lua scripts
to disk. This should never be seen by an end-user.

This is triggered by a logic bug in the i/o subsystem.
This should never be seen by an end-user.
"tar" is a proper name in this case (it's a file format).

This is a generic error message when a programming bug produced a
result we weren't expecting (a negative number when we expected
positive, etc...)

Buggy config elements:
This is supposed to be a config element (%0) and something that's wrong
with it (%1), such as "BUG: Config Package::description not a string"
The grammar can be imperfect here; this is a developer error, not an
end-user error, so we haven't made this very flexible.

This is an error string for a buggy config element. See notes above.