To be clear, there are generally no objections to "1) accept FLIF (and possibly
serve PNG thumbs for browsers without js" other than convince commons
it would be a good idea to accept the format. All the controversial
bit is converting files to FLIF. Accepting FLIF files for upload is
I concur with the extension idea.
I'd add that have options for degrees of using FLIF would be a good idea as
well. I.E. the decision could be to simply 1) accept FLIF (and possibly
serve PNG thumbs for browsers without js), to 2) encourage FLIF use, or to
3)"force" FLIF by converting everything
If you want to work on implementing support for FLIF, I would recommend
doing it as an extension (similar to e.g.
https://www.mediawiki.org/wiki/Extension:PdfHandler) rather than in
MediaWiki core.
--
Bartosz Dziewoński
___
Wikitech-l mailing list
10 дек. 2017 г. 23:42 пользователь "Ruben Kelevra"
написал:
So... to break the current discussion down, there is no hard "we
don't want this format" yet shown up.
Nope, you've been provided ample reasons why a phab ticket requesting this
will probably be declined on the
Hey Brian,
On 11.12.2017 00:10, Brian Wolff wrote:
> Maybe not a hard no, but I would rate the probability as somewhere around
> 1%.
>
> If you really wanted to push this (with the understanding that its probably
> not going anywhere) I would say make a report, comingup with a solid case
> with
Maybe not a hard no, but I would rate the probability as somewhere around
1%.
If you really wanted to push this (with the understanding that its probably
not going anywhere) I would say make a report, comingup with a solid case
with a solid implementation plan, including:
* what is the fallback
Hey Andre,
On 10.12.2017 22:10, Andre Klapper wrote:
> On Sun, 2017-12-10 at 21:42 +0100, Ruben Kelevra wrote:
>> So... to break the current discussion down, there is no hard "we
>> don't want this format" yet shown up.
>>
>> What's the next step guys?
>
> Working on widespread FLIF support
Sadly Google stick to cheer for their WebP-crap, my ticket #539120 for
the chromium project dated back to late 2015, while there are some
supporters, the main reason was back then 'it's not yet finalized' which
isn't true anymore.
Since we need the Poly-flif stuff anyway - not any user uses the
On Sun, 2017-12-10 at 21:42 +0100, Ruben Kelevra wrote:
> So... to break the current discussion down, there is no hard "we
> don't want this format" yet shown up.
>
> What's the next step guys?
Working on widespread FLIF support among browsers/clients, to not
require JavaScript support in
So... to break the current discussion down, there is no hard "we
don't want this format" yet shown up.
What's the next step guys? Generate a feature request for MediaWiki
which enables FLIF as possible input-format and ships the poly-flif
JavaScript library for browsers which does not
Hey Thiemo,
On 06.12.2017 14:27, Thiemo Kreuz wrote:
>> Point was more: Get rid of this bloody Download a JPG, do some Stuff &
> Upload a 3 Times locally saved JPG again […]
>
> I'm afraid I did not made my point clear enough. With all respect to your
> enthusiasm, but the scenario you describe
Le 06/12/2017 à 14:27, Thiemo Kreuz a écrit :
Sure. Go and encourage people to upload RAW. That's very much welcome.
Is it? I thought that Commons didn't include a RAW file format in its
list of authorized file type.
___
Wikitech-l mailing list
> Point was more: Get rid of this bloody Download a JPG, do some Stuff &
Upload a 3 Times locally saved JPG again […]
I'm afraid I did not made my point clear enough. With all respect to your
enthusiasm, but the scenario you describe is exactly what your suggestion
will not improve. How could it?
Changing a crucial element of the fifth most popular website on the
Internet may be a good example for an article about [[PITA]] :D
While I'm open to new formats/technologies I think a fundamental
prerequisite is a widespread support among browsers/clients. JS-only
support will severely weaken
An encode latency of 7 seconds and decode latency of 1 second arent what I
would call "very fast" (the decode latency measurement probably isnt
realistic as decode and encode to png is different from just display in
browser. Then again all these measurements are going to vary by filesize,
not to
On Mon, Dec 4, 2017 at 10:34 AM Ruben Kelevra wrote:
> > Sure, your suggestion avoids a lot of this. But the CPUs involved will
> > experience heavy load, both on the server as well as clients that need
> > to recode FLIF files via a JavaScript library first.
> FLIF is very
Hey Thiemo,
On 04.12.2017 10:43, Thiemo Kreuz wrote:> I consider myself an image
file format nerd, so thanks a lot for
> sharing this! FLIF was new to me.Don't mind it! :)
> I would like to share two important notes:
>
> 1. Unfortunately the flif.info website does not say a word about the
> CPU
Hey,
I consider myself an image file format nerd, so thanks a lot for
sharing this! FLIF was new to me.
I would like to share two important notes:
1. Unfortunately the flif.info website does not say a word about the
CPU resources their current implementation burns when converting a,
let's say,
I've picked a featured image of today for a small demonstration:
$ du -h Mansudae-Monument-Bow-2014.* | sort -n
2,0MMansudae-Monument-Bow-2014.jpg
4,9MMansudae-Monument-Bow-2014..progressiv.jpg *
6,5MMansudae-Monument-Bow-2014.flif
16M Mansudae-Monument-Bow-2014.png
*(saved again
Hey Andre,
On 03.12.2017 00:49, Andre Klapper wrote:
> On Sat, 2017-12-02 at 22:20 +0100, RubenKelevra wrote:
>> There's a small JavaScript library which can be used until there's a
>> browser support given, so theres no need to wait until there is
>> browser-support.
>
> Please provide a link to
The library can be found here: http://flif.info/
Sent from my iPhone
> On Dec 2, 2017, at 5:49 PM, Andre Klapper wrote:
>
> Hi,
>
>> On Sat, 2017-12-02 at 22:20 +0100, RubenKelevra wrote:
>> There's a small JavaScript library which can be used until there's a
>>
Hi,
On Sat, 2017-12-02 at 22:20 +0100, RubenKelevra wrote:
> There's a small JavaScript library which can be used until there's a
> browser support given, so theres no need to wait until there is
> browser-support.
Please provide a link to that library.
Thanks,
andre
--
Andre Klapper |
Hey guys,
some years ago I stumbled across the FLIF-format, which might be very
interesting for wikimedia commons and/or Mediawiki in general.
I try to summon the fileformat and it's advantages a bit:
It's a free, patent free, lossless image compression format, which
supports RGB(A) /
23 matches
Mail list logo