|
|
24.
|
|
|
BUG: support_uninstall requires write_manifest
|
|
|
This is shown if the config file wants us to include the uninstaller
program with the rest of the files we write to disk, but didn't enable
the manifest support the installer needs. This is a bug the developer
must fix before shipping her installer.
|
|
|
|
|
PUUK: support_uninstall vajab write_manifest 'i
|
|
Translated and reviewed by
aott
|
|
|
|
|
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.
|
|
|
|
|
PUUK: write_manifest vajab Lua parser 'i tuge
|
|
Translated and reviewed by
aott
|
|
|
|
|
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.
|
|
|
|
|
PUUK: Setup.DesktopMenuItem vajab support_uninstall 'i
|
|
Translated and reviewed by
aott
|
|
|
|
|
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.
|
|
|
|
|
PUUK: '%0' ei ole kehtiv loastring
|
|
Translated by
aott
|
|
Reviewed by
aott
|
|
|
|
|
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)
|
|
|
|
|
PUUK: Vigane vormingu() string
|
|
Translated and reviewed by
aott
|
|
|
|
|
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.
|
|
|
|
|
PUUK: etapp tagastas vale tüübi
|
|
Translated and reviewed by
aott
|
|
|
|
|
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.
|
|
|
|
|
PUUK: etapp tagastas vale väärtuse
|
|
Translated and reviewed by
aott
|
|
|
|
|
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.
|
|
|
|
|
PUUK: samm tagasi üle etapi alguse
|
|
Translated by
aott
|
|
Reviewed by
aott
|
|
|
|
|
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.
|
|
|
|
|
PUUK: Käsitlematu andmetüüp
|
|
Translated and reviewed by
aott
|
|
|
|
|
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).
|
|
|
|
|
PUUK: Ei saa duplitseerida tar sisendeid
|
|
Translated and reviewed by
aott
|
|
|
