From 812d7e5767a8f8181d7517fd422213bbfa7d88d2 Mon Sep 17 00:00:00 2001 From: Bill Kendrick Date: Tue, 4 Oct 2022 02:44:39 -0700 Subject: [PATCH] Sync docs after Magic API POT/PO file split --- docs/en/MAGIC-API.txt | 6 ++-- docs/en/html/MAGIC-API.html | 2 +- docs/es_ES.UTF-8/MAGIC-API.txt | 8 ++--- docs/es_ES.UTF-8/html/MAGIC-API.html | 4 +-- docs/fr_FR.UTF-8/ADVANCED-STAMPS-HOWTO.txt | 31 +++++++++---------- docs/fr_FR.UTF-8/MAGIC-API.txt | 14 ++++----- .../html/ADVANCED-STAMPS-HOWTO.html | 4 +-- docs/fr_FR.UTF-8/html/MAGIC-API.html | 12 +++---- docs/gl_ES.UTF-8/MAGIC-API.txt | 16 +++++----- docs/gl_ES.UTF-8/html/MAGIC-API.html | 14 ++++----- docs/ja_JP.UTF-8/ADVANCED-STAMPS-HOWTO.txt | 30 +++++++++++++++--- docs/ja_JP.UTF-8/MAGIC-API.txt | 16 +++++----- .../html/ADVANCED-STAMPS-HOWTO.html | 8 ++--- docs/ja_JP.UTF-8/html/MAGIC-API.html | 14 ++++----- 14 files changed, 98 insertions(+), 81 deletions(-) diff --git a/docs/en/MAGIC-API.txt b/docs/en/MAGIC-API.txt index 46229d805..4673cb03d 100644 --- a/docs/en/MAGIC-API.txt +++ b/docs/en/MAGIC-API.txt @@ -697,9 +697,9 @@ Linux and other Unix-like Platforms The first line sets up Makefile variable ("CFLAGS") that contains flags for the compiler. "-Wall" asks for all compiler warnings to be shown. - "-O2" asks for level 2 optimization. "( tp-magic-config --cflags)" runs - "tp-magic-config" to retrieve additional compiler flags that "Magic" tool - plugins require. (The "$(shell ...)" directive is similar to the ` + "-O2" asks for level 2 optimization. "($shell tp-magic-config --cflags)" + runs "tp-magic-config" to retrieve additional compiler flags that "Magic" + tool plugins require. (The "$(shell ...)" directive is similar to the ` ("grave") character in the BASH shell examples, above.) The next line defines a Makefile target, "my_plugin.so", and states that diff --git a/docs/en/html/MAGIC-API.html b/docs/en/html/MAGIC-API.html index 0694033a0..c278a91bd 100644 --- a/docs/en/html/MAGIC-API.html +++ b/docs/en/html/MAGIC-API.html @@ -763,7 +763,7 @@

- The first line sets up Makefile variable ("CFLAGS") that contains flags for the compiler. "-Wall" asks for all compiler warnings to be shown. "-O2" asks for level 2 optimization. "( tp-magic-config --cflags)" runs "tp-magic-config" to retrieve additional compiler flags that "Magic" tool plugins require. (The "$(shell ...)" directive is similar to the ` ("grave") character in the BASH shell examples, above.)

+ The first line sets up Makefile variable ("CFLAGS") that contains flags for the compiler. "-Wall" asks for all compiler warnings to be shown. "-O2" asks for level 2 optimization. "($shell tp-magic-config --cflags)" runs "tp-magic-config" to retrieve additional compiler flags that "Magic" tool plugins require. (The "$(shell ...)" directive is similar to the ` ("grave") character in the BASH shell examples, above.)

The next line defines a Makefile target, "my_plugin.so", and states that it depends on the C source file "my_plugin.c". (Any time the C file changes, "make" will know to recompile it and produce an updated ".so" file. If the C file hadn't changed, it won't bother recompiling.)

