Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5A872DB9E for ; Fri, 26 Oct 2012 09:06:26 +0000 (UTC) Received: (qmail 5416 invoked by uid 500); 26 Oct 2012 09:06:26 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 5285 invoked by uid 500); 26 Oct 2012 09:06:25 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 5267 invoked by uid 99); 26 Oct 2012 09:06:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Oct 2012 09:06:25 +0000 X-ASF-Spam-Status: No, hits=2.3 required=5.0 tests=HK_RANDOM_ENVFROM,HK_RANDOM_FROM,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [193.95.142.37] (HELO mail05.mail.esat.net) (193.95.142.37) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Oct 2012 09:06:18 +0000 Received: from (100AkerWood) [109.78.198.244] by mail05.mail.esat.net with smtp id 1TRfrX-0003YI-81; Fri, 26 Oct 2012 10:05:55 +0100 Date: Fri, 26 Oct 2012 10:05:54 +0100 From: Rory O'Farrell To: ooo-dev@incubator.apache.org Subject: Re: Apache and ODF Message-Id: <20121026100554.b437203354d7c3a2e4cf7a28@iol.ie> In-Reply-To: References: X-Mailer: Sylpheed 3.2.0 (GTK+ 2.24.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Fri, 26 Oct 2012 09:58:25 +0100 Ian Lynch wrote: > On 26 October 2012 08:42, Fan Zheng wrote: >=20 > > Hi, All: > > > > I am confused about the UX specifications of document representation > > requirement on mobile devices, that which is the most first important p= oint > > should be, the different device condition adaptability of layout result= ? or > > the fidelity of the document originally recorded? > > > > For example. An ODT format text document with several pages sized as > > "Letter", which is physically defined as 279:216 (ratio as 1.29), and u= ser > > want to render it in a Kindle Fire, which supplies a 1024:600 (ratio as > > 1.71) screen for presenting. >=20 >=20 > Is it possible to have choices? Keep the original page aspect ratio and > scroll (Never used a kindle so not sure if it can scroll but obviously > Android on phones can!) or have a "fit to aspect" where the page is scaled > to the kindle in AOO befor export. If one of the pre-defined page templat= es > in AOO was the kindle page size it would be possible to reformat the pages > in a document to that size just as you can change from say A4 to US lette= r. > Probably for complex documents with graphics this would break some parts = of > the layout but for the sort of text only novels etc mostly used on these > devices it should work well enough. This assumes you can export to > epub/mobi format in any scale but I'm assuming that will be similar to > export to pdf. Of course the resulting document layout could be checked by > viewing the epub/mobi output. Having an odf viewer for the mobile devices > would be an alternative method and probably less constrained than using > epub formats but it is also more work to do it. OTOH a versatile odf read= er > for mobile devices could be very useful in helping establish odf as the > open standard for all types of document. >=20 >=20 > > If we do much more care about the adaptability > > of representation, lots data recorded inside the file will be changed, > > removed or even ignored. But, if we care about the fidelity much more, = we > > have to record all the document data inside, and rendering it on the > > devices dutifully. In the case, all we could do for the UX, is to give = some > > adjustable scale. Such differences are meaning not only the pagination > > stuff, but also some solid data inside: thinking about a full > > page-width-size table for instance. > > >=20 > There can be issues with documents that have both portrait and landscape > pages in them on normal computer screens. >=20 > > > > Of cause, all the former document editor/viewer applications for deskto= p, > > will obey the "Keep Fidelity" as the very first rule. But what about the > > mobile device platforms? > > > > As such differences will actually lead the solution into the different > > direction, we maybe should make it clear before having a deeper discuss= ion. > > > > Thanks. > > > > ZhengFan > > > > > > 2012/10/26 Andreas S=E4ger > > > > > Am 25.10.2012 21:14, Rob Weir wrote: > > > > > > > > If you search for it, you will find various solutions for converting > > > > ODF to EPub. But I have not seen something that does the same for > > > > Kindle's MOBI format. > > > > > > > > -Rob > > > > > > > > > > Thank you. I know about the converters. The problem is that all our > > > office documents are ODF documents. The Kindle device does not provide > > > any access to our documents until they have been converted by some ot= her > > > device. > > > In this discussion it is important to specify clearly which Kindle is the t= arget device, as the screen ratio and pixel count varies from device to dev= ice with the newer Kindles. A stranger coming to this discussion might ass= ume that Kindle genericly refers to the normal "reading" Kindle, with an 80= 0h x 600w screen, which is the common Kindle in use. --=20 Rory O'Farrell