W3C home > Mailing lists > Public > public-media-fragment@w3.org > January 2010

Re: spec review

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Wed, 27 Jan 2010 21:45:39 +1100
Message-ID: <2c0e02831001270245if3dc427x3036866a7960b1ad@mail.gmail.com>
To: tmichel@w3.org
Cc: raphael.troncy@eurecom.fr, Philip Jšgenstedt <philipj@opera.com>, public-media-fragment@w3.org
The file that displays incorrectly
(http://www.w3.org/TR/media-frags-reqs/) is being delivered by the Web
server as:

Content-Type	text/html; charset=iso-8859-1

while the same file from
http://www.w3.org/2008/WebVideo/Fragments/WD-media-fragments-reqs/ is
being delivered as:

Content-Type	text/html; charset=utf-8

I think it may be a server setup for this file.


On Wed, Jan 27, 2010 at 9:28 PM, Thierry MICHEL <tmichel@w3.org> wrote:
> I have requested to Webreq (Webmaster) to fix this encoding issue.
> http://www.w3.org/TR/media-frags-reqs/
> Only the webmaster can fix documents on TR space.
> The document was fine on publication (checked by webmaster and conformant to
> publication rules).
> http://www.w3.org/TR/2009/WD-media-frags-reqs-20091217
> it is still fine, but curiously the †alias done by the webmaster pointing to
> the same document is showing encoding issues
> http://www.w3.org/TR/media-frags-reqs/
> Thierry
> RaphaŽl Troncy wrote:
>> Hi Philip,
>>> I've hacked away at the spec and have something I want comments on. What
>>> can I do to make it available for all to see, short of putting it on my
>>> own webserver? Checking it in on a CVS branch seems sane, but would it
>>> be possible for others to view the results?
>> To clarify that:
>> †- the documents published in the /TR space if frozen and has been
>> approved by the group prior to its publication (e.g.
>> http://www.w3.org/TR/media-frags-reqs/).
>> †- the documents published in our group space are evolving, non stable,
>> they are our working draft (I need to change the css to show that), (e.g.
>> http://www.w3.org/2008/WebVideo/Fragments/WD-media-fragments-reqs/). You can
>> change the later as you wish. Commit directly in cvs. Send a mail to the
>> mailing list and make sure your changes are discussed by the group in a
>> upcoming telecon. We can reverse back these changes if not approved.
>> †RaphaŽl
Received on Wednesday, 27 January 2010 10:46:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:52:44 UTC