|
|
10.
|
|
|
(%0-%1 of %2 lines, see more?)
|
|
|
This is shown when using stdio UI's built-in README pager, to
show what range of lines of text are being displayed (%0 is first
line, %1 is last line, %2 is the total number of lines of text).
|
|
|
|
|
(no translation yet)
|
|
|
|
|
11.
|
|
|
Type '%0' to go back.
|
|
|
The stdio UI uses this sentence in the prompt if the user is able
to return to a previous stage of installation (from the options
section to the "choose installation destination" section, etc).
|
|
|
|
|
(no translation yet)
|
|
|
|
|
21.
|
|
|
B_rowse...
|
|
|
This is a GTK+ button label. The '_' comes before the hotkey character.
"Back" might be using 'B' in English. This button brings up a file
dialog where the end-user can navigate to and select files.
|
|
|
|
|
(no translation yet)
|
|
|
|
|
22.
|
|
|
BUG: duplicate media id
|
|
|
All the "BUG:" strings are generally meant to be seen by developers,
not end users. They represent programming errors and configuration
file problems.
This is shown if the configuration file has specified two cd-roms (or
whatever) with the same media id, which is a bug the developer must
fix before shipping her installer.
"media id" refers to Setup.Media.id in the config file. It's not meant
to be a proper name, in this case.
|
|
|
|
|
(no translation yet)
|
|
|
|
|
23.
|
|
|
BUG: no options
|
|
|
This is shown if the configuration file has no installable options,
either because none are listed or they've all become disabled, which
is a bug the developer must fix before shipping her installer.
|
|
|
|
|
(no translation yet)
|
|
|
|
|
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.
|
|
|
|
|
(no translation yet)
|
|
|
|
|
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.
|
|
|
|
|
(no translation yet)
|
|
|
|
|
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.
|
|
|
|
|
(no translation yet)
|
|
|
|
|
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.
|
|
|
|
|
(no translation yet)
|
|
|
|
|
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)
|
|
|
|
|
(no translation yet)
|
|
|
