r22771 by jghali - Uniformize presentation of scripter's constants
scribus-commit
scribus-commit at lists.scribus.net
Sun Nov 18 00:35:27 UTC 2018
Author: jghali
Date: Sun Nov 18 00:35:27 2018
New Revision: 22771
URL: http://scribus.net/websvn/listing.php?repname=Scribus&sc=1&rev=22771
Log:
Uniformize presentation of scripter's constants
Modified:
trunk/Scribus/doc/de/scripterapi-constants.html
trunk/Scribus/doc/en/scripterapi-constants.html
trunk/Scribus/doc/fr/scripterapi-constants.html
trunk/Scribus/doc/it/scripterapi-constants.html
Modified: trunk/Scribus/doc/de/scripterapi-constants.html
URL: http://scribus.net/websvn/diff.php?repname=Scribus&rev=22771&path=/trunk/Scribus/doc/de/scripterapi-constants.html
==============================================================================
--- trunk/Scribus/doc/de/scripterapi-constants.html (original)
+++ trunk/Scribus/doc/de/scripterapi-constants.html Sun Nov 18 00:35:27 2018
@@ -14,7 +14,7 @@
<h4>Scribus Version:</h4>
<p>The script interface provides two variables containing the current Scribus version in the <code>scribus</code> module. Scripts can use these variables to check that they're running under the version of Scribus they expect, and to report information about incompatibilities to the user. These two variables, <code>scribus_version</code> and <code>scribus_version_info</code>, were added in 1.2.1 and 1.3.0svn and will not be present in earlier versions. If you need to, you can check for their presence with <code>hasattr(scribus, 'scribus_version')</code>.</p>
<p><code>scribus_version</code> contains the current Scribus version as a string. It will usually look like <code>'1.2.1svn'</code> or <code>'1.3.0'</code>, for example, but is not guaranteed to always follow that format. This variable is useful when you need to display the version to the user, for example when reporting an incompatibility. Do not parse or compare this variable, that is what <code>scribus_version_info</code> is for.</p>
- <p><code>scribus_version_info</code> is a tuple similar to the <code>sys.version_info</code> tuple provided by Python. It is a tuple of the form (majorversion, minorversion, patchlevel, extraversion, build) for example, 1.2.1svn will have <code>(1,2,1,'svn',0)</code> and 1.3.2 will have <code>(1,3,2,'',0)<code> . These tuples are ideal for checking for minimum versions, etc, because Python compares tuples element-by-element, left-to-right. For example:</p>
+ <p><code>scribus_version_info</code> is a tuple similar to the <code>sys.version_info</code> tuple provided by Python. It is a tuple of the form (majorversion, minorversion, patchlevel, extraversion, build) for example, 1.2.1svn will have <code>(1,2,1,'svn',0)</code> and 1.3.2 will have <code>(1,3,2,'',0)</code> . These tuples are ideal for checking for minimum versions, etc, because Python compares tuples element-by-element, left-to-right. For example:</p>
<pre>
if scribus.scribus_version_info[:3] < (1,2,2):
messageBox("Scribus - Python script",
@@ -27,6 +27,7 @@
<h4>Unit Enumeration Constants: </h4>
+<table><tr><td>
<dl>
<dt>UNIT_POINTS</dt>
<dd>Measurement Unit Point = 0</dd>
@@ -37,6 +38,7 @@
<dt>UNIT_PICAS</dt>
<dd>Measurement Unit Pica = 3</dd>
</dl>
+</td></tr></table>
<h4>Unit Conversion Constants</h4>
@@ -45,6 +47,7 @@
convert points to inches you write 'value*inch', and to convert inches to mm
you write 'value*mm/inch' .</p>
+<table><tr><td>
<dl>
<dt>pt</dt>
<dd>points in 1 pt</dd>
@@ -59,14 +62,17 @@
<dt>...</dt>
<dd>Other constants will be provided if the Scribus core knows about them.</dd>
</dl>
+</td></tr></table>
<h4>Page Orientation Definitions: </h4>
+<table><tr><td>
<dl>
<dt>PORTRAIT</dt>
<dd>Page orientation Portrait = 0</dd>
<dt>LANDSCAPE</dt>
<dd>Page orientation Landscape = 1</dd>
</dl>
+</td></tr></table>
<h4>Definitions for Page Formats: </h4>
<p>If you are using these, it's important to understand that these constants are simply tuples of these specific numbers. There are now two sets of these constants for A and B series of paper formats.</p>
@@ -188,6 +194,7 @@
</table>
<h4>Definitions for Document Layout:</h4>
+<table><tr><td>
<dl>
<dt>FACINGPAGES</dt>
<dd>Layout with facing Pages.</dd>
@@ -198,10 +205,12 @@
<dt>FIRSTPAGERIGHT</dt>
<dd>The first Page of the Document is a right Page.</dd>
</dl>
+</td></tr></table>
<h4>Alignment Definitions: </h4>
-<dl>
- <dt>ALIGN_LEFTK</dt>
+<table><tr><td>
+<dl>
+ <dt>ALIGN_LEFT</dt>
<dd>Text is aligned to the Left.</dd>
<dt>ALIGN_CENTERED</dt>
<dd>The Text is centered in the Textframe.</dd>
@@ -212,8 +221,10 @@
<dt>ALIGN_BLOCK</dt>
<dd>The Text has block Alignment</dd>
</dl>
+</td></tr></table>
<h4>Vertical alignment Definitions: </h4>
+<table><tr><td>
<dl>
<dt>ALIGNV_TOP</dt>
<dd>Text is aligned vertically to the top.</dd>
@@ -222,8 +233,10 @@
<dt>ALIGNV_BOTTOM</dt>
<dd>Text is aligned vertically to the bottom.</dd>
</dl>
+</td></tr></table>
<h4>Line related Definitions: </h4>
+<table><tr><td>
<dl>
<dt>LINE_DASH</dt>
<dt>LINE_DASHDOT</dt>
@@ -239,8 +252,10 @@
<dt>CAP_ROUND</dt>
<dt>CAP_SQUARE</dt>
</dl>
+</td></tr></table>
<h4>Fill related Definitions: </h4>
+<table><tr><td>
<dl>
<dt>FILL_NOG</dt>
<dd>No gradient, plain color</dd>
@@ -250,6 +265,7 @@
<dt>FILL_CROSSDIAGONALG</dt>
<dt>FILL_RADIALG</dt>
</dl>
+</td></tr></table>
<h4>Dialog Buttons</h4>
<p>
@@ -270,12 +286,14 @@
<p>For example, even if you assign CANCEL to button1, RETRY to button2, and YES to button3, they will appear YES, RETRY, and CANCEL left to right in the dialog.</p>
<h4>Dialog Icons</h4>
+<table><tr><td>
<dl>
<dt>ICON_CRITICAL</dt>
<dt>ICON_INFORMATION</dt>
<dt>ICON_NONE</dt>
<dt>ICON_WARNING</dt>
</dl>
+</td></tr></table>
</body>
</html>
Modified: trunk/Scribus/doc/en/scripterapi-constants.html
URL: http://scribus.net/websvn/diff.php?repname=Scribus&rev=22771&path=/trunk/Scribus/doc/en/scripterapi-constants.html
==============================================================================
--- trunk/Scribus/doc/en/scripterapi-constants.html (original)
+++ trunk/Scribus/doc/en/scripterapi-constants.html Sun Nov 18 00:35:27 2018
@@ -14,7 +14,7 @@
<h4>Scribus Version:</h4>
<p>The script interface provides two variables containing the current Scribus version in the <code>scribus</code> module. Scripts can use these variables to check that they're running under the version of Scribus they expect, and to report information about incompatibilities to the user. These two variables, <code>scribus_version</code> and <code>scribus_version_info</code>, were added in 1.2.1 and 1.3.0svn and will not be present in earlier versions. If you need to, you can check for their presence with <code>hasattr(scribus, 'scribus_version')</code>.</p>
<p><code>scribus_version</code> contains the current Scribus version as a string. It will usually look like <code>'1.2.1svn'</code> or <code>'1.3.0'</code>, for example, but is not guaranteed to always follow that format. This variable is useful when you need to display the version to the user, for example when reporting an incompatibility. Do not parse or compare this variable, that is what <code>scribus_version_info</code> is for.</p>
- <p><code>scribus_version_info</code> is a tuple similar to the <code>sys.version_info</code> tuple provided by Python. It is a tuple of the form (majorversion, minorversion, patchlevel, extraversion, build) for example, 1.2.1svn will have <code>(1,2,1,'svn',0)</code> and 1.3.2 will have <code>(1,3,2,'',0)<code> . These tuples are ideal for checking for minimum versions, etc, because Python compares tuples element-by-element, left-to-right. For example:</p>
+ <p><code>scribus_version_info</code> is a tuple similar to the <code>sys.version_info</code> tuple provided by Python. It is a tuple of the form (majorversion, minorversion, patchlevel, extraversion, build) for example, 1.2.1svn will have <code>(1,2,1,'svn',0)</code> and 1.3.2 will have <code>(1,3,2,'',0)</code> . These tuples are ideal for checking for minimum versions, etc, because Python compares tuples element-by-element, left-to-right. For example:</p>
<pre>
if scribus.scribus_version_info[:3] < (1,2,2):
messageBox("Scribus - Python script",
@@ -27,6 +27,7 @@
<h4>Unit Enumeration Constants: </h4>
+<table><tr><td>
<dl>
<dt>UNIT_POINTS</dt>
<dd>Measurement Unit Point = 0</dd>
@@ -37,6 +38,7 @@
<dt>UNIT_PICAS</dt>
<dd>Measurement Unit Pica = 3</dd>
</dl>
+</td></tr></table>
<h4>Unit Conversion Constants</h4>
@@ -45,6 +47,7 @@
convert points to inches you write 'value*inch', and to convert inches to mm
you write 'value*mm/inch' .</p>
+<table><tr><td>
<dl>
<dt>pt</dt>
<dd>points in 1 pt</dd>
@@ -59,14 +62,17 @@
<dt>...</dt>
<dd>Other constants will be provided if the Scribus core knows about them.</dd>
</dl>
+</td></tr></table>
<h4>Page Orientation Definitions: </h4>
+<table><tr><td>
<dl>
<dt>PORTRAIT</dt>
<dd>Page orientation Portrait = 0</dd>
<dt>LANDSCAPE</dt>
<dd>Page orientation Landscape = 1</dd>
</dl>
+</td></tr></table>
<h4>Definitions for Page Formats: </h4>
<p>If you are using these, it's important to understand that these constants are simply tuples of these specific numbers. There are now two sets of these constants for A and B series of paper formats.</p>
@@ -188,6 +194,7 @@
</table>
<h4>Definitions for Document Layout:</h4>
+<table><tr><td>
<dl>
<dt>FACINGPAGES</dt>
<dd>Layout with facing Pages.</dd>
@@ -198,10 +205,12 @@
<dt>FIRSTPAGERIGHT</dt>
<dd>The first Page of the Document is a right Page.</dd>
</dl>
+</td></tr></table>
<h4>Alignment Definitions: </h4>
-<dl>
- <dt>ALIGN_LEFTK</dt>
+<table><tr><td>
+<dl>
+ <dt>ALIGN_LEFT</dt>
<dd>Text is aligned to the Left.</dd>
<dt>ALIGN_CENTERED</dt>
<dd>The Text is centered in the Textframe.</dd>
@@ -212,8 +221,10 @@
<dt>ALIGN_BLOCK</dt>
<dd>The Text has block Alignment</dd>
</dl>
+</td></tr></table>
<h4>Vertical alignment Definitions: </h4>
+<table><tr><td>
<dl>
<dt>ALIGNV_TOP</dt>
<dd>Text is aligned vertically to the top.</dd>
@@ -222,8 +233,10 @@
<dt>ALIGNV_BOTTOM</dt>
<dd>Text is aligned vertically to the bottom.</dd>
</dl>
+</td></tr></table>
<h4>Line related Definitions: </h4>
+<table><tr><td>
<dl>
<dt>LINE_DASH</dt>
<dt>LINE_DASHDOT</dt>
@@ -239,8 +252,10 @@
<dt>CAP_ROUND</dt>
<dt>CAP_SQUARE</dt>
</dl>
+</td></tr></table>
<h4>Fill related Definitions: </h4>
+<table><tr><td>
<dl>
<dt>FILL_NOG</dt>
<dd>No gradient, plain color</dd>
@@ -250,6 +265,7 @@
<dt>FILL_CROSSDIAGONALG</dt>
<dt>FILL_RADIALG</dt>
</dl>
+</td></tr></table>
<h4>Dialog Buttons</h4>
<p>
@@ -270,12 +286,14 @@
<p>For example, even if you assign CANCEL to button1, RETRY to button2, and YES to button3, they will appear YES, RETRY, and CANCEL left to right in the dialog.</p>
<h4>Dialog Icons</h4>
+<table><tr><td>
<dl>
<dt>ICON_CRITICAL</dt>
<dt>ICON_INFORMATION</dt>
<dt>ICON_NONE</dt>
<dt>ICON_WARNING</dt>
</dl>
+</td></tr></table>
</body>
</html>
Modified: trunk/Scribus/doc/fr/scripterapi-constants.html
URL: http://scribus.net/websvn/diff.php?repname=Scribus&rev=22771&path=/trunk/Scribus/doc/fr/scripterapi-constants.html
==============================================================================
--- trunk/Scribus/doc/fr/scripterapi-constants.html (original)
+++ trunk/Scribus/doc/fr/scripterapi-constants.html Sun Nov 18 00:35:27 2018
@@ -20,7 +20,7 @@
<p><code>scribus_version_info</code> est un vecteur semblable au vecteur <code>sys.version_info</code> fourni par Python.
C'est un vecteur de la forme (majorversion, minorversion, patchlevel,
extraversion, build), par exemple 1.2.1cvs correspond à
-<code>(1,2,1,'cvs',0)</code> et 1.3.2 correspond à <code>(1,3,2,'',0)<code> . Ces vecteurs sont idéaux pour vérifier les versions minimum, etc., parce que Python compare les vecteurs élément par élément, de gauche à droite. Par exemple :</p>
+<code>(1,2,1,'cvs',0)</code> et 1.3.2 correspond à <code>(1,3,2,'',0)</code> . Ces vecteurs sont idéaux pour vérifier les versions minimum, etc., parce que Python compare les vecteurs élément par élément, de gauche à droite. Par exemple :</p>
<pre>
if scribus.scribus_version_info[:3] < (1,2,2):
messageBox("Scribus - script Python",
@@ -31,6 +31,7 @@
</pre>
<h4>Constantes d'énumération d'unités : </h4>
+<table><tr><td>
<dl>
<dt>UNIT_POINTS</dt>
<dd>Unité de mesure point = 0</dd>
@@ -41,12 +42,14 @@
<dt>UNIT_PICAS</dt>
<dd>Unité de mesure pica = 3</dd>
</dl>
+</td></tr></table>
<h4>Constantes de conversion d'unités</h4>
<p>Ces facteurs de conversion peuvent être utilisés pour convertir les unités en points et vice versa.
Ainsi, pour convertir les pouces en points, il suffit d'écrire 'valeur/inch'; pour convertir les points en pouces vous écrirez 'valeur*inch', et pour convertir les pouces en mm vous écrirez 'valeur*mm/inch'.</p>
+<table><tr><td>
<dl>
<dt>pt</dt>
<dd>points dans 1 pt</dd>
@@ -61,14 +64,17 @@
<dt>...</dt>
<dd>D'autres constantes seront fournies si le coeur de Scribus les reconnaît.</dd>
</dl>
+</td></tr></table>
<h4>Définitions d'orientation de page :</h4>
+<table><tr><td>
<dl>
<dt>PORTRAIT</dt>
<dd>Orientation Portrait = 0</dd>
<dt>LANDSCAPE</dt>
<dd>Orientation Landscape = 1</dd>
</dl>
+</td></tr></table>
<h4>Réglages de format de page : </h4>
<table><tr>
@@ -188,6 +194,7 @@
</table>
<h4>Réglages de la disposition du document :</h4>
+<table><tr><td>
<dl>
<dt>FACINGPAGES</dt>
<dd>Disposition avec des pages en regard.</dd>
@@ -198,10 +205,12 @@
<dt>FIRSTPAGERIGHT</dt>
<dd>La première page du document est une première de droite.</dd>
</dl>
+</td></tr></table>
<h4>Réglages de l'alignement :</h4>
-<dl>
- <dt>ALIGN_LEFTK</dt>
+<table><tr><td>
+<dl>
+ <dt>ALIGN_LEFT</dt>
<dd>Le texte est aligné à gauche.</dd>
<dt>ALIGN_CENTERED</dt>
<dd>Le texte est centré dans le cadre de texte.</dd>
@@ -212,8 +221,10 @@
<dt>ALIGN_BLOCK</dt>
<dd>Le texte a un alignement bloqué.</dd>
</dl>
+</td></tr></table>
<h4>Réglages de l'alignement vertical :</h4>
+<table><tr><td>
<dl>
<dt>ALIGNV_TOP</dt>
<dd>Le texte est aligné verticalement en haut.</dd>
@@ -222,8 +233,10 @@
<dt>ALIGNV_BOTTOM</dt>
<dd>Le texte est aligné verticalement en bas.</dd>
</dl>
+</td></tr></table>
<h4>Réglages relatifs aux lignes :</h4>
+<table><tr><td>
<dl>
<dt>LINE_DASH</dt>
<dt>LINE_DASHDOT</dt>
@@ -239,8 +252,10 @@
<dt>CAP_ROUND</dt>
<dt>CAP_SQUARE</dt>
</dl>
+</td></tr></table>
<h4>Réglages relatifs au fond :</h4>
+<table><tr><td>
<dl>
<dt>FILL_NOG</dt>
<dd>Pas de dégradé, couleur unie</dd>
@@ -250,8 +265,10 @@
<dt>FILL_CROSSDIAGONALG</dt>
<dt>FILL_RADIALG</dt>
</dl>
+</td></tr></table>
<h4>Boutons de dialogue</h4>
+<table><tr><td>
<dl>
<dt>BUTTON_ABORT</dt>
<dt>BUTTON_CANCEL</dt>
@@ -262,14 +279,17 @@
<dt>BUTTON_RETRY</dt>
<dt>BUTTON_YES</dt>
</dl>
+</td></tr></table>
<h4>Icônes de dialogue</h4>
+<table><tr><td>
<dl>
<dt>ICON_CRITICAL</dt>
<dt>ICON_INFORMATION</dt>
<dt>ICON_NONE</dt>
<dt>ICON_WARNING</dt>
</dl>
+</td></tr></table>
</body>
</html>
Modified: trunk/Scribus/doc/it/scripterapi-constants.html
URL: http://scribus.net/websvn/diff.php?repname=Scribus&rev=22771&path=/trunk/Scribus/doc/it/scripterapi-constants.html
==============================================================================
--- trunk/Scribus/doc/it/scripterapi-constants.html (original)
+++ trunk/Scribus/doc/it/scripterapi-constants.html Sun Nov 18 00:35:27 2018
@@ -14,7 +14,7 @@
<h4>Scribus Version:</h4>
<p>The script interface provides two variables containing the current Scribus version in the <code>scribus</code> module. Scripts can use these variables to check that they're running under the version of Scribus they expect, and to report information about incompatibilities to the user. These two variables, <code>scribus_version</code> and <code>scribus_version_info</code>, were added in 1.2.1 and 1.3.0svn and will not be present in earlier versions. If you need to, you can check for their presence with <code>hasattr(scribus, 'scribus_version')</code>.</p>
<p><code>scribus_version</code> contains the current Scribus version as a string. It will usually look like <code>'1.2.1svn'</code> or <code>'1.3.0'</code>, for example, but is not guaranteed to always follow that format. This variable is useful when you need to display the version to the user, for example when reporting an incompatibility. Do not parse or compare this variable, that is what <code>scribus_version_info</code> is for.</p>
- <p><code>scribus_version_info</code> is a tuple similar to the <code>sys.version_info</code> tuple provided by Python. It is a tuple of the form (majorversion, minorversion, patchlevel, extraversion, build) for example, 1.2.1svn will have <code>(1,2,1,'svn',0)</code> and 1.3.2 will have <code>(1,3,2,'',0)<code> . These tuples are ideal for checking for minimum versions, etc, because Python compares tuples element-by-element, left-to-right. For example:</p>
+ <p><code>scribus_version_info</code> is a tuple similar to the <code>sys.version_info</code> tuple provided by Python. It is a tuple of the form (majorversion, minorversion, patchlevel, extraversion, build) for example, 1.2.1svn will have <code>(1,2,1,'svn',0)</code> and 1.3.2 will have <code>(1,3,2,'',0)</code> . These tuples are ideal for checking for minimum versions, etc, because Python compares tuples element-by-element, left-to-right. For example:</p>
<pre>
if scribus.scribus_version_info[:3] < (1,2,2):
messageBox("Scribus - Python script",
@@ -27,6 +27,7 @@
<h4>Unit Enumeration Constants: </h4>
+<table><tr><td>
<dl>
<dt>UNIT_POINTS</dt>
<dd>Measurement Unit Point = 0</dd>
@@ -37,6 +38,7 @@
<dt>UNIT_PICAS</dt>
<dd>Measurement Unit Pica = 3</dd>
</dl>
+</td></tr></table>
<h4>Unit Conversion Constants</h4>
@@ -45,6 +47,7 @@
convert points to inches you write 'value*inch', and to convert inches to mm
you write 'value*mm/inch' .</p>
+<table><tr><td>
<dl>
<dt>pt</dt>
<dd>points in 1 pt</dd>
@@ -59,14 +62,17 @@
<dt>...</dt>
<dd>Other constants will be provided if the Scribus core knows about them.</dd>
</dl>
+</td></tr></table>
<h4>Page Orientation Definitions: </h4>
+<table><tr><td>
<dl>
<dt>PORTRAIT</dt>
<dd>Page orientation Portrait = 0</dd>
<dt>LANDSCAPE</dt>
<dd>Page orientation Landscape = 1</dd>
</dl>
+</td></tr></table>
<h4>Definitions for Page Formats: </h4>
<p>If you are using these, it's important to understand that these constants are simply tuples of these specific numbers. There are now two sets of these constants for A and B series of paper formats.</p>
@@ -188,6 +194,7 @@
</table>
<h4>Definitions for Document Layout:</h4>
+<table><tr><td>
<dl>
<dt>FACINGPAGES</dt>
<dd>Layout with facing Pages.</dd>
@@ -198,10 +205,12 @@
<dt>FIRSTPAGERIGHT</dt>
<dd>The first Page of the Document is a right Page.</dd>
</dl>
+</td></tr></table>
<h4>Alignment Definitions: </h4>
-<dl>
- <dt>ALIGN_LEFTK</dt>
+<table><tr><td>
+<dl>
+ <dt>ALIGN_LEFT</dt>
<dd>Text is aligned to the Left.</dd>
<dt>ALIGN_CENTERED</dt>
<dd>The Text is centered in the Textframe.</dd>
@@ -212,8 +221,10 @@
<dt>ALIGN_BLOCK</dt>
<dd>The Text has block Alignment</dd>
</dl>
+</td></tr></table>
<h4>Vertical alignment Definitions: </h4>
+<table><tr><td>
<dl>
<dt>ALIGNV_TOP</dt>
<dd>Text is aligned vertically to the top.</dd>
@@ -222,8 +233,10 @@
<dt>ALIGNV_BOTTOM</dt>
<dd>Text is aligned vertically to the bottom.</dd>
</dl>
+</td></tr></table>
<h4>Line related Definitions: </h4>
+<table><tr><td>
<dl>
<dt>LINE_DASH</dt>
<dt>LINE_DASHDOT</dt>
@@ -239,8 +252,10 @@
<dt>CAP_ROUND</dt>
<dt>CAP_SQUARE</dt>
</dl>
+</td></tr></table>
<h4>Fill related Definitions: </h4>
+<table><tr><td>
<dl>
<dt>FILL_NOG</dt>
<dd>No gradient, plain color</dd>
@@ -250,6 +265,7 @@
<dt>FILL_CROSSDIAGONALG</dt>
<dt>FILL_RADIALG</dt>
</dl>
+</td></tr></table>
<h4>Dialog Buttons</h4>
<p>
@@ -270,12 +286,14 @@
<p>For example, even if you assign CANCEL to button1, RETRY to button2, and YES to button3, they will appear YES, RETRY, and CANCEL left to right in the dialog.</p>
<h4>Dialog Icons</h4>
+<table><tr><td>
<dl>
<dt>ICON_CRITICAL</dt>
<dt>ICON_INFORMATION</dt>
<dt>ICON_NONE</dt>
<dt>ICON_WARNING</dt>
</dl>
+</td></tr></table>
</body>
</html>
More information about the scribus-commit
mailing list