Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

Why not setup a repository in git to keep the images etc. there?

-----Original Message-----
From: Robinson Tryon [] 
Sent: 15 February 2013 20:09
To: Florian Effenberger
Cc: website LibreOffice
Subject: Re: [libreoffice-website] Wiki upload issues [was Libo4 Pages: new
version 20130211]

On Fri, Feb 15, 2013 at 5:10 AM, Florian Effenberger
<> wrote:
so, the function and message itself is incorporated in MediaWiki 
directly, and editing is probably not impossible,

oh, really...?

but rather painful, since you would
have to translate the text in all supported languages, plus edit the 
MediaWiki core, and merge your changes with every update coming in. In 
words: It is somehow impossible. ;-)

...yes, really :-)

What we can do is tweaking the file sizes when a warning gets triggered.
Right now, I have configured the wiki the following way:

$wgUploadSizeWarning = 1024 * 1024 * 5; $wgMaxUploadSize = 1024 * 1024 
* 25;

I would feel uncomfortable with more than 25 MB upload size, since the 
wiki is no file storage.

I do apologize for gumming-up the wiki with these oversized image files.
They really don't belong on the wiki. Perhaps Camille and I can work with
you to find a replacement tool for storing all of our source media! Or
rather, perhaps we can take the lead on that task and coordinate with you --
I don't want to take more of your time than necessary.

However, we can talk about raising the warning size. :-) What do you 
think makes sense?

As a quick fix, I'd suggest moving it up to 10MB. Even though the wiki is
serving as our defacto repository for source media for design team stuff, I
think it's reasonable to have reservations about throwing anything larger up
than 10MB without having a really good reason, first :-)

2) Some uploaded images display properly, some don't:

It indeed seems that MediaWiki has a problem with resizing these 
files, independent of whether we use ImageMagick or not, and 
independent of the memory limitation I configure. I can't solve this 
ad-hoc, but will put it on the todo to be fixed then.

Is this only for larger size images, or did you spot this also for 
much smaller files?

I'm puzzled myself! A 3.8MB file and a ~ 6MB file worked. But a couple of
4.1MB files and a ~7MB file did not, so it's not like I'm seeing a direct
correlation with file size. Maybe there's something about the complexity of
the encoding...bit depth...something that makes the internal processing

3) We need more license options in the drop-down file upload box

That was an easy task, they're added now. :)

Great! :-)


Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.