Translations by Trần Ngọc Quân

Failed to parse message "%s" from dialog process

Error launching metacity-dialog to ask about killing an application: %s

Failed to get hostname: %s

Failed to open X Window System display '%s'

Error launching metacity-dialog to print an error about a command: %s

Failed to scan themes directory: %s

Failed to restart: %s

_Always on Visible Workspace

_Only on This Workspace

Move to Workspace _Left

Move to Workspace R_ight

Move to Workspace _Up

Move to Workspace _Down

Workspace %d

Workspace 1_0

Workspace %s%d

Move to Another _Workspace

There was an error running "%s": %s.

Determines whether applications or the system can generate audible 'beeps'; may be used in conjunction with 'visual bell' to allow silent 'beeps'.

Disable misfeatures that are required by old or broken applications

If true, ignore the titlebar_font option, and use the standard application font for window titles.

If true, trade off usability for less resource usage

Move window one workspace down

Move window one workspace to the left

Move window one workspace to the right

Move window one workspace up

Move window to workspace 1

Move window to workspace 2

Move window to workspace 3

Move window to workspace 4

Show the panel run application dialog

Switch to workspace 1

Switch to workspace 2

Switch to workspace 3

Switch to workspace 4

Tells Metacity how to implement the visual indication that the system bell or another application 'bell' indicator has been rung. Currently there are two valid values, "fullscreen", which causes a fullscreen white-black flash, and "frame_flash" which causes the titlebar of the application which sent the bell signal to flash. If the application which sent the bell is unknown (as is usually the case for the default "system beep"), the currently focused window's titlebar is flashed.

The /apps/metacity/global_keybindings/run_command_N keys define keybindings that correspond to these commands. Pressing the keybinding for run_command_N will execute command_N.

The /apps/metacity/global_keybindings/run_command_screenshot key defines a keybinding which causes the command specified by this setting to be invoked.

The /apps/metacity/global_keybindings/run_command_window_screenshot key defines a keybinding which causes the command specified by this setting to be invoked.

The keybinding that runs the correspondingly-numbered command in /apps/metacity/keybinding_commands The format looks like "<Control>a" or "<Shift><Alt>F1". The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action.

The keybinding that switches to the workspace above the current workspace. The format looks like "<Control>a" or "<Shift><Alt>F1". The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action.

The keybinding that switches to the workspace below the current workspace. The format looks like "<Control>a" or "<Shift><Alt>F1". The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action.

The keybinding that switches to the workspace on the left of the current workspace. The format looks like "<Control>a" or "<Shift><Alt>F1". The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action.

The keybinding that switches to the workspace on the right of the current workspace. The format looks like "<Control>a" or "<Shift><Alt>F1". The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action.

The keybinding that switches to workspace 1. The format looks like "<Control>a" or "<Shift><Alt>F1". The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action.

The keybinding that switches to workspace 10. The format looks like "<Control>a" or "<Shift><Alt>F1". The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action.

The keybinding that switches to workspace 11. The format looks like "<Control>a" or "<Shift><Alt>F1". The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action.

The keybinding that switches to workspace 12. The format looks like "<Control>a" or "<Shift><Alt>F1". The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action.

The keybinding that switches to workspace 2. The format looks like "<Control>a" or "<Shift><Alt>F1". The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action.

The keybinding that switches to workspace 3. The format looks like "<Control>a" or "<Shift><Alt>F1". The parser is fairly liberal and allows lower or upper case, and also abbreviations such as "<Ctl>" and "<Ctrl>". If you set the option to the special string "disabled", then there will be no keybinding for this action.