Last modified: 2011-09-22 12:38:41 UTC
I have found several issues with the babel-Extension, and I'm too lazy to create a report each. * Substitution does not work, because the babel table misses the extra css file. * The used templates only show up in the "used templates section" after you've clicked on [preview]: http://de.wikipedia.org/w/index.php?title=Benutzer:Raymond&action=edit#mw-editTools, and they don't show up in the backlinklist. * There is no way to set the gender parameter ("mw"), which often has a option for the value "1". My propose would be to allow named parameters, which then are forwarded to each od the used templates. * And of course there is no way to configure the look-and-feel of non-template-based boxes, which was the big point for all those smaller wikis that really /need/ the extension. But that's Bug 31084. * Also, there might be problems with the for-loop. It should not allow more cycles than the number of supported languages. I've tried, you can make every server report technical errors by passing 5000 three-letter arguments to the function. I'm not sure whether this is a security hole. * I guess the extension can be heavily misused, cause every user is allowed to create templates in the [[{{int:babel-template}}...]]-schema. As an example for what is possible today try http://de.wikipedia.org/wiki/Spezial:Vorlagen_expandieren?input=%7B%7B%23Babel%3AWikiquote%7CSUL%7C~%7Ccommitted%20identity%7CEgyp%7Cfr%2FDoku%7D%7D, but I think there are clever minds who will use the #babel function as a replacement for the #forargs function. I also think it would be more suitable to activate that one, and build the normal Babel-Templates with it, as the system messages for understanding of languages could be used on smaller wikis where there are no templates.
I am too lazy to fix your issues.
(In reply to comment #0) > I have found several issues with the babel-Extension, and I'm too lazy to > create a report each. Handling these kinds wishlists in bugzilla is very cumbersome. Developers are already pressed on working the code, they are not going to be happy if they need to spend time splitting these into individual reports. > * Substitution does not work, because the babel table misses the extra css > file. It is not a template. > * The used templates only show up in the "used templates section" after you've > clicked on [preview] This could be looked into. > * There is no way to set the gender parameter ("mw"), which often has a option > for the value "1". My propose would be to allow named parameters, which then > are forwarded to each od the used templates. So this is a feature request for custom user templates? The gender already works for inbuilt language strings. > * And of course there is no way to configure the look-and-feel of > non-template-based boxes, which was the big point for all those smaller wikis > that really /need/ the extension. But that's Bug 31084. Works for me. > * Also, there might be problems with the for-loop. It should not allow more > cycles than the number of supported languages. I've tried, you can make every > server report technical errors by passing 5000 three-letter arguments to the > function. I'm not sure whether this is a security hole. You only get an error, no security issues involved. We might have a fix for this issue. > * I guess the extension can be heavily misused Everything can be misused.
Opened bug 31094 and bug 31095 for the real issues I see in this report. Closing this one.
