|
|
25.
|
|
|
BUG: write_manifest requires Lua parser support
|
|
|
This is shown if the config file wants us to install a manifest (a list
of everything we wrote to disk) but didn't enable Lua parser support
in the binary, which they need to handle Lua source code without
compiling it first (as it needs to be "parsed")...the manifest is
ultimately just an uncompiled Lua program that the installer generates.
This is a bug the developer must fix before shipping her installer.
|
|
|
|
|
Kewer: write_manifest vereis Lua omskakelaar ondersteuning
|
|
Translated and reviewed by
scipher
|
|
|
|
|
26.
|
|
|
BUG: Setup.DesktopMenuItem requires support_uninstall
|
|
|
This is shown if the config file wants us to add desktop menu items
but uninstaller support isn't enabled. It is considered bad taste
to add system menu items without a way to remove them. This is
a bug the developer must fix before shipping her installer.
|
|
|
|
|
Kewer: Setup.DesktopMenuItem vereis support_uninstall
|
|
Translated and reviewed by
scipher
|
|
|
|
|
27.
|
|
|
BUG: '%0' is not a valid permission string
|
|
|
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.
|
|
|
|
|
Kewer: '%0' is nie 'n geldige toestemming string nie
|
|
Translated and reviewed by
scipher
|
|
|
|
|
28.
|
|
|
BUG: Invalid format() string
|
|
|
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)
|
|
|
|
|
Kewer: Ongeldige format() string
|
|
Translated and reviewed by
scipher
|
|
|
|
|
29.
|
|
|
BUG: stage returned wrong type
|
|
|
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.
|
|
|
|
|
Kewer: stage het 'n verkeerde tipe terug gevoer
|
|
Translated and reviewed by
scipher
|
|
|
|
|
30.
|
|
|
BUG: stage returned wrong value
|
|
|
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.
|
|
|
|
|
Kewer: Fase het 'n verkeerde waarde terug gevoer
|
|
Translated and reviewed by
scipher
|
|
|
|
|
31.
|
|
|
BUG: stepped back over start of stages
|
|
|
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.
|
|
|
|
|
Kewer: terug gestap verby die begin van die fases
|
|
Translated and reviewed by
scipher
|
|
|
|
|
32.
|
|
|
BUG: Unhandled data type
|
|
|
This happens if there's an unusual case when writing out Lua scripts
to disk. This should never be seen by an end-user.
|
|
|
|
|
BUG: Ongehanteerde data tipe
|
|
Translated by
Darryl Smith
|
|
Reviewed by
Darryl Smith
|
|
|
|
|
33.
|
|
|
BUG: Can't duplicate tar inputs
|
|
|
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).
|
|
|
|
|
Kewer: Kan nie tar toevoere dupliseer nie
|
|
Translated and reviewed by
scipher
|
|
|
|
|
34.
|
|
|
BUG: Unexpected value
|
|
|
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...)
|
|
|
|
|
Kewer: Onverwagte waarde
|
|
Translated and reviewed by
scipher
|
|
|
