Page MenuHomePhabricator

Bad Parsoid FLAC media handling (use FLAC instead of OGG)
Closed, DuplicatePublic

Description

Using the following code:
[[File:Hmv-db2291-32-4807-2wx766.flac]]

generates code with urls pointing to the flac file, but this should point to the ogg file (which is the version of the file which is adapted to the web).


Version: unspecified
Severity: normal

Details

Reference
bz56304

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 2:16 AM
bzimport added a project: Parsoid.
bzimport set Reference to bz56304.

Parsoid probably shouldn't need to know details of media rendering, which is potentially infinitely extensible.

I would expect Parsoid to only deal with placeholders that actual media viewers get inserted into...

(In reply to comment #1)

Parsoid probably shouldn't need to know details of media rendering, which is
potentially infinitely extensible.

I would expect Parsoid to only deal with placeholders that actual media
viewers
get inserted into...

Is there an API that we can call to get the current core media rendering for things that are not simple images? In the worst case we could probably abuse action=parse.

We have not given the desired semantic DOM structure for videos or sounds much thought yet. It would be tempting to use native video / audio html5 tags and let shims handle the fall-back for clients that don't support it.

I have some ideas for creating a cleaner interface for this sort of thing; I'll write up some notes...

(In reply to comment #4)

Ok threw some quick notes up at
https://www.mediawiki.org/wiki/User:Brion_VIBBER/
Media_rendering_encapsulation

@brion: Images are handled according to https://www.mediawiki.org/wiki/Parsoid/MediaWiki_DOM_spec#Images

For video / audio, my initial instinct would be to spec something similar using video and audio tags in a way that works directly on modern browsers, and let shims handle legacy clients.

Yeah I started adding markup notes along those lines -- I'm a bit unclear on where all the media parameters end up though; particularly width and height *must* be retained and I think there may be some additional custom properties... images may include a page specifier (for DjVu, PDF, etc), and TimedMediaHandler items may have things like a start time.

I can certainly envision additional custom parameters on other types -- a 3d model viewer might have initial camera parameters or lighting setup, an animation may want to indicate that it should autoplay or loop (like animated GIFs do) as an alternative to non-autoplaying audio/video behavior.

How do we pass those through if Parsoid and VE don't know about them specifically?

Arlolra set Security to None.

What the status on this? Does the Parsoid dev team has a timeline to implement this?

@Kelson: @cscott is looking at multimedia support in Parsoid this quarter (T64270). Scott: Take a look at Brion's notes up there as well.

OLPC and other Educational/offline users of Wikipedia impoverished/offline schools keep asking us for more vids, maps & historical photographs. They say that textual Wikipedia is just not enough, for elementary and middle schools especially.

So 32G, 64G and even 128G SD cards are really beginning to save the day here, with more underserved areas than we can count :/

While I don't understand all the issues yet, this is our #1 request in developing world schools adopting schoolserver.org and similar technologies emerging from OLPC, so I want to help...Thanks everyone who understood this emerging need years ago!!