Custom ranges in 1.9

[Velensk]

Not sure where to put this but I figured here would be about as good a place as any.

I recently noticed that in wesnoth 1.9.4 when you are using a unit with a range other than 'melee' or 'ranged' it will insert UNTLB range_ in front of the name of the custom range. This looks rather ugly/awkward. I figure that it is intended to make it easier to notice when you do something like type melle or other such things but I am really hoping that there is some way to turn it off. Does anyone know how?

[silene]

I recently noticed that in wesnoth 1.9.4 when you are using a unit with a range other than 'melee' or 'ranged' it will insert UNTLB range_ in front of the name of the custom range. This looks rather ugly/awkward. I figure that it is intended to make it easier to notice when you do something like type melle or other such things but I am really hoping that there is some way to turn it off. Does anyone know how?

"UNTLB" means "untranslatable" (which is bad). You don't have any way to turn it off.

[Velensk]

I'd like to request that ranges become translatable before 1.10. Alternatively, offer some kind of feature to disable the notification though forcing everyone to use a translatable string instead might be advisable.

EDIT: I completely rewrote this message after doing a little bit of testing.

[silene]

I'd like to request that ranges become translatable before 1.10.

I didn't get to try it nor do I know if it is the correct way of enabling it, but theoretically it's already translatable in 1.9. You might try adding a language block to your campaign:

Code: Select all

[language] #or perhaps [+language]?
  range_whatever=_"whatever"
[/language]

[Velensk]

I'm unfamiliar with how Wesnoth handles translations.

The problem is actually showing up for my eras. Is what you are suggesting that the following code be put into the main cfg or have I gotten something wrong about it?

Code: Select all

[language]
     secret= _ "secret"
[/language]

[silene]

have I gotten something wrong about it?

I'm sure it is "range_secret=" instead of just "secret=". What I'm not sure is whether you have to use "[language]" or "[+language]". I suggest you try both. (If both works, I suggest using "[language]".)

[Sapient]

This could present a problem for a multiplayer scenario that uses the default era and has an object to add an attack with a non-standard range.

(There is one such in my map pack. Then again, not many people play Northerner RPG these days...)

[silene]

This could present a problem for a multiplayer scenario that uses the default era and has an object to add an attack with a non-standard range.

Just to make things clear, the UNTLB thing dates from around 2006, so it's nothing new. But perhaps it has been broken when the [language] block was improved for 1.9.4. (But since I didn't follow the changes, I don't know.)

[Velensk]

Thanks for the help, [language] works.