Re: [pwp] Progressive enhancement of digital books

On Dec 2, 2015, at 4:27 AM, AUDRAIN LUC <LAUDRAIN@hachette-livre.fr> wrote:

>
> For the sake of the demo, I donıt see why in slide 5, you donıt give
> href="nav.html" in the link in c0001.html?
> Obviously as the link points to a non existant file, it doesnıt work in
> ordinary browser as shown in slide 5.
> but with a link pointing to nav.html, it should work or is index.html a
> reserved name?
>

I did a poor job of explaining. If you have the URL of the folder, but don't know what's inside the folder, a browser won't generally display any of the content unless it finds an index.html file (or something like an .htaccess file, if the server supports it). But if we have nav.html and rename it to index.html, then any browser will open index.html when you go to the folder URL. It's just a convention that makes it easy to find this critical document.

Thanks,

Dave

>
> Le 01/12/2015 19:51, Ğ Cramer, Dave ğ <Dave.Cramer@hbgusa.com> a écrit :
>
>> Hi Everyone,
>>
>> Just for fun, I put together some slides on the progressive enhancement
>> of ebooks. You can download the PDF at [1]. This might serve as
>> background for our discussions of PWP formats, Acme Publishing, etcetera.
>>
>> Thanks,
>>
>> Dave
>>
>> [1] https://lists.w3.org/Archives/Public/www-archive/2015Dec/0000.html
>> This may contain confidential material. If you are not an intended
>> recipient, please notify the sender, delete immediately, and understand
>> that no disclosure or reliance on the information herein is permitted.
>> Hachette Book Group may monitor email to and from our network.
>>
>
>

This may contain confidential material. If you are not an intended recipient, please notify the sender, delete immediately, and understand that no disclosure or reliance on the information herein is permitted. Hachette Book Group may monitor email to and from our network.

Received on Wednesday, 2 December 2015 16:26:15 UTC