Re: TheWebConf 2018 Trip Report

> On 1 May 2018, at 01:27, Harshvardhan J. Pandit <me@harshp.com> wrote:
> 
> Great report Sarven, it is very well put!
> With PDF (vs HTML), the issue is PDF being (seen as) an end or viewing format. It abstracts out the underlying complexity of representations, and lots of tools can spew out a PDF. With HTML, it is like asking everyone to write their work in LaTeX only (which isn't bad in itself).
> Maybe a point of convergence could be to get everything to produce decent HTML which isn't mangled by inherent messy CSS+JS native to the product/tool?
> I (still) see "Microsoft Word..." in the title-bars of PDFs people submit, so I assume that a lot of people cannot or don't want to write their papers in LaTeX or other tools.
> How to work towards exporting this text-based writing approach to native web formats?

Actually Apple's Pages produces epub format which is html plus some extra packaging
zipped together in one file.

I put my "Epistemology in the Cloud" up in PDF and epub format here
http://bblfish.net/blog/2018/04/21/

Is there a way to get browsers to turn into an ePub reader? Then I could
just unzip it and make it visible as html.

Henry


> 
> On Monday 30 April 2018 10:29 PM, Sarven Capadisli wrote:
>> Remark: PDF can be still welcomed because fundamentally there shouldn't
>> be any discrimination on how someone wants to communicate their work
>> (*). If a "Linked Data" researcher feels that PDF is the best way to
>> communicate and disseminate their knowledge, that's their call. So, I
>> think we shouldn't set that restriction, but then we are damned to make
>> it hard on ourselves. Ohwell, let's see how else we can move things
>> forward... perhaps more how-tos and stuff - something the other chairs
>> suggested before the event even.
> 
> -- 
> ---
> Harshvardhan J. Pandit
> PhD Researcher
> ADAPT Centre, Trinity College Dublin
> https://harshp.com
> GPG: D81BF4F31D31B413
> 
>

Received on Tuesday, 1 May 2018 11:24:23 UTC