EI: Bind translatable strings to wesnoth-units
Barrow Wight's definition includes a couple of attack name strings
from the wesnoth-units textdomain bound to wesnoth-ei by default
instead, which creates two unnecessary extra strings for translators
to translate. This change fixes this by binding these two strings to
wesnoth-units so their existing translations can be used.
(Pyre Wight does not require this change since it already uses the
wesnoth-units textdomain for the single attack name it uses.)
(cherry picked from commit d6a8c98211
)
This commit is contained in:
parent
95c62173a3
commit
f229bef40a
1 changed files with 2 additions and 0 deletions
|
@ -44,6 +44,7 @@
|
|||
[attack]
|
||||
name=sword
|
||||
icon=attacks/greatsword-orcish.png
|
||||
#textdomain wesnoth-units
|
||||
description=_"sword"
|
||||
type=blade
|
||||
range=melee
|
||||
|
@ -54,6 +55,7 @@
|
|||
name=trample
|
||||
icon="attacks/hoof-skeletal.png"
|
||||
description=_"trample"
|
||||
#textdomain wesnoth-ei
|
||||
type=impact
|
||||
range=melee
|
||||
damage=14
|
||||
|
|
Loading…
Add table
Reference in a new issue