Re: Matroshka

ChristianHJW wrote:
 >> Well, we need a name. That's for sure. (a name that can be turned
 >> into a verb (to matrosk/matroskate), an adjective
 >> (mastrosked/matroskated), a name (matroska), a process
 >> (matroskation)) If you don't like it, you can still propose some
 >> other ones. Many have tried so far, without much success. The last
 >> one was capsule/capsuline.

I'd simply keep Media Container Format, with Encapsulation as the verb, 
adjective and process. I got this term from some guy (back in 2001) from 
OpenDivX saying that AVI is the encapsulating format. I think this is a 
perfect term, as it's easy to understand, yet sounds like a professional 
term. The BAD thing to do, then, is to start calling the files Capsules, 
and randomly improvising on the word to make it sound like toothpaste or 
lubricant ("Capsuline, now with improved anti-caries formula", or 
"Capsuline, new from Durex"). Really, no offense meant.

 > I fully support you Steve, we need a 'friendly' name ! We need a
 > website with a nice, easy to remember URL  ( mf : mcf.sourceforge.net
 >  IS NOT EASY ENOUGH !! :-P ... nobody outside the opensource
 > landscape has a f..ing clue what sourceforge is, nor how to spell it
 > ).

mcf.sf.net. it's easier than any cjb.net or xrs.net or vze.com or 
whatever, and those URL services are super-popular too. Short things are 
easy to remember, and mcf.sf.net is as short as it gets. What's wrong 
with it?!

 > The name should ( in best case ) have a kind of menaing also, thats
 > why i liked 'matroshka' a lot, with respect to the dol in the doll in
 >  the doll ( one doll 'containing' / 'wrapping' another, smaller one )
 >  picture. But, if the name sounds completely unusual or not nice for
 > the whole english speaking users of MCF then we have to think of
 > another one.

Matroshka would suggest a container in a container, like how MPEG4 is 
handled within AVI. This is a bad thing to be associated with :-P.

 > Dont panic guys !!  Lets concentrate on the technical aspects for the
 > time being, and keep the name issue in the back of our minds. I am
 > sure one day somebody will come up with  THE name, and will like it
 > and agree to it. There is no reaosn to hurry with this, as long as we
 > dont release a MCF parser version with automatic codec download from
 > MCF server and we have to include the URL into the parser.

I think a simple redirect from http://mcf.sourceforge.net/codecs to a 
select list of mirrored codec download servers (that way sourceforge 
gets none of the real traffic, and people can set up mirrors on 
ultra-fast university or whatever servers, the location of which can 
change since the master list is on SF.net) would be fine.

 > Is this acceptable for all of you ?

Nope, see above comments :-P.

 > Christian
mf ;D





-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T 
handheld. Power & Color in a compact size! 
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en