Re: Chrome bez H.264

Article View: pl.comp.os.advocacy

Article #481111

Back to pl.comp.os.advocacy Previous Next

#481111

From: Bart Ogryczak
Date: Thu, 13 Jan 2011 12:42

20 lines
2268 bytes

On Jan 13, 12:03 pm, Andrzej Libiszewski
<a.libiszew...@gazeta.usunto.pl> wrote:
> Dnia Thu, 13 Jan 2011 02:59:51 -0800 (PST), Bart Ogryczak napisał(a):
>
>
>
> >>> Flash ma się nijak do <video> z HTML5. Co więcej, zwolennicy H.264 w
> >>> <video> są jednocześnie przeciwnikami Flasha.
>
> >>> BTW. Chrome ma wbudowany Flash.
>
> >> I dlatego całe pitolenie o wolnym kodeku i miłości bliźniego z ich strony
> >> jest bzdurą.
>
> > Flash niesie za sobą jakieś zagrożenie patentowe?
>
> A H.264 niesie?

Oczywiście. A w przypadku H.264 wewnątrz Flasha, ewentualne zagrożenia
patentowe są zagrożeniami dla Adobe, nie dla producenta przeglądarki.

Technical Details

Message-ID: <30e94564-139e-42e7-9c0b-f87d99e5088b@z5g2000yqb.googlegroups.com>

Path:

mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!news.supermedia.pl!news.nask.pl!news.nask.org.pl!news.unit0.net!news2.euro.net!feeder.news-service.com!postnews.google.com!z5g2000yqb.googlegroups.com!not-for-mail

References:

<1667f9fa-1c3e-46b5-946c-4527df550e80@f8g2000yqd.googlegroups.com> <slrniirm77.lrm.mikmach@blacher.nos> <0d423da9-d24f-496d-9975-02018d37977c@l8g2000yqh.googlegroups.com> <igl1m0$81s$1@news.net.icm.edu.pl> <43d25697-e5f2-49da-9feb-bf79feab41bc@r29g2000yqj.googlegroups.com> <14fpy3d15xvr1$.1mph0d9tundo8.dlg@40tude.net> <be3ed1d3-bbd1-4fc1-a9ff-ef31b74cb5d1@z19g2000yqb.googlegroups.com> <bqj0k2lixdyb.jf019pic1pkg$.dlg@40tude.net>

Show Full Headers

Complete Article Headers

Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!news.supermedia.pl!news.nask.pl!news.nask.org.pl!news.unit0.net!news2.euro.net!feeder.news-service.com!postnews.google.com!z5g2000yqb.googlegroups.com!not-for-mail
From: Bart Ogryczak <b.ogryczak@gmail.com>
Newsgroups: pl.comp.os.advocacy
Subject: Re: Chrome bez H.264
Date: Thu, 13 Jan 2011 04:42:42 -0800 (PST)
Organization: http://groups.google.com
Lines: 24
Message-ID: <30e94564-139e-42e7-9c0b-f87d99e5088b@z5g2000yqb.googlegroups.com>
References: <1667f9fa-1c3e-46b5-946c-4527df550e80@f8g2000yqd.googlegroups.com> <slrniirm77.lrm.mikmach@blacher.nos> <0d423da9-d24f-496d-9975-02018d37977c@l8g2000yqh.googlegroups.com> <igl1m0$81s$1@news.net.icm.edu.pl> <43d25697-e5f2-49da-9feb-bf79feab41bc@r29g2000yqj.googlegroups.com> <14fpy3d15xvr1$.1mph0d9tundo8.dlg@40tude.net> <be3ed1d3-bbd1-4fc1-a9ff-ef31b74cb5d1@z19g2000yqb.googlegroups.com> <bqj0k2lixdyb.jf019pic1pkg$.dlg@40tude.net>
NNTP-Posting-Host: 94.100.112.225
Mime-Version: 1.0
X-Trace: posting.google.com 1294922562 27274 127.0.0.1 (13 Jan 2011 12:42:42 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Thu, 13 Jan 2011 12:42:42 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: z5g2000yqb.googlegroups.com; posting-host=94.100.112.225; posting-account=1kG_1AoAAADLEA3eucGvO2J-Uo4aPCW_
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.47 Safari/534.13,gzip(gfe)
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Reply to Parent Message