[projectaon] Re: Grand Master comment period [Books 15-20]
- From: Jonathan Blake <jonathan@xxxxxxxxxxxxx>
- To: projectaon@xxxxxxxxxxxxx
- Date: Wed, 15 Aug 2012 11:00:50 -0700
On Sun, Aug 12, 2012 at 1:07 PM, Jonathan Blake <jonathan@xxxxxxxxxxxxx> wrote:
> On Thu, Aug 2, 2012 at 11:51 AM, Ingo Kloecker
> <projectaon@xxxxxxxxxxxxxxxx> wrote:
>> On Thursday 02 August 2012, Jonathan Blake wrote:
>>> On Thu, Apr 12, 2012 at 3:24 AM, Simon Osborne
>>> <outspaced@xxxxxxxxxxxx> wrote:
>>>
>>> Thanks for putting this list together, Simon.
>>>
>>> > BOOKS 1-28
>>> >
>>> > (ne) Illustration Captions: [so: In some books the longer captions
>>> > are broken up using <line> tags; in others they are not. Let's
>>> > decide which is better and standardise.]
>>>
>>> What the explicit line breaks are intended to do is turn cases like
>>> this where the automatic line wrapping creates an awkward
>>> presentation:
>>>
>>> ~~~~~
>>> Two men in ragged clothes are huddled together beside a small
>>> fire.
>>> ~~~~~
>>>
>>> Into this:
>>>
>>> ~~~~~
>>> Two men in ragged clothes are huddled
>>> together beside a small fire.
>>> ~~~~~
>>>
>>> This has been applied ad hoc because it's hard to know in advance
>>> when this will be a problem since letterforms have different widths.
>>>
>>> Thoughts?
>>
>> For the PDFs I have adjusted quite a few of those captions because the
>> linebreaks didn't work for the PDFs. In particular, I have changed all
>> 3-line captions to 2-line captions. Those adjustments have to re-done
>> each time the XMLs change.
>>
>> For the ebooks we should probably ignore those linebreaks when
>> converting the XML because there isn't a one-size-fits-all line length
>> for all ebook reader in both screen orientations and with all font
>> sizes.
>>
>> For HTML more or less the same applies as for ebooks although most
>> people will probably read the HTML versions with the default font size
>> and if they scale the whole web page with their browser, as is common
>> nowadays, instead of just changing the font size then the linebreaks
>> should still work.
>>
>> So, to sum up, for the PDFs I optimize them anyway, for the ebooks we
>> should ignore them and for the HTML versions I don't really have an
>> opinion. Or, in other words, I'm fine with optimizing the linebreaks in
>> the XMLs for the HTML versions provided this optimization is done just
>> once.
>
> This is making me lean toward not worrying about it and letting the
> line breaks fall where they may.
Hearing no objections, I went ahead and implemented this. Onward and upward.
--
Jon
~~~~~~
Manage your subscription at //www.freelists.org/list/projectaon
Other related posts:
