Skip to content

Commit

Permalink
Fixed formatting error in i18n files
Browse files Browse the repository at this point in the history
  • Loading branch information
@bubblobill
bubblobill committed Dec 3, 2023
1 parent 9b02231 commit 04fd49a
Show file tree
Hide file tree
Showing 3 changed files with 51 additions and 123 deletions.
50 changes: 13 additions & 37 deletions src/main/resources/net/rptools/maptool/language/i18n.properties
View file
Original file line number Diff line number Diff line change
Expand Up @@ -866,33 +866,6 @@ CampaignPropertiesDialog.label.light = <html>\
name: type shape OPTIONS scale range#rrggbb+x</pre>\
<p>Define groups of light types with a line of text to indicate the group \
name followed by one or more <b>name</b> definitions. End a group with a \
blank line. All text is case-insensitive. Lines that start with a "-" are \
considered comments and are ignored. The group name becomes an entry on \
the token's popup menu under the <b>Light Sources</b> element, and \
individual light source definitions become sub-entries. Group names are \
displayed in sorted order, and the sub-entries are alphabetically sorted \
as well.</p>\
<dl>\
<dt>name</dt><dd>A user-visible name for light definition.</dd>\
<dt>type</dt><dd>An optional type for the light. Currently only <b>aura</b> is valid. (See below for a description of auras.)</dd>\
<dt>shape</dt><dd>shape may be <b>circle</b>, <b>square</b>, <b>hex</b>, <b>grid</b>, <b>cone</b> or <b>beam</b>.</dd>\
<dt>distance=y</dt><dd>Distance is the range at which this vision type ends. Can be a decimal value, e.g. distance=10.5</dd>\
<dt>scale</dt><dd>An optional keyword that adds the token's footprint (size) to the distance so vision starts at token's edge vs the token's center.</dd>\
<dt>arc=y</dt><dd>Used with the cone shape. The angle of the cone in degrees, it determines the field of view covered by the light. Can be an integer value, e.g. arc=120</dd>\
<dt>width=y</dt><dd>Used with the beam shape. How wide the beam will be in map units. Can be a decimal, e.g. width=1.4</dd>\
<dt>offset=y</dt><dd>Used with the cone and beam shape. For cones, how many degrees off center the shape begins; for beams, how many degrees off center to the center-line of the beam. Can be an integer value, e.g. offset=120</dd>\
<dt>x#</dt><dd>Magnifier, multiplies each light source radius by this value. Can be a decimal value, e.g. x2.5</dd>\
<dt>r#</dt><dd><p>Range of personal light. The token will have a light source that only they can see, centered on them, with a radius of this value. You can define multiple personal lights per sight type.</p>\
<p>Can have an optional #rrggbb hex color component appended to it as per typical CSS rules.</p>\
<p>Can also have an optional +x lumens value. Lumens defaults to 100, meaning it will see through any darkness with a lumens value from -1 to -99. See discussion of lumens on the Light tab for more info.</p>\
<p>Ex: r60#bb0000+120</p></dd>\
</dl>\
<b>Format:</b> \
<pre>Group name<br>\
----------<br>\
name: type shape OPTIONS scale range#rrggbb+x</pre>\
<p>Define groups of light types with a line of text to indicate the group \
name followed by one or more <b>name</b> definitions. End a group with a \
blank line. All text is case-insensitive. Lines starting with a "-" are \
considered comments and are ignored. The group name becomes an entry on \
the token's popup menu under the <b>Light Sources</b> element, and \
Expand All @@ -902,21 +875,23 @@ their sub-entries are alphabetically sorted.</p>\
<dt>name</dt><dd>A user-visible name for light definition.</dd>\
<dt>type</dt><dd>An optional type for the light. Currently only <b>aura</b> is valid. (See below for a description of auras.)</dd>\
<dt>shape</dt><dd><p>An optional shape for the light emanation. Can be <b>circle</b> (default), \
<b>square</b>, <b>cone</b>, <b>beam</b>, or <b>grid&dagger;</b>.</p>\
<b>square</b>, <b>cone</b>, <b>beam</b>, or <b>grid</b>&dagger;.</p>\
<p>Additional fields exist for beams and cones; both have an <b>offset=<i>y</i></b> field,\
cones also have <b>arc=<i>y</i></b> and beams have a <b>width=<i>y</i></b> field.</p>\
<p>Shapes apply from the point they are included in the definition until the end of the \
definition or until another shape is specified. This means multiple light shapes \
can be created under a single name and turned on or off as a unit.</p>\
<p>&dagger;<i>For systems like Pathfinder if you want to see exactly which grid cells are\
affected by a Light/Aura.</i></p></dd>\
<dt>scale</dt><dd>An optional keyword that adds the token's footprint (size) to the range so the light/aura starts at token's edge vs the token's center.</dd>\
<dt>range</dt><dd><p>A distance measured in map units (defined when the map is created). Units are \
measured from the centerpoint of the grid cell, hence the extra 2 &#189; feet \
added in the below example to make neat squares.</p>\
<p>Can have an optional <i>#rrggbb</i> hex color component appended to it as per \
typical CSS rules.</p>\
<p>Can have an optional <i>+x</i> lumens value, with x equaling an integer \
<dt>arc=y</dt><dd>Used with the cone shape. The angle of the cone in degrees, it determines the field of view covered by the light. Can be an integer value, e.g. arc=120</dd>\
<dt>width=y</dt><dd>Used with the beam shape. How wide the beam will be in map units. Can be a decimal, e.g. width=1.4</dd>\
<dt>offset=y</dt><dd>Used with the cone and beam shape. For cones, how many degrees off center the shape begins; for beams, how many degrees off center to the center-line of the beam. Can be an integer value, e.g. offset=120</dd>\
<dt>OPTIONS</dt><dd>The only valid options are <b>GM</b> and <b>OWNER</b> and they apply only to auras (see below).</dd>\
<dt>scale</dt><dd>An optional keyword that adds the token's footprint (size) to the distance so vision starts at token's edge vs the token's center.</dd>\
<dt>range</dt><dd><p>A distance in map units as measured from the centerpoint of the grid cell.</p>\
<p>Can have additional definitions;\
<ul><li>A <i>#rrggbb</i> hex color component appended to determine color.</li>\
<li><p>A <i>+x</i> lumens value, with x equaling an integer \
(<i>-x</i> can instead be used to provide a negative lumens value). If not \
provided, the value will default to 100. If set to a negative number, the \
light will instead act as darkness and subtract it's area from the FoW. \
Expand All @@ -927,8 +902,9 @@ their sub-entries are alphabetically sorted.</p>\
<p><i>*Note:</i> Personal Lights defined in <i>Sight</i> have a default lumens \
value of 100. So a typical sight defined for Darkvision will see through \
any lights with a lumens value of -1 through -99. To overcome Darkvision, use \
lumens values &lt;= -100.</p></dd>\
<dt>OPTIONS</dt><dd>The only valid options are <b>GM</b> and <b>OWNER</b> and they apply only to auras (see below).</dd>\
lumens values &lt;= -100.</p>\
</li>\
</ul></dd>\
</dl>\
<p><b>Example:</b></p>\
<pre>\
Expand Down
62 changes: 19 additions & 43 deletions src/main/resources/net/rptools/maptool/language/i18n_en_au.properties
View file
Original file line number Diff line number Diff line change
Expand Up @@ -849,13 +849,13 @@ CampaignPropertiesDialog.label.sight = <html>\
<dl>\
<dt>shape</dt><dd>shape may be circle, square, hex, grid, cone or beam</dd>\
<dt>distance=y</dt><dd>Distance is the range at which this vision type ends. Can be a decimal value, e.g. distance=10.5</dd>\
<dt>scale</dt><dd>An optional keyword that adds the token's footprint (size) to the distance so vision starts at token's edge vs the token's centre.</dd>\
<dt>scale</dt><dd>An optional keyword that adds the token's footprint (size) to the distance so vision starts at token's edge vs the token's center.</dd>\
<dt>arc=y</dt><dd>Used with the cone shape. The angle of the cone in degrees, it determines the field of view the token has. Can be an integer value, e.g. arc=120</dd>\
<dt>width=y</dt><dd>Used with the beam shape. How wide the beam will be in map units. Can be a decimal, e.g. width=1.4</dd>\
<dt>offset=y</dt><dd>Used with the cone and beam shape. For cones, how many degrees off centre the shape begins; for beams, how many degrees off centre to the centre-line of the beam. Can be an integer value, e.g. offset=120</dd>\
<dt>offset=y</dt><dd>Used with the cone and beam shape. For cones, how many degrees off center the shape begins; for beams, how many degrees off center to the center-line of the beam. Can be an integer value, e.g. offset=120</dd>\
<dt>x#</dt><dd>Magnifier, multiplies each light source radius by this value. Can be a decimal value, e.g. x2.5</dd>\
<dt>r#</dt><dd><p>Range of personal light. The token will have a light source centreed on them that only they can see with a radius of this value. You can define multiple personal lights per sight type.</p>\
<p>Can have an optional #rrggbb hex color component appended to it as per typical CSS rules.</p>\
<dt>r#</dt><dd><p>Range of personal light. The token will have a light source centered on them that only they can see with a radius of this value. You can define multiple personal lights per sight type.</p>\
<p>Can have an optional #rrggbb hex colour component appended to it as per typical CSS rules.</p>\
<p>Can also have an optional +x lumens value. Lumens defaults to 100, meaning it will see through any darkness with a lumens value from -1 to -99. See discussion of lumens on the Light tab for more info.</p>\
<p>Ex: r60#bb0000+120</p></dd>\
</dl>\
Expand All @@ -868,33 +868,6 @@ CampaignPropertiesDialog.label.light = <html>\
name: type shape OPTIONS scale range#rrggbb+x</pre>\
<p>Define groups of light types with a line of text to indicate the group \
name followed by one or more <b>name</b> definitions. End a group with a \
blank line. All text is case-insensitive. Lines that start with a "-" are \
considered comments and are ignored. The group name becomes an entry on \
the token's popup menu under the <b>Light Sources</b> element, and \
individual light source definitions become sub-entries. Group names are \
displayed in sorted order, and the sub-entries are alphabetically sorted \
as well.</p>\
<dl>\
<dt>name</dt><dd>A user-visible name for light definition.</dd>\
<dt>type</dt><dd>An optional type for the light. Currently only <b>aura</b> is valid. (See below for a description of auras.)</dd>\
<dt>shape</dt><dd>shape may be <b>circle</b>, <b>square</b>, <b>hex</b>, <b>grid</b>, <b>cone</b> or <b>beam</b>.</dd>\
<dt>distance=y</dt><dd>Distance is the range at which this vision type ends. Can be a decimal value, e.g. distance=10.5</dd>\
<dt>scale</dt><dd>An optional keyword that adds the token's footprint (size) to the distance so vision starts at token's edge vs the token's centre.</dd>\
<dt>arc=y</dt><dd>Used with the cone shape. The angle of the cone in degrees, it determines the field of view covered by the light. Can be an integer value, e.g. arc=120</dd>\
<dt>width=y</dt><dd>Used with the beam shape. How wide the beam will be in map units. Can be a decimal, e.g. width=1.4</dd>\
<dt>offset=y</dt><dd>Used with the cone and beam shape. For cones, how many degrees off centre the shape begins; for beams, how many degrees off centre to the centre-line of the beam. Can be an integer value, e.g. offset=120</dd>\
<dt>x#</dt><dd>Magnifier, multiplies each light source radius by this value. Can be a decimal value, e.g. x2.5</dd>\
<dt>r#</dt><dd><p>Range of personal light. The token will have a light source that only they can see, centreed on them, with a radius of this value. You can define multiple personal lights per sight type.</p>\
<p>Can have an optional #rrggbb hex color component appended to it as per typical CSS rules.</p>\
<p>Can also have an optional +x lumens value. Lumens defaults to 100, meaning it will see through any darkness with a lumens value from -1 to -99. See discussion of lumens on the Light tab for more info.</p>\
<p>Ex: r60#bb0000+120</p></dd>\
</dl>\
<b>Format:</b> \
<pre>Group name<br>\
----------<br>\
name: type shape OPTIONS scale range#rrggbb+x</pre>\
<p>Define groups of light types with a line of text to indicate the group \
name followed by one or more <b>name</b> definitions. End a group with a \
blank line. All text is case-insensitive. Lines starting with a "-" are \
considered comments and are ignored. The group name becomes an entry on \
the token's popup menu under the <b>Light Sources</b> element, and \
Expand All @@ -904,21 +877,23 @@ their sub-entries are alphabetically sorted.</p>\
<dt>name</dt><dd>A user-visible name for light definition.</dd>\
<dt>type</dt><dd>An optional type for the light. Currently only <b>aura</b> is valid. (See below for a description of auras.)</dd>\
<dt>shape</dt><dd><p>An optional shape for the light emanation. Can be <b>circle</b> (default), \
<b>square</b>, <b>cone</b>, <b>beam</b>, or <b>grid&dagger;</b>.</p>\
<b>square</b>, <b>cone</b>, <b>beam</b>, or <b>grid</b>&dagger;.</p>\
<p>Additional fields exist for beams and cones; both have an <b>offset=<i>y</i></b> field,\
cones also have <b>arc=<i>y</i></b> and beams have a <b>width=<i>y</i></b> field.</p>\
<p>Shapes apply from the point they are included in the definition until the end of the \
definition or until another shape is specified. This means multiple light shapes \
can be created under a single name and turned on or off as a unit.</p>\
<p>&dagger;<i>For systems like Pathfinder if you want to see exactly which grid cells are\
affected by a Light/Aura.</i></p></dd>\
<dt>scale</dt><dd>An optional keyword that adds the token's footprint (size) to the range so the light/aura starts at token's edge vs the token's centre.</dd>\
<dt>range</dt><dd><p>A distance measured in map units (defined when the map is created). Units are \
measured from the centrepoint of the grid cell, hence the extra 2 &#189; feet \
added in the below example to make neat squares.</p>\
<p>Can have an optional <i>#rrggbb</i> hex color component appended to it as per \
typical CSS rules.</p>\
<p>Can have an optional <i>+x</i> lumens value, with x equaling an integer \
<dt>arc=y</dt><dd>Used with the cone shape. The angle of the cone in degrees, it determines the field of view covered by the light. Can be an integer value, e.g. arc=120</dd>\
<dt>width=y</dt><dd>Used with the beam shape. How wide the beam will be in map units. Can be a decimal, e.g. width=1.4</dd>\
<dt>offset=y</dt><dd>Used with the cone and beam shape. For cones, how many degrees off center the shape begins; for beams, how many degrees off center to the center-line of the beam. Can be an integer value, e.g. offset=120</dd>\
<dt>OPTIONS</dt><dd>The only valid options are <b>GM</b> and <b>OWNER</b> and they apply only to auras (see below).</dd>\
<dt>scale</dt><dd>An optional keyword that adds the token's footprint (size) to the distance so vision starts at token's edge vs the token's center.</dd>\
<dt>range</dt><dd><p>A distance in map units as measured from the centerpoint of the grid cell.</p>\
<p>Can have additional definitions;\
<ul><li>A <i>#rrggbb</i> hex colour component appended to determine colour.</li>\
<li><p>A <i>+x</i> lumens value, with x equaling an integer \
(<i>-x</i> can instead be used to provide a negative lumens value). If not \
provided, the value will default to 100. If set to a negative number, the \
light will instead act as darkness and subtract it's area from the FoW. \
Expand All @@ -929,8 +904,9 @@ their sub-entries are alphabetically sorted.</p>\
<p><i>*Note:</i> Personal Lights defined in <i>Sight</i> have a default lumens \
value of 100. So a typical sight defined for Darkvision will see through \
any lights with a lumens value of -1 through -99. To overcome Darkvision, use \
lumens values &lt;= -100.</p></dd>\
<dt>OPTIONS</dt><dd>The only valid options are <b>GM</b> and <b>OWNER</b> and they apply only to auras (see below).</dd>\
lumens values &lt;= -100.</p>\
</li>\
</ul></dd>\
</dl>\
<p><b>Example:</b></p>\
<pre>\
Expand All @@ -953,7 +929,7 @@ Darkness - 20 (CL4): circle 22.5-40<br> \
<hr>\
<p><b>Auras:</b></p>\
<p>To create an aura, put the keyword <b>aura</b> at the beginning of the \
definition. Auras radiate a colored area and interact with the vision \
definition. Auras radiate a coloured area and interact with the vision \
blocking layer (i.e. are blocked by VBL), but do not actually cast any \
visible light and do not expose any fog-of-war. GM-only auras are only \
visible by clients logged into the server as GM. They remain visible \
Expand All @@ -962,7 +938,7 @@ only visible to the player(s) who owns the token. They are always visible\
to the GM. See examples, below.</p>\
<p>In the following example, the GM-only auras are red, the owner-only \
auras are green, and the player auras are blue. You can of course define \
your own colors.</p>\
your own colours.</p>\
<pre>\
Sample Auras: 5' grid<br>\
----<br>\
Expand Down
Loading

0 comments on commit 04fd49a

Please sign in to comment.