Follow-up Comment #2, bug #17395 (project wesnoth):
Well, the rest of that file seems to work in the expected way, not simply
being a dummy key to declare the string to wmlxgettext.
The reason I checked into this in the first place is to see what was needed
to allow UMC to make their own ranges translatable.
Currently, this is almost possible, except that they need to get their own
dummied strings into the 'wesnoth' textdomain.
So, usecases:
-allowing custom ranges for UMC that don't have access to the 'wesnoth'
textdomain to be translated
-separating the range identifier from the user-visible part, like unit_type's
id and name. It can be useful for the same reasons.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?17395>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
