Received-SPF: pass (google.com: domain of jimr1603@gmail.com designates 2607:f8b0:4001:c03::230 as permitted sender) client-ip=2607:f8b0:4001:c03::230;
MIME-Version: 1.0
In-Reply-To: <20131229110811.GA4842@samsa.fritz.box>
References: <20131227041501.GA21848@stodi.digitalkingdom.org>
	<4682a0d7-9b6b-453f-bc1c-6f9a4f450637@googlegroups.com>
	<20131228080656.GD15882@stodi.digitalkingdom.org>
	<20131228173537.GN22926@samsa.fritz.box>
	<20131229000115.GG15882@stodi.digitalkingdom.org>
	<20131229110811.GA4842@samsa.fritz.box>
Date: Sun, 29 Dec 2013 13:18:40 +0200
Message-ID: <CAH6YDUW3MzxuU-zB2_yS2EVSnXGyP3wwHog3oYjYtByhSW=xTQ@mail.gmail.com>
Subject: Re: [lojban] Re: The CLL project, technical directions
From: james riley <jimr1603@gmail.com>
To: lojban@googlegroups.com
Reply-To: lojban@googlegroups.com
Precedence: list
Mailing-list: list lojban@googlegroups.com; contact lojban+owners@googlegroups.com
Sender: lojban@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
X-Spam_score: 0.0
X-Spam_score_int: 0
X-Spam_bar: /

LaTeX has hyperlinks these days so we could make a PDF that isn't just
pages from a book.

On 29 December 2013 13:08, v4hn <me@v4hn.de> wrote:
> On Sat, Dec 28, 2013 at 04:01:16PM -0800, Robin Lee Powell wrote:
>> > Given that major web-browsers nowadays open pdf just like any html
>> > file through additional plugins and hyperlinks can be used in pdfs
>> > as well, what exactly are the reasons for generating HTML in the
>> > first place?
>>
>> PDF viewers are, almost without exception, steaming piles of crap?
>
> So are browsers.
>
>> Mostly it's just that a book-format PDF has completely different
>> user needs from a web page.  It's broken up by physical pages, which
>> is unnatural for the web, it doesn't wrap to fit the browser, etc.
>>
>> It's certainly a possible fallback, but it's pretty weak IMO.
>
> IMO that's nitpicking in this context. Yes, there are differences
> between HTML and PDF. But the CLL is ba'e the official document
> for lojban and I do not see why it has to be available in different
> formats to begin with.
>
> With multiple output formats you will always end up with situations like
> "hm, I could need some additional space in the pdf here" or "Argh, I hit a
> special case using this environment and now it looks awkward in this format".
> As far as I can see this is quite a problem at the moment.
> If you then introduce lots of this-format-only tags into your sources,
> you're basically back to your two-fork mess imo.
>
>> > The main problem you're trying to solve the whole time is
>> > generating HTML and PDF from one source. Granted, that's
>> > non-trivial, though possible.
>>
>> Quite.  The question is, how would I need to be doing it to get your help?
>
> docbook and xslt is a pretty confusing mess imho.
> If the CLL really uses only few features of this combination,
> it would really help quite a bit to have the whole conversion process
> in one ``simple'' module written for this specific translation task exactly.
> However, we might again end up with something very confusing.
>
>
> v4hn

-- 
You received this message because you are subscribed to the Google Groups "lojban" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lojban+unsubscribe@googlegroups.com.
To post to this group, send email to lojban@googlegroups.com.
Visit this group at http://groups.google.com/group/lojban.
For more options, visit https://groups.google.com/groups/opt_out.