Mark de Wever <[email protected]>:
> Now that we have pango support for dialogs we also have more options to do
> formatting. At the moment this formatting is used by the engine internally
> to convert the Wesnoth markup to pango markup. The question is do we want to
> allow the WML authors to use pango markup or not.
> 
> The pros and cons of both markup systems
> Pango [1]
> Pro:
> - Markup can be used everywhere in a text.
> - looks like html, which might be easier for authors of WML to reconized.
> Con:
> - Certain characters like & must be escaped like &amp;
> 
> Wesnoth markup [2]
> Pro:
> - Simple to use.
> Con:
> - Markup can be used on a per line basis.
> 
> If we want to give WML authors acces to the Pango syntax do we also want to
> keep the current WML syntax? (I see no way to automate the conversion
> easily, especially since I expect authors want to take advantage of the new
> way, so the text needs a manual review. So we'll need a, long, transition
> phase supporting both syntaxes if we want to phase it out.)
> 
> Of course if we decide to do it we'll need to discuss how to implement it in
> WML and how to help the WML authors to properly escape their strings. But I
> rather put off those questions until we know what we want.
> 
> [1] http://library.gnome.org/devel/pango/unstable/PangoMarkupFormat.html
> [2] http://www.wesnoth.org/wiki/InterfaceActionsWML#.5Bmessage.


I think we should go with Pango and scrap the old Wesnoth markup. Immediately. 

The old Wesnoth markup is ugly and limited. So limited that I don't
really think transitional support is at all important.  Pango is powerful,
well documented, and a public standard with conventians that will already 
be familiar to HTML/XML authors; I see no contest here.

As for the conversion issue, that's what wmllint is for.  I just read about
Pango markup; I could write and test a wmllint rule to do the conversion
in less than an hour, I think.
-- 
                <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>

_______________________________________________
Wesnoth-dev mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-dev

Reply via email to