On Mon, 7 Sep 2009, Graeme Geldenhuys wrote:
Hi,
Maybe it's just me (please let me know if it is), but looking at the
various FPC .pdf files in a folder, I am never sure which one I should
open for whatever I am looking for.
We currently have:
ref.pdf
user.pdf
rtl.pdf
prog.pdf
fcl.pdf
In our previous episode, Graeme Geldenhuys said:
> Out of those 3 seems to have logical names. rtl, fcl and fpdoc. The
> problem I have is the 'user', 'ref' and 'prog' names. Maybe somebody
> can explain to me how I can remember the various information in each of
> these. For example, if I want to
In our previous episode, Michael Van Canneyt said:
> > Yes I know I can rename them locally, but I also thing it makes sense to
> > give the documents better "default" names than ref, prog, user.
>
> If there is a more or less consensus about such things, I don't see why
> we couldn't rename them.
Hi,
I'm all about saving the planet and saving our trees, but currently
reading documentation on-screen (no matter how hard I try), is just not
as comfortable as reading from a book. I don't have these $350+ eBook
readers, so I can't comment on them with there e-Ink technology screens.
Does any of
Hi,
Considering that LaTeX does a really good job about text layout and
styling, I was very surprised to notice the following issue in the
RTL.pdf document.
See attached image. The section numbers and section headings overlap
each other in the Contents pages. Can this be fixed, or is it a bug in
Michael Van Canneyt het geskryf:
>
> If there is a more or less consensus about such things, I don't see why
> we couldn't rename them.
Glad to hear you are willing to consider this. ;-)
> The names actually stem from the TP documentation, which was divided into 3
> books:
> Language Reference
In our previous episode, Graeme Geldenhuys said:
> OK, in the list above "Language Reference" seems obvious, but everywhere
> else (as far as I remember) it is listed as FPC Reference Guide, which
> isn't obvious.
(in the pre-fpdoc past, the reference guide also included the system unit
reference)
> > Yes I know I can rename them locally, but I also thing it makes sense to
> > give the documents better "default" names than ref, prog, user.
>
> If there is a more or less consensus about such things, I don't see why
> we couldn't rename them.
>
>
I agreed with Graeme.
FPC is very well document
In our previous episode, Graeme Geldenhuys said:
> My problem is the RTL document. It is HUGE! Last time I checked, it was
> just under 1600 pages.
>
> * Is it worth printing this document? Or does it make more sense to only
> print the language and compiler guides?
>From 2000-2003 I used the i
On Mon, 7 Sep 2009, Graeme Geldenhuys wrote:
Michael Van Canneyt het geskryf:
If there is a more or less consensus about such things, I don't see why
we couldn't rename them.
Glad to hear you are willing to consider this. ;-)
The names actually stem from the TP documentation, which was
On Mon, 7 Sep 2009, Graeme Geldenhuys wrote:
Hi,
Considering that LaTeX does a really good job about text layout and
styling, I was very surprised to notice the following issue in the
RTL.pdf document.
See attached image. The section numbers and section headings overlap
each other in the Con
On Mon, 7 Sep 2009, Marco van de Voort wrote:
In our previous episode, Michael Van Canneyt said:
Yes I know I can rename them locally, but I also thing it makes sense to
give the documents better "default" names than ref, prog, user.
If there is a more or less consensus about such things, I
Graeme written:
>
> My problem is the RTL document. It is HUGE! Last time I checked, it was
> just under 1600 pages.
>
> * Has anybody else printed the RTL document? If so, how did you bind it?
> No printer here wants to bind such a huge book.
> - Graeme -
>
>
I suggest the FPC dev team to con
In our previous episode, Michael Van Canneyt said:
> > See attached image. The section numbers and section headings overlap
> > each other in the Contents pages. Can this be fixed, or is it a bug in
> > LaTeX?
>
> Probably there is some obscure option to set the width of the indent of the
> conten
Marco van de Voort het geskryf:
>
> At the uni I had a big 5SI with a duplex unit, so printing double
> sided in A5 format was easy. I usually didn't cut it though, just
Our company has huge printers as well — they do everything but make
coffee. Apparently that's an optional extra. ;-) We often p
In our previous episode, Graeme Geldenhuys said:
> Marco van de Voort het geskryf:
> >
> > At the uni I had a big 5SI with a duplex unit, so printing double
> > sided in A5 format was easy. I usually didn't cut it though, just
>
> Our company has huge printers as well ?
Well, it was more an impl
On Mon, 7 Sep 2009, Marco van de Voort wrote:
In our previous episode, Michael Van Canneyt said:
See attached image. The section numbers and section headings overlap
each other in the Contents pages. Can this be fixed, or is it a bug in
LaTeX?
Probably there is some obscure option to set th
Corrado Valeri het geskryf:
>
> I suggest the FPC dev team to consider the option to publish on lulu.com
I actually thought this was done already. I searched the lulu.com
website yesterday, but couldn't find any Free Pascal specific content.
The problem I have with Lulu.com is that as far as I k
On Mon, 7 Sep 2009, Corrado Valeri wrote:
Graeme written:
My problem is the RTL document. It is HUGE! Last time I checked, it was
just under 1600 pages.
* Has anybody else printed the RTL document? If so, how did you bind it?
No printer here wants to bind such a huge book.
- Graeme -
Michael Van Canneyt het geskryf:
>
> Well, if there is enough demand, we could definitely consider this.
Does it cost anything to become a publisher on lulu.com? I thought it's
free and that you only need to upload the PDF document to them. Then
they get a percentage from an actual sale. I didn't
On Mon, 7 Sep 2009, Graeme Geldenhuys wrote:
Michael Van Canneyt het geskryf:
Well, if there is enough demand, we could definitely consider this.
Does it cost anything to become a publisher on lulu.com? I thought it's
free and that you only need to upload the PDF document to them. Then
the
Michael Van Canneyt het geskryf:
>
> Since you now discovered what each document describes, the problem has
> solved itself :-)
My brain is saturated with other information. By the end of the week I
would have forgotten all this already. :-) To help myself, I locally
renamed the PDF documents to
Michael Van Canneyt het geskryf:
>
> Also, we'd need someone to design a cover for the books.
> My graphical skills are worse than horrible :-)
I saw they actually have a few cover templates one can use and a small
cover wizard. I do not know how good the end-result is, but it should
suffice in
Michael Van Canneyt het geskryf:
>
> Like I said, the FPC docs use LaTeX to the fullest...
Can the contents be multi-column like the Delphi/Kylix documentation.
This allow for more information being visible at once. I also don't
know if it is needed to have the section numbers in the Contents pa
On Mon, 7 Sep 2009, Graeme Geldenhuys wrote:
Michael Van Canneyt het geskryf:
Like I said, the FPC docs use LaTeX to the fullest...
Can the contents be multi-column like the Delphi/Kylix documentation.
This allow for more information being visible at once. I also don't
know if it is neede
On 07 Sep 2009, at 08:53, Graeme Geldenhuys wrote:
Maybe it's just me (please let me know if it is), but looking at the
various FPC .pdf files in a folder, I am never sure which one I should
open for whatever I am looking for.
For the Mac OS X releases, I rename them before packing the instal
Jonas Maebe het geskryf:
>
> For the Mac OS X releases, I rename them before packing the installer.
> The names I use are:
Much better names. :-) I think my main problem is distinguishing
between the Programmers Manual and the Users Manual. See, I am both — so
I never know which PDF to view fo
Jonas Maebe het geskryf:
> For the Mac OS X releases, I rename them before packing the installer.
> The names I use are:
>
> Code Documenter.pdf
> Compiler Switches.pdf
> Free Component Library.pdf
> Language Reference Guide.pdf
> Programmer's Manual.pdf
> Units Reference Guide.pdf
> User's Manu
On Mon, 7 Sep 2009, Jonas Maebe wrote:
On 07 Sep 2009, at 08:53, Graeme Geldenhuys wrote:
Maybe it's just me (please let me know if it is), but looking at the
various FPC .pdf files in a folder, I am never sure which one I should
open for whatever I am looking for.
For the Mac OS X releas
Michael Van Canneyt het geskryf:
>
> Spaces and quotes are vetoed as a general rule :)
Such an "old" file-system limitation does not apply in newer OS versions
anymore. I must say, old habits die hard! :) I often find myself naming
eBooks, TV series or music with underscores instead of spaces. Bu
On 07 Sep 2009, at 11:44, Michael Van Canneyt wrote:
On Mon, 7 Sep 2009, Jonas Maebe wrote:
On 07 Sep 2009, at 08:53, Graeme Geldenhuys wrote:
For the Mac OS X releases, I rename them before packing the
installer. The names I use are:
Code Documenter.pdf
Compiler Switches.pdf
Free Compo
In our previous episode, Jonas Maebe said:
> > Spaces and quotes are vetoed as a general rule :)
>
> That's fine as a general rule, but at least on Mac OS X specifically
> it's no problem. I think more documents and applications (other than
> the command line unix ones) than not have a space i
On Mon, 7 Sep 2009, Graeme Geldenhuys wrote:
Michael Van Canneyt het geskryf:
Spaces and quotes are vetoed as a general rule :)
Such an "old" file-system limitation does not apply in newer OS versions
anymore. I must say, old habits die hard! :) I often find myself naming
eBooks, TV series
On 07/09/2009 11:00, Jonas Maebe wrote:
On 07 Sep 2009, at 11:44, Michael Van Canneyt wrote:
On Mon, 7 Sep 2009, Jonas Maebe wrote:
...
Spaces and quotes are vetoed as a general rule :)
That's fine as a general rule, but at least on Mac OS X specifically
it's no problem. I think more
On 07 Sep 2009, at 12:30, Frank Peelo wrote:
In Linux, and I guess other unixish OSes like the Mac, it's quite
possible to have spaces or punctuation in file names. That doesn't
mean they're a good idea.
Since they're ubiquitous already anyway on Mac OS X (partly due to its
heritage of c
My 2 cents are that the worst problem with the docs is this: Very often I do
not know in which one to look for what i want to know or similarly I have to
look in three of them at the same time. In my view rtl and fcl are even more
important than user, ref and prog, and therefore should be includ
On Mon, 7 Sep 2009 12:12:42 +0200 (CEST), Michael Van Canneyt wrote
about Re: [fpc-pascal] The names of the various FPC documentation:
> On Mon, 7 Sep 2009, Graeme Geldenhuys wrote:
>
> > Such an "old" file-system limitation does not apply in newer OS
> > versions anymore. I must say, old habits
Michael Van Canneyt wrote:
On Mon, 7 Sep 2009, Graeme Geldenhuys wrote:
Michael Van Canneyt het geskryf:
Well, if there is enough demand, we could definitely consider this.
Does it cost anything to become a publisher on lulu.com? I thought it's
free and that you only need to upload the PD
38 matches
Mail list logo
