On Tue, May 5, 2009 at 1:47 PM, Roan Kattouw <[email protected]> wrote: > 2009/5/5 Brad Jorsch <[email protected]>: >> On Tue, May 05, 2009 at 09:10:16AM -0700, Michael Dale wrote: >>> Could we add in an action get message to the api or add some >>> functionality to meta=allmessages ? >>> >>> Really need to be able to: >>> A) send in parameterized replace values per msg key >>> B) get the html rendered / parsed result (rather than the wikitext) >>> >>> Security wise the parameterized replace values should be treated as >>> wikitext and go through the wiki-text-parser before rendered back out to >>> the browser. >> >> I'm not sure how feasable that would actually be, as the messages are >> not all handled the same way. In fact, as far as I know there isn't even >> any generic way to tell how any particular message is handled besides >> "read the source". It all depends on how exactly the message is used in >> the code that actually makes use of it. >> >> Among other possibilities, the message could be treated as plain text, >> as raw HTML, as fully-parsed wikitext (action=parse), or as >> preprocessed-only wikitext (similar to if not the same as >> action=expandtemplates); see the various wfMsg* functions. Substitution >> of the parameters could be done before or after the message itself is >> processed, and the individual parameters could themselves have been >> processed in any manner before being passed to wfMsgWhatever. >> > Good point. Because parameter substitution is trivial (e.g. with PHP's > strtr() function) and all other functions (preprocess, parse) are > available already, this doesn't need any additional functionality. > > Roan Kattouw (Catrope) > > _______________________________________________ > Mediawiki-api mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/mediawiki-api >
On that note and similar, I had been thinking about just this same issue recently. Rather than a new API module (which would be redundant, as Roan points out), what if we added some new Ajax functions? Then JS has access to messages, but we're not relying on custom Http requests to the API to get them. -Chad _______________________________________________ Mediawiki-api mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mediawiki-api