diff --git a/docs/es_ES.UTF-8/MAGIC-API.txt b/docs/es_ES.UTF-8/MAGIC-API.txt index 135d62219..60e94a280 100644 --- a/docs/es_ES.UTF-8/MAGIC-API.txt +++ b/docs/es_ES.UTF-8/MAGIC-API.txt @@ -1,5 +1,5 @@ Tux Paint - versión 0.9.29 + version 0.9.29 Magic Tool Plugin API Documentation @@ -697,9 +697,9 @@ Linux and other Unix-like Platforms The first line sets up Makefile variable ("CFLAGS") that contains flags for the compiler. "-Wall" asks for all compiler warnings to be shown. - "-O2" asks for level 2 optimization. "( tp-magic-config --cflags)" runs - "tp-magic-config" to retrieve additional compiler flags that "Magic" tool - plugins require. (The "$(shell ...)" directive is similar to the ` + "-O2" asks for level 2 optimization. "($shell tp-magic-config --cflags)" + runs "tp-magic-config" to retrieve additional compiler flags that "Magic" + tool plugins require. (The "$(shell ...)" directive is similar to the ` ("grave") character in the BASH shell examples, above.) The next line defines a Makefile target, "my_plugin.so", and states that diff --git a/docs/es_ES.UTF-8/html/MAGIC-API.html b/docs/es_ES.UTF-8/html/MAGIC-API.html index 980f32d05..9c6e73dfd 100644 --- a/docs/es_ES.UTF-8/html/MAGIC-API.html +++ b/docs/es_ES.UTF-8/html/MAGIC-API.html @@ -89,7 +89,7 @@ width="205" height="210" alt="Tux Paint">
- versión 0.9.29 + version 0.9.29

Magic Tool Plugin API Documentation

@@ -763,7 +763,7 @@

- The first line sets up Makefile variable ("CFLAGS") that contains flags for the compiler. "-Wall" asks for all compiler warnings to be shown. "-O2" asks for level 2 optimization. "( tp-magic-config --cflags)" runs "tp-magic-config" to retrieve additional compiler flags that "Magic" tool plugins require. (The "$(shell ...)" directive is similar to the ` ("grave") character in the BASH shell examples, above.)

+ The first line sets up Makefile variable ("CFLAGS") that contains flags for the compiler. "-Wall" asks for all compiler warnings to be shown. "-O2" asks for level 2 optimization. "($shell tp-magic-config --cflags)" runs "tp-magic-config" to retrieve additional compiler flags that "Magic" tool plugins require. (The "$(shell ...)" directive is similar to the ` ("grave") character in the BASH shell examples, above.)

The next line defines a Makefile target, "my_plugin.so", and states that it depends on the C source file "my_plugin.c". (Any time the C file changes, "make" will know to recompile it and produce an updated ".so" file. If the C file hadn't changed, it won't bother recompiling.)

diff --git a/docs/fr_FR.UTF-8/ADVANCED-STAMPS-HOWTO.txt b/docs/fr_FR.UTF-8/ADVANCED-STAMPS-HOWTO.txt index 988c96c89..ee474f952 100644 --- a/docs/fr_FR.UTF-8/ADVANCED-STAMPS-HOWTO.txt +++ b/docs/fr_FR.UTF-8/ADVANCED-STAMPS-HOWTO.txt @@ -244,12 +244,11 @@ Remplacer la frange et les pixels indésirables élargir un peu la sélection et / ou masquer la ligne "fourmis rampantes" qui marque la sélection. - Utilisez l'outil de clonage et l'outil de pinceau. Faites varier - l'opacité selon vos besoins. Utilisez principalement des petites brosses - rondes, peut-être de 3x3 ou 5x5, floues ou non. (Il est généralement - agréable d'associer des pinceaux flous avec une opacité de 100 % et des - pinceaux non flous avec une opacité d'environ 70 %). On peut utiliser - des modes de dessin inhabituels avec des objets semi-transparents. + Use the clone tool and the brush tool. Vary the opacity as needed. Use + small round brushes mostly, perhaps 3x3 or 5x5, fuzzy or not. (It is + generally nice to pair up fuzzy brushes with 100% opacity and non-fuzzy + brushes with about 70% opacity.) Unusual drawing modes can be helpful + with semi-transparent objects. Le but est de supprimer la frange de bord, à la fois à l'intérieur et à l'extérieur de l'objet. La frange intérieure, visible lorsque l'objet @@ -280,17 +279,15 @@ Remplacer la frange et les pixels indésirables Sauvegarder l'image pour Tux Paint - Il est très facile de gâcher votre travail, lui qui vous a demandé - beaucoup d'efforts. Les éditeurs d'images peuvent détruire - silencieusement les pixels dans les zones 0% opaques. Les conditions - dans lesquelles cela se produit peuvent varier d'une version à l'autre. - Si vous êtes très confiant, vous pouvez essayer d'enregistrer votre - image directement au format PNG. Assurez-vous de le relire pour vérifier - que les zones opaques à 0% ne deviennent ni noires ni blanches, ce qui - créerait des franges lorsque Tux Paint réduira l'image. Si vous devez - redimensionner votre image pour gagner de la place (et cacher vos - erreurs), vous êtes presque certain de détruire toutes les zones opaques - à 0%. Alors, voici une meilleure façon... + It is very easy to ruin your hard work. Image editors can silently + destroy pixels in 0% opaque areas. The conditions under which this + happens may vary from version to version. If you are very trusting, you + can try saving your image directly as a PNG. Be sure to read it back in + again to verify that the 0% opaque areas didn't turn black or white, + which would create fringes when Tux Paint scales the image down. If you + need to scale your image to save space (and hide your mistakes), you are + almost certain to destroy all the 0% opaque areas. So here is a better + way... Une façon sûre pour sauvegarder diff --git a/docs/fr_FR.UTF-8/MAGIC-API.txt b/docs/fr_FR.UTF-8/MAGIC-API.txt index 98b0ff508..f9f38473e 100644 --- a/docs/fr_FR.UTF-8/MAGIC-API.txt +++ b/docs/fr_FR.UTF-8/MAGIC-API.txt @@ -3,13 +3,13 @@ Magic Tool Plugin API Documentation - Copyright © 2007-2022 by divers contributeurs; see AUTHORS.txt. + Copyright © 2007-2022 by various contributors; see AUTHORS.txt. https://tuxpaint.org/ octobre 3, 2022 +----------------------------------------------------+ - |Table des matières | + |Table of Contents | |----------------------------------------------------| | * Prequisites | | * Interfaces | @@ -52,7 +52,7 @@ Magic Tool Plugin API Documentation graphics tools, such as GIMP, should be familiar with this plugin concept.) - Prérequis + Prerequisites Tux Paint is written in the C programming language, and uses the Simple DirectMedia Layer library ('libSDL', or simply 'SDL'; available from @@ -697,9 +697,9 @@ Linux and other Unix-like Platforms The first line sets up Makefile variable ("CFLAGS") that contains flags for the compiler. "-Wall" asks for all compiler warnings to be shown. - "-O2" asks for level 2 optimization. "( tp-magic-config --cflags)" runs - "tp-magic-config" to retrieve additional compiler flags that "Magic" tool - plugins require. (The "$(shell ...)" directive is similar to the ` + "-O2" asks for level 2 optimization. "($shell tp-magic-config --cflags)" + runs "tp-magic-config" to retrieve additional compiler flags that "Magic" + tool plugins require. (The "$(shell ...)" directive is similar to the ` ("grave") character in the BASH shell examples, above.) The next line defines a Makefile target, "my_plugin.so", and states that @@ -1044,7 +1044,7 @@ macOS * GNU C Compiler: See "gcc" * grave: The "`" character; used by the BASH shell to use the output of a command as the command-line arguments to another. - * vert: See "RGBA" + * green: See "RGBA" * ->: See "arrow" * .h: See "C header file" * header: See "C header file" diff --git a/docs/fr_FR.UTF-8/html/ADVANCED-STAMPS-HOWTO.html b/docs/fr_FR.UTF-8/html/ADVANCED-STAMPS-HOWTO.html index e5b7390c2..281ac6153 100644 --- a/docs/fr_FR.UTF-8/html/ADVANCED-STAMPS-HOWTO.html +++ b/docs/fr_FR.UTF-8/html/ADVANCED-STAMPS-HOWTO.html @@ -244,7 +244,7 @@ déposez cette couleur dans la sélection, supprimant ainsi la plupart des pixel Pour réduire les accidents, vous souhaiterez peut-être sélectionner uniquement les pixels qui ne sont pas gris dans le masque. (Sélectionnez par couleur dans le masque, choisissez le noir, ajoutez le mode, choisissez le blanc, inversez. Ou bien : sélectionnez tout, sélectionnez par couleur dans le masque, soustrayez le mode, choisissez le noir, choisissez le blanc.) Si vous faites cela, vous voudrez probablement élargir un peu la sélection et / ou masquer la ligne "fourmis rampantes" qui marque la sélection.

- Utilisez l'outil de clonage et l'outil de pinceau. Faites varier l'opacité selon vos besoins. Utilisez principalement des petites brosses rondes, peut-être de 3x3 ou 5x5, floues ou non. (Il est généralement agréable d'associer des pinceaux flous avec une opacité de 100 % et des pinceaux non flous avec une opacité d'environ 70 %). On peut utiliser des modes de dessin inhabituels avec des objets semi-transparents.

+ Use the clone tool and the brush tool. Vary the opacity as needed. Use small round brushes mostly, perhaps 3x3 or 5x5, fuzzy or not. (It is generally nice to pair up fuzzy brushes with 100% opacity and non-fuzzy brushes with about 70% opacity.) Unusual drawing modes can be helpful with semi-transparent objects.

Le but est de supprimer la frange de bord, à la fois à l'intérieur et à l'extérieur de l'objet. La frange intérieure, visible lorsque l'objet est composé de magenta ou de vert, doit être supprimée pour des raisons évidentes. La frange extérieure doit également être supprimée car elle deviendra visible lorsque l'image sera réduite. À titre d'exemple, considérons une région avec 2x2 de pixels au bord d'un objet aux arêtes vives. La moitié gauche est noire et opaque à 0%. La moitié droite est blanche et 100% opaque. Autrement dit, nous avons un objet blanc sur fond noir. Lorsque Tux Paint redimensionne cela à 50% (une zone de 1 x 1 pixel), le résultat sera un pixel opaque gris à 50%. Le résultat correct devrait être un pixel blanc opaque à 50%. Pour obtenir ce résultat, nous devrions peindre les pixels noirs. Ils comptent, bien qu'ils soient à 0 % d'opacité.

@@ -263,7 +263,7 @@ déposez cette couleur dans la sélection, supprimant ainsi la plupart des pixel

- Il est très facile de gâcher votre travail, lui qui vous a demandé beaucoup d'efforts. Les éditeurs d'images peuvent détruire silencieusement les pixels dans les zones 0% opaques. Les conditions dans lesquelles cela se produit peuvent varier d'une version à l'autre. Si vous êtes très confiant, vous pouvez essayer d'enregistrer votre image directement au format PNG. Assurez-vous de le relire pour vérifier que les zones opaques à 0% ne deviennent ni noires ni blanches, ce qui créerait des franges lorsque Tux Paint réduira l'image. Si vous devez redimensionner votre image pour gagner de la place (et cacher vos erreurs), vous êtes presque certain de détruire toutes les zones opaques à 0%. Alors, voici une meilleure façon...

+ It is very easy to ruin your hard work. Image editors can silently destroy pixels in 0% opaque areas. The conditions under which this happens may vary from version to version. If you are very trusting, you can try saving your image directly as a PNG. Be sure to read it back in again to verify that the 0% opaque areas didn't turn black or white, which would create fringes when Tux Paint scales the image down. If you need to scale your image to save space (and hide your mistakes), you are almost certain to destroy all the 0% opaque areas. So here is a better way...

Une façon sûre pour sauvegarder

diff --git a/docs/fr_FR.UTF-8/html/MAGIC-API.html b/docs/fr_FR.UTF-8/html/MAGIC-API.html index 2f1b268fe..e178378fc 100644 --- a/docs/fr_FR.UTF-8/html/MAGIC-API.html +++ b/docs/fr_FR.UTF-8/html/MAGIC-API.html @@ -95,7 +95,7 @@ Magic Tool Plugin API Documentation

- Copyright © 2007-2022 by divers contributeurs; see AUTHORS.txt.
+ Copyright © 2007-2022 by various contributors; see AUTHORS.txt.
https://tuxpaint.org/

@@ -107,12 +107,12 @@ + Table of Contents @@ -162,7 +162,7 @@

- Prérequis

+ Prerequisites

@@ -763,7 +763,7 @@

- The first line sets up Makefile variable ("CFLAGS") that contains flags for the compiler. "-Wall" asks for all compiler warnings to be shown. "-O2" asks for level 2 optimization. "( tp-magic-config --cflags)" runs "tp-magic-config" to retrieve additional compiler flags that "Magic" tool plugins require. (The "$(shell ...)" directive is similar to the ` ("grave") character in the BASH shell examples, above.)

+ The first line sets up Makefile variable ("CFLAGS") that contains flags for the compiler. "-Wall" asks for all compiler warnings to be shown. "-O2" asks for level 2 optimization. "($shell tp-magic-config --cflags)" runs "tp-magic-config" to retrieve additional compiler flags that "Magic" tool plugins require. (The "$(shell ...)" directive is similar to the ` ("grave") character in the BASH shell examples, above.)

The next line defines a Makefile target, "my_plugin.so", and states that it depends on the C source file "my_plugin.c". (Any time the C file changes, "make" will know to recompile it and produce an updated ".so" file. If the C file hadn't changed, it won't bother recompiling.)

@@ -1225,7 +1225,7 @@ grave: The "`" character; used by the BASH shell to use the output of a command as the command-line arguments to another.
  • - vert: + green: See "RGBA"
  • ->: diff --git a/docs/gl_ES.UTF-8/MAGIC-API.txt b/docs/gl_ES.UTF-8/MAGIC-API.txt index 5f026e3a6..b76f89a3d 100644 --- a/docs/gl_ES.UTF-8/MAGIC-API.txt +++ b/docs/gl_ES.UTF-8/MAGIC-API.txt @@ -1,15 +1,15 @@ Tux Paint - versión 0.9.29 + version 0.9.29 Magic Tool Plugin API Documentation - Copyright © 2007-2022 by varios colaboradores; see AUTHORS.txt. + Copyright © 2007-2022 by various contributors; see AUTHORS.txt. https://tuxpaint.org/ - 3 de Outubro de 2022 + Outubro 3, 2022 +----------------------------------------------------+ - |Índice | + |Table of Contents | |----------------------------------------------------| | * Prequisites | | * Interfaces | @@ -697,9 +697,9 @@ Linux and other Unix-like Platforms The first line sets up Makefile variable ("CFLAGS") that contains flags for the compiler. "-Wall" asks for all compiler warnings to be shown. - "-O2" asks for level 2 optimization. "( tp-magic-config --cflags)" runs - "tp-magic-config" to retrieve additional compiler flags that "Magic" tool - plugins require. (The "$(shell ...)" directive is similar to the ` + "-O2" asks for level 2 optimization. "($shell tp-magic-config --cflags)" + runs "tp-magic-config" to retrieve additional compiler flags that "Magic" + tool plugins require. (The "$(shell ...)" directive is similar to the ` ("grave") character in the BASH shell examples, above.) The next line defines a Makefile target, "my_plugin.so", and states that @@ -1044,7 +1044,7 @@ macOS * GNU C Compiler: See "gcc" * grave: The "`" character; used by the BASH shell to use the output of a command as the command-line arguments to another. - * verde: See "RGBA" + * green: See "RGBA" * ->: See "arrow" * .h: See "C header file" * header: See "C header file" diff --git a/docs/gl_ES.UTF-8/html/MAGIC-API.html b/docs/gl_ES.UTF-8/html/MAGIC-API.html index 9cf07f4b4..36ea97d9a 100644 --- a/docs/gl_ES.UTF-8/html/MAGIC-API.html +++ b/docs/gl_ES.UTF-8/html/MAGIC-API.html @@ -89,30 +89,30 @@ width="205" height="210" alt="Tux Paint">
    - versión 0.9.29 + version 0.9.29

    Magic Tool Plugin API Documentation

    - Copyright © 2007-2022 by varios colaboradores; see AUTHORS.txt.
    + Copyright © 2007-2022 by various contributors; see AUTHORS.txt.
    https://tuxpaint.org/

    - 3 de Outubro de 2022

    + Outubro 3, 2022

    • - Table des matières
    + Table of Contents @@ -763,7 +763,7 @@

    - The first line sets up Makefile variable ("CFLAGS") that contains flags for the compiler. "-Wall" asks for all compiler warnings to be shown. "-O2" asks for level 2 optimization. "( tp-magic-config --cflags)" runs "tp-magic-config" to retrieve additional compiler flags that "Magic" tool plugins require. (The "$(shell ...)" directive is similar to the ` ("grave") character in the BASH shell examples, above.)

    + The first line sets up Makefile variable ("CFLAGS") that contains flags for the compiler. "-Wall" asks for all compiler warnings to be shown. "-O2" asks for level 2 optimization. "($shell tp-magic-config --cflags)" runs "tp-magic-config" to retrieve additional compiler flags that "Magic" tool plugins require. (The "$(shell ...)" directive is similar to the ` ("grave") character in the BASH shell examples, above.)

    The next line defines a Makefile target, "my_plugin.so", and states that it depends on the C source file "my_plugin.c". (Any time the C file changes, "make" will know to recompile it and produce an updated ".so" file. If the C file hadn't changed, it won't bother recompiling.)

    @@ -1225,7 +1225,7 @@ grave: The "`" character; used by the BASH shell to use the output of a command as the command-line arguments to another.
  • - verde: + green: See "RGBA"
  • ->: diff --git a/docs/ja_JP.UTF-8/ADVANCED-STAMPS-HOWTO.txt b/docs/ja_JP.UTF-8/ADVANCED-STAMPS-HOWTO.txt index f643625db..d8476abf2 100644 --- a/docs/ja_JP.UTF-8/ADVANCED-STAMPS-HOWTO.txt +++ b/docs/ja_JP.UTF-8/ADVANCED-STAMPS-HOWTO.txt @@ -96,9 +96,18 @@ 一番上のオリジナル画像のレイヤーを表示しながら、作業用レイヤーに対して編集を加えるするように設定します。編集作業の必要に応じて画像を約400％に拡大してください（画像の各ピクセルを画面上 4x4 ピクセルのブロックとして表示し、編集することができます） - 100%不透明な部分と完全に透明な部分を選択します。色を指定することで、オブジェクトや背景をある程度正確に選択できる場合は、そのようにします。部分的に不透明にすべきピクセル（一般的にはオブジェクトの輪郭）を選択しないように、必要に応じて選択範囲を拡大、縮小、反転させます。 + Select parts of the image that need to be 100% opaque or 0% opaque. If + you can select the object or background somewhat accurately by color, do + so. As needed to avoid selecting any pixels that should be partially + opaque (generally at the edge of the object) you should grow, shrink, + and invert the selection. - 不透明な部分を白で、透明な部分を黒で塗りつぶします。この作業は、前景／背景色のインジケータからドラッグ＆ドロップするのが最も簡単です。作業用レイヤーのマスクを編集しながら、変更されていない画像レイヤーを見ているので、見た目には何も起こらないはずですが、サムネイル画像では大きな変更が見えるかもしれません。 + Fill the 100% opaque areas with white, and the 0% opaque areas with + black. This is most easily done by drag-and-drop from the + foreground/background color indicator. You should not see anything + happen, because you are viewing the unmodified image layer while editing + the mask of the WIP layer. Large changes might be noticable in the + thumbnail. 次に、画像を拡大します。 @@ -136,7 +145,11 @@ 失敗を減らすために、マスクの中の灰色ではないピクセルだけを選択するとよいでしょう。（「マスクから色で領域選択、黒を選択、色加算モード、白を選択、反転」あるいは「すべてを選択、マスクから色で領域選択、色減算モード、黒を選択、白を選択」）この作業を行う際、選択範囲を少し広げて、選択領域を示す線を隠したくなるかもしれません。 - ここではクローンツールとブラシツールを使います。必要に応じて不透明度を変えて下さい。3x3か5x5の小さな円形のブラシを主に使います。ぼかし筆かどうかは問いません。（ぼかし筆は不透明度100％、ぼかしではないブラシは不透明度70％程度で組み合わせると良いでしょう）。あまり一般的ではない使い方ですが、半透明のオブジェクトの場合には有効です。 + Use the clone tool and the brush tool. Vary the opacity as needed. Use + small round brushes mostly, perhaps 3x3 or 5x5, fuzzy or not. (It is + generally nice to pair up fuzzy brushes with 100% opacity and non-fuzzy + brushes with about 70% opacity.) Unusual drawing modes can be helpful + with semi-transparent objects. 最終目標は、オブジェクトの内側と外側の両方の縁取りを除去することです。内側の縁取りは、マゼンタやグリーンの上にオブジェクトを合成したときに見えるもので、明らかに除去が必要です。外側のフリンジは、画像を縮小したときに見えるようになるため、こちらも除去する必要があります。例として、鋭角なオブジェクトの輪郭にある2x2のピクセルの領域を考えてみましょう。左半分は黒で、不透明度は0％。右半分は白で、100％不透明です。つまり、黒い背景に白い物体がある状態です。Tux Paintがこれを50％（1x1ピクセルの領域）にスケーリングすると、結果はグレーの50％不透明ピクセルになりますが、正しい結果は、白の50％不透明ピクセルです。この結果を得るためには、黒いピクセルを塗り潰します。不透明度が0％であるにもかかわらず、黒いピクセルは重要です。 @@ -148,8 +161,15 @@ Tux Paint 用の画像の保存 - せっかくの労作も簡単にダメになることがあります。画像編集ソフトは、不透明度0％の領域のピクセルを勝手にで破棄することがあります。この現象が発生する条件は、ソフトウェアのバージョンによっても異なります。慎重を期すため、画像を直接PNGとして保存してみてください。その後、不透明度0％の部分が黒くなったり白くなったりしていないことを確認するために、もう一度画像を読み込んでみてください。ディスクスペースを節約するため（そして自分のミスを隠すため）に画像を縮小する必要がある場合、ほぼ確実に - 0％の不透明部分をすべて破壊してしまうことになります。そこで、もっと良い方法があります。 + It is very easy to ruin your hard work. Image editors can silently + destroy pixels in 0% opaque areas. The conditions under which this + happens may vary from version to version. If you are very trusting, you + can try saving your image directly as a PNG. Be sure to read it back in + again to verify that the 0% opaque areas didn't turn black or white, + which would create fringes when Tux Paint scales the image down. If you + need to scale your image to save space (and hide your mistakes), you are + almost certain to destroy all the 0% opaque areas. So here is a better + way... より安全な保存方法 diff --git a/docs/ja_JP.UTF-8/MAGIC-API.txt b/docs/ja_JP.UTF-8/MAGIC-API.txt index abe084cc2..721a9a989 100644 --- a/docs/ja_JP.UTF-8/MAGIC-API.txt +++ b/docs/ja_JP.UTF-8/MAGIC-API.txt @@ -1,15 +1,15 @@ Tux Paint - バージョン 0.9.29 + version 0.9.29 Magic Tool Plugin API Documentation - Copyright © 2007-2022 by various contributors; AUTHORS.txt 参照. + Copyright © 2007-2022 by various contributors; see AUTHORS.txt. https://tuxpaint.org/ - 2022年10月 3日 + 10月 3, 2022 +----------------------------------------------------+ - |目次 | + |Table of Contents | |----------------------------------------------------| | * Prequisites | | * Interfaces | @@ -697,9 +697,9 @@ Linux and other Unix-like Platforms The first line sets up Makefile variable ("CFLAGS") that contains flags for the compiler. "-Wall" asks for all compiler warnings to be shown. - "-O2" asks for level 2 optimization. "( tp-magic-config --cflags)" runs - "tp-magic-config" to retrieve additional compiler flags that "Magic" tool - plugins require. (The "$(shell ...)" directive is similar to the ` + "-O2" asks for level 2 optimization. "($shell tp-magic-config --cflags)" + runs "tp-magic-config" to retrieve additional compiler flags that "Magic" + tool plugins require. (The "$(shell ...)" directive is similar to the ` ("grave") character in the BASH shell examples, above.) The next line defines a Makefile target, "my_plugin.so", and states that @@ -1044,7 +1044,7 @@ macOS * GNU C Compiler: See "gcc" * grave: The "`" character; used by the BASH shell to use the output of a command as the command-line arguments to another. - * グリーン: See "RGBA" + * green: See "RGBA" * ->: See "arrow" * .h: See "C header file" * header: See "C header file" diff --git a/docs/ja_JP.UTF-8/html/ADVANCED-STAMPS-HOWTO.html b/docs/ja_JP.UTF-8/html/ADVANCED-STAMPS-HOWTO.html index c4d23e171..51b0f3a9d 100644 --- a/docs/ja_JP.UTF-8/html/ADVANCED-STAMPS-HOWTO.html +++ b/docs/ja_JP.UTF-8/html/ADVANCED-STAMPS-HOWTO.html @@ -186,10 +186,10 @@ 一番上のオリジナル画像のレイヤーを表示しながら、作業用レイヤーに対して編集を加えるするように設定します。編集作業の必要に応じて画像を約400％に拡大してください（画像の各ピクセルを画面上 4x4 ピクセルのブロックとして表示し、編集することができます）

    - 100%不透明な部分と完全に透明な部分を選択します。色を指定することで、オブジェクトや背景をある程度正確に選択できる場合は、そのようにします。部分的に不透明にすべきピクセル（一般的にはオブジェクトの輪郭）を選択しないように、必要に応じて選択範囲を拡大、縮小、反転させます。

    + Select parts of the image that need to be 100% opaque or 0% opaque. If you can select the object or background somewhat accurately by color, do so. As needed to avoid selecting any pixels that should be partially opaque (generally at the edge of the object) you should grow, shrink, and invert the selection.

    - 不透明な部分を白で、透明な部分を黒で塗りつぶします。この作業は、前景／背景色のインジケータからドラッグ＆ドロップするのが最も簡単です。作業用レイヤーのマスクを編集しながら、変更されていない画像レイヤーを見ているので、見た目には何も起こらないはずですが、サムネイル画像では大きな変更が見えるかもしれません。

    + Fill the 100% opaque areas with white, and the 0% opaque areas with black. This is most easily done by drag-and-drop from the foreground/background color indicator. You should not see anything happen, because you are viewing the unmodified image layer while editing the mask of the WIP layer. Large changes might be noticable in the thumbnail.

    次に、画像を拡大します。

    @@ -243,7 +243,7 @@ 失敗を減らすために、マスクの中の灰色ではないピクセルだけを選択するとよいでしょう。（「マスクから色で領域選択、黒を選択、色加算モード、白を選択、反転」あるいは「すべてを選択、マスクから色で領域選択、色減算モード、黒を選択、白を選択」）この作業を行う際、選択範囲を少し広げて、選択領域を示す線を隠したくなるかもしれません。

    - ここではクローンツールとブラシツールを使います。必要に応じて不透明度を変えて下さい。3x3か5x5の小さな円形のブラシを主に使います。ぼかし筆かどうかは問いません。（ぼかし筆は不透明度100％、ぼかしではないブラシは不透明度70％程度で組み合わせると良いでしょう）。あまり一般的ではない使い方ですが、半透明のオブジェクトの場合には有効です。

    + Use the clone tool and the brush tool. Vary the opacity as needed. Use small round brushes mostly, perhaps 3x3 or 5x5, fuzzy or not. (It is generally nice to pair up fuzzy brushes with 100% opacity and non-fuzzy brushes with about 70% opacity.) Unusual drawing modes can be helpful with semi-transparent objects.

    最終目標は、オブジェクトの内側と外側の両方の縁取りを除去することです。内側の縁取りは、マゼンタやグリーンの上にオブジェクトを合成したときに見えるもので、明らかに除去が必要です。外側のフリンジは、画像を縮小したときに見えるようになるため、こちらも除去する必要があります。例として、鋭角なオブジェクトの輪郭にある2x2のピクセルの領域を考えてみましょう。左半分は黒で、不透明度は0％。右半分は白で、100％不透明です。つまり、黒い背景に白い物体がある状態です。Tux Paintがこれを50％（1x1ピクセルの領域）にスケーリングすると、結果はグレーの50％不透明ピクセルになりますが、正しい結果は、白の50％不透明ピクセルです。この結果を得るためには、黒いピクセルを塗り潰します。不透明度が0％であるにもかかわらず、黒いピクセルは重要です。

    @@ -262,7 +262,7 @@

    - せっかくの労作も簡単にダメになることがあります。画像編集ソフトは、不透明度0％の領域のピクセルを勝手にで破棄することがあります。この現象が発生する条件は、ソフトウェアのバージョンによっても異なります。慎重を期すため、画像を直接PNGとして保存してみてください。その後、不透明度0％の部分が黒くなったり白くなったりしていないことを確認するために、もう一度画像を読み込んでみてください。ディスクスペースを節約するため（そして自分のミスを隠すため）に画像を縮小する必要がある場合、ほぼ確実に 0％の不透明部分をすべて破壊してしまうことになります。そこで、もっと良い方法があります。

    + It is very easy to ruin your hard work. Image editors can silently destroy pixels in 0% opaque areas. The conditions under which this happens may vary from version to version. If you are very trusting, you can try saving your image directly as a PNG. Be sure to read it back in again to verify that the 0% opaque areas didn't turn black or white, which would create fringes when Tux Paint scales the image down. If you need to scale your image to save space (and hide your mistakes), you are almost certain to destroy all the 0% opaque areas. So here is a better way...

    より安全な保存方法

    diff --git a/docs/ja_JP.UTF-8/html/MAGIC-API.html b/docs/ja_JP.UTF-8/html/MAGIC-API.html index f2c740c9a..1e60cdd99 100644 --- a/docs/ja_JP.UTF-8/html/MAGIC-API.html +++ b/docs/ja_JP.UTF-8/html/MAGIC-API.html @@ -89,30 +89,30 @@ width="205" height="210" alt="Tux Paint">
    - バージョン 0.9.29 + version 0.9.29

    Magic Tool Plugin API Documentation

    - Copyright © 2007-2022 by various contributors; AUTHORS.txt 参照.
    + Copyright © 2007-2022 by various contributors; see AUTHORS.txt.
    https://tuxpaint.org/

    - 2022年10月 3日

    + 10月 3, 2022

    • - Índice
    + Table of Contents @@ -763,7 +763,7 @@

    - The first line sets up Makefile variable ("CFLAGS") that contains flags for the compiler. "-Wall" asks for all compiler warnings to be shown. "-O2" asks for level 2 optimization. "( tp-magic-config --cflags)" runs "tp-magic-config" to retrieve additional compiler flags that "Magic" tool plugins require. (The "$(shell ...)" directive is similar to the ` ("grave") character in the BASH shell examples, above.)

    + The first line sets up Makefile variable ("CFLAGS") that contains flags for the compiler. "-Wall" asks for all compiler warnings to be shown. "-O2" asks for level 2 optimization. "($shell tp-magic-config --cflags)" runs "tp-magic-config" to retrieve additional compiler flags that "Magic" tool plugins require. (The "$(shell ...)" directive is similar to the ` ("grave") character in the BASH shell examples, above.)

    The next line defines a Makefile target, "my_plugin.so", and states that it depends on the C source file "my_plugin.c". (Any time the C file changes, "make" will know to recompile it and produce an updated ".so" file. If the C file hadn't changed, it won't bother recompiling.)

    @@ -1225,7 +1225,7 @@ grave: The "`" character; used by the BASH shell to use the output of a command as the command-line arguments to another.
  • - グリーン: + green: See "RGBA"
  • ->:
    • - 目次