Þ•¼\Ð<ÑM1\Ž1©>Û4HOF˜]ß.=1l†ž|%)¢$Ì-ñGggEÏ = NS 2¢ Õ 2ñ ?$ 5d Jš Hå _. 0Ž 3¿ ‡ó }{*ù%$.JHyi    Alpha value "%s" in blended color is not between 0.0 and 1.0Blend format is "blend/bg_color/fg_color/alpha", "%s" does not fit the formatCould not parse alpha value "%s" in blended colorCould not parse color "%s"Could not parse shade factor "%s" in shaded colorDid not understand color component "%s" in color specificationDid not understand state "%s" in color specificationError launching metacity-dialog to ask about killing an application: %s Error launching metacity-dialog to print an error about a command: %s Error launching metacity-dialog to warn about apps that don't support session management: %s Error reading from dialog display process: %s Failed to parse message "%s" from dialog process GTK color specification must have a close bracket after the state, e.g. gtk:fg[NORMAL] where NORMAL is the state; could not parse "%s"GTK color specification must have the state in brackets, e.g. gtk:fg[NORMAL] where NORMAL is the state; could not parse "%s"Gradients should have at least two colorsNo "color" attribute on element <%s>Shade factor "%s" in shaded color is negativeShade format is "shade/base_color/factor", "%s" does not fit the formatSome applications break specifications in ways that result in window manager misfeatures. For example, ideally Metacity would place all dialogs in a consistent position with respect to their parent window. This requires ignoring application-specified positions for dialogs. But some versions of Java/Swing mark their popup menus as dialogs, so Metacity has to disable dialog positioning to allow menus to work in broken Java applications. There are several other examples like this. This option puts Metacity in full-on Correct mode, which perhaps gives a moderately nicer UI if you don't need to run any broken apps. Sadly, workarounds must be enabled by default; the real world is an ugly place. Some of the workarounds are workarounds for limitations in the specifications themselves, so sometimes a bug in no-workarounds mode won't be fixable without amending a spec.Project-Id-Version: metacity Report-Msgid-Bugs-To: POT-Creation-Date: 2004-01-02 17:19+0100 PO-Revision-Date: 2002-10-15 23:19+0000 Last-Translator: Robert Brady , Bastien Nocera Language-Team: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Alpha value "%s" in blended colour is not between 0.0 and 1.0Blend format is "blend/bg_colour/fg_color/alpha", "%s" does not fit the formatCould not parse alpha value "%s" in blended colourCould not parse colour "%s"Could not parse shade factor "%s" in shaded colourDid not understand colour component "%s" in color specificationDid not understand state "%s" in colour specificationError launching metacity-dialogue to ask about killing an application: %s Error launching metacity-dialogue to print an error about a command: %s Error launching metacity-dialogue to warn about apps that don't support session management: %s Error reading from dialogue display process: %s Failed to parse message "%s" from dialogue process GTK colour specification must have a close bracket after the state, e.g. gtk:fg[NORMAL] where NORMAL is the state; could not parse "%s"GTK colour specification must have the state in brackets, e.g. gtk:fg[NORMAL] where NORMAL is the state; could not parse "%s"Gradients should have at least two coloursNo "colour" attribute on element <%s>Shade factor "%s" in shaded colour is negativeShade format is "shade/base_colour/factor", "%s" does not fit the formatSome applications break specifications in ways that result in window manager misfeatures. For example, ideally Metacity would place all dialogues in a consistent position with respect to their parent window. This requires ignoring application-specified positions for dialogs. But some versions of Java/Swing mark their popup menus as dialogs, so Metacity has to disable dialog positioning to allow menus to work in broken Java applications. There are several other examples like this. This option puts Metacity in full-on Correct mode, which perhaps gives a moderately nicer UI if you don't need to run any broken apps. Sadly, workarounds must be enabled by default; the real world is an ugly place. Some of the workarounds are workarounds for limitations in the specifications themselves, so sometimes a bug in no-workarounds mode won't be fixable without amending a spec.