Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

On 06/25/2011 03:37 PM, Alexandro Colorado wrote:
On Sat, Jun 25, 2011 at 7:37 AM, Simon Phipps <> wrote:

On 25 Jun 2011, at 08:33, Ian Lynch wrote:

Manfred wrote:

"I still believe that PDF is the best solution to distribute final
of text (and maybe other office) documents."

I'd say yes if they are likely to be printed on paper, no if it is only
likely to be read from a screen.

I disagree. Once a document no longer needs editing (and this is a frequent
need in daily life - think purchase receipt, invoice, insurance schedule and
so on) it needs to be provided in an electronic format that cannot be easily
altered. PDF plays this role, ODF doesn't.

No, but HTML does. More to the point, chm files also are build for
read-only. Surely they are more microsoft based, but even Read (activity
from the OLPC/Sugar), had to add a webkit renderer for another popular
format -- epub. Which of course is done for read-only porpouses.

So a bigger discussion than demanding PDF reader, might be to upgrade the
very old HTML renderer in LibreOffice to something like webkit.
This might be of interest:
[pdf.js: Rendering PDF with HTML5 and JavaScript]
[pdf.js reached its first milestone]

Perhaps that could be modifed/integrated to also view .odt etc?

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.