Welcome to mediawiki-l. This mailing list exists for discussion and questions
about the MediaWiki software[0]. Important MediaWiki-related announcements
(such as new versions) are also posted to this list.
Other resources.
If you only wish to receive announcements, you should subscribe to
mediawiki-announce[1] instead.
MediaWiki development discussion, and all Wikimedia technical questions, should
be directed to the wikitech-l[2] mailing list.
Several other MediaWiki-related lists exist:
- mediawiki-api[5] for API discussions,
- mediawiki-enterprise[6] for discussion of MediaWiki in the enterprise,
- mediawiki-cvs[7] for notification of commits to the Subversion repository,
- mediawiki-i18n[8] for discussion of MediaWiki internationalisation support,
- wikibugs-l[9] for notification of changes to the bug tracker.
List administrivia (unsubscribing, list archives).
To unsubscribe from this mailing list, visit [12]. Archives of previous postings
can be found at [3].
This list is also gatewayed to the Gmane NNTP server[4], which you can use to
read and post to the list.
Posting to the list.
Before posting to this list, please read the MediaWiki FAQ[10]. Many common
questions are answered here. You may also search the list archives to see if
your question has been asked before.
Please try to ask your question in a way that enables people to answer you.
Provide all relevant details, explain your problem clearly, etc. You may
wish to read [13], which explains how to ask questions well.
To post to the list, send mail to <mediawiki-l(a)lists.wikimedia.org>. This is a
public list, so you should not include confidential information in mails you
send.
When replying to an existing thread, use the "Reply" or "Followup" feature of
your mail client, so that clients that understand threading can sort your
message properly. When quoting other messages, please use the "inline" quoting
style[11], for clarity.
When creating a new thread, do not reply to an existing message and change the
subject. This will confuse peoples' mail readers, and will result in fewer
people reading your mail. Instead, compose a new message for your post.
Messages posted to the list have the "Reply-To" header set to the mailing list,
which means that by default, replies will go to the entire list. If you are
posting a reply which is only interesting to the original poster, and not the
list in general, you should change the reply to only go to that person. This
avoids cluttering the list with irrelevant traffic.
About this message.
This message is posted to the list once per week by <river(a)wikimedia.org>.
Please contact me if you have any questions or concerns about this mailing.
References.
[0] http://www.mediawiki.org/
[1] http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
[2] http://lists.wikimedia.org/mailman/listinfo/wikitech-l
[3] http://lists.wikimedia.org/pipermail/mediawiki-l/
[4] http://dir.gmane.org/gmane.org.wikimedia.mediawiki
[5] http://lists.wikimedia.org/mailman/listinfo/mediawiki-api
[6] http://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise
[7] http://lists.wikimedia.org/mailman/listinfo/mediawiki-cvs
[8] http://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
[9] http://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[10] http://www.mediawiki.org/wiki/FAQ
[11] http://en.wikipedia.org/wiki/Posting_style#Inline_replying
[12] http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
[13] http://www.catb.org/~esr/faqs/smart-questions.html
Hello,
I need to be able to trace trough my wiki processing and followed
http://www.mediawiki.org/wiki/How_to_debug instructions to setup the debug.
However, the wfProfileIn & wfProfileOut calls in
$wikiroot/includes/WebStart.php are causing undefined function errors. Can
someone tell me what is the problem? Thank you.
Nelson
Computer Sciences Corporation
Registered Office: 2100 East Grand Avenue, El Segundo California 90245, USA
Registered in USA No: C-489-59
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery.
NOTE: Regardless of content, this e-mail shall not operate to bind CSC to
any order or other contract unless pursuant to explicit written agreement
or government initiative expressly permitting the use of e-mail for such
purpose.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I've edited the extension http://www.mediawiki.org/wiki/Extension:Flash to
allow post my own uploaded flashes animations.
It works great... but only in preview mode!!!
In the discussion page of this extension someone talks about "the solution
is to correct the current directory assumptions in the Flash code." but I've
tried with flash animations without any actionscript that could take any
current directory assumptions and does not work too.
This is my extension flash version:
class Flash
{
var $tmp;
var $file;
/* Constructor */
function Flash( $input )
{
$this->tmp = '';
Flash::parseInput( $input ); // Parse the input
Flash::genCode(); // Generate the final code
}
/* Parser */
function parseInput( $input )
{
$this->file = $input;
}
/* Generate big, final chunk of code */
function genCode()
{
// Possibly malicious settings:
$allowscriptaccess = 'false'; // allow / disallow scripts
$swliveconnect = 'false'; // start / do not start up java
// Default version Setting:
$this->version = '7,0,0,0'; // Version settings for <object>
$this->url = $this->getTitle( $this->file );//Flash::imageUrl(
$this->file, $this->fromSharedDirectory ); // get Wiki internal url
$this->code = '<div style="border:1px solid;">
<embed src="extensions/flashMovie/quemecorro.swf" width="400"
height="400"
type="application/x-shockwave-flash" pluginspage="
http://www.macromedia.com/go/getflashplayer" />
</div>';
return $this->code;
}
function getTitle( $file )
{
$title = Title::makeTitleSafe("Image",$file);
$img = new Image( $title );
$path = $img->getViewURL(false);
return $path;
}
}
function wfFlashExtension()
{
global $wgParser;
$wgParser->setHook( "flash", "renderFlash" );
}
function renderFlash( $input )
{
global $code;
// Constructor
$flashFile = new Flash( $input );
$code = $flashFile->code;
return $code; // send the final code to the wiki
}
Hello. This is my first post to the list.
I've been looking for a way to pre-populate normal wiki articles with
a template (specifically, I want all user-created articles to include
the Digg extension, using the <digg /> tag). How would I go about
doing that?
I don't want things like special pages and help pages to have the
digg code, which is why I'm not just hard-coding it into my custom
template.
Thanks in advance for any help.
If anyone is interested in open source semantic temporal audio/video
metadata in mediaWiki take a look at the metavidWiki extension. I just
posted a screen cast ... still a few weeks away from public launch but
you can check out the preview now:
http://metavid.ucsc.edu/blog/2007/12/18/short-metavidwiki-extension-screenc…
if your *really* interested come by #metavid on freenode (like most
projects) we could use more testers / whatever level you interested in
getting engaged at ;)
peace,
michael
On Dec 18, 2007 7:16 AM, Kent S. Larsen II <kent(a)lusobraz.com> wrote:
>
> Turns out that the Proofread Page extension can be used for this.
> Apparently, Proofread Page is used on Wikisource for proofing scans and
> entering text from images.
>
I messed around four a handful of hours after feeling inspired from
that website that was linked.
*I got a 'diff' like view of __TOC__ items (en on one side, fr on other other)
*If the fr is missing prompt to create it, use a hack to use en as default text.
*I found it much easier to have en side read only and the fr side
mundanely writeable.
*I just did cheesy <form> actions to a hack that pushed the changes as
individual __TOC_ edits rather than using that sexy ajax thing they
had.
I can see the need for work flow being what drives how you design
this. Since I know nothing about actual translations and just did the
raw diff edit.
The editing of complete static texts vs editing living wiki content
seems quite easy. Especially with major content structure changes
where the __TOC__ will get out of whack. Make big changes to en,
potentially you could toss out the hours of work on fr.
--
Gabriel Millerd
On Dec 5, 2007 1:19 AM, Kent S. Larsen II <kent(a)lusobraz.com> wrote:
>
> It is trivial to set up a wiki with the text to be translated on one page,
> and the result on another (or on a subpage).
>
> The difficulty comes when the source and result are side by side.
>
Pretty cool project!
I can see why they went with such an ajax heavy page to avoid the
diff/merge of the whole page. Seems like:
1. Writing a Special:MultiXlate page that show a single page with its
various TOC elements side by side.
2. Crafting an ajax <textarea> editor for each TOC element on the
target side that submits changes to the actual language page as
'section' edits.
3. Creating some stock ajax <textarea>'s logic where the TOC elements
don't exist on the missing sides if one of the pages was out of
translation. Likely some heavy coloring indicating this. Though this
might not be needed for translating 'works' since the source side is
always going to be there. But for a translating a normal user
generated content wiki it would be.
4. The 'rate my translation' and '% of work translated' stuff seems
sort of kinky and highly variable depending on the environment and the
documents being translated.
--
Gabriel Millerd
Hello, I have a problem with SVG images. If I upload an image in SVG format there is: "Error creating thumbnail: Invalid parameter - white" in the browser. What's wrong? Thank you for help. -MGrabovsky
