While I certainly agree that WML markup is lacking in many ways, I am skeptical about the smoothness of the transition you are describing. The 5 standard escape entities in Pango Markup Language are: & < > " ' This means that ~RC(a>b) image path function syntax will need to change (because it contains >) No great loss there. But aren't there other places where special syntax of WML attributes uses special characters to represent lots of complex data that is crammed into a small space, e.g. http://www.wesnoth.org/wiki/DescriptionWML ?
Now we can either hand over entire control of markup parsing to Pango, or we can start by just handling known entities such as "<b>" "</b>" and doing some pattern matching where users might be able to use '<' and '>' and '&' without escape characters, (where said characters do not correspond to a formation of a known entity). Also, rather than discarding backwards compatibility-- consider the old syntax being used as a shorthand form? I would at least like that idea to be discussed in a forum where campaign authors and UMC maintainers can have their say before the change. --Sapient _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
