public inbox for documentation@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Daniel Weismüller" <whytea@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: [Documentation] Downloadable .pdf for Wiki sites
Date: Mon, 05 Mar 2012 08:53:49 +0100	[thread overview]
Message-ID: <4F54710D.70503@ipfire.org> (raw)
In-Reply-To: <1D6683AD-5A23-43A5-B73B-0DF4ACFE66BE@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 4577 bytes --]

Hi Erik! Hi Karl!

At first when I've read this idea I also thought that it would be nice.
But now I've thinked little more about it I must say that I think it is 
waste of time.

The reason is:
In every OS (linux, windows, mac os) you can printout websites as pdf.
So where is the advantage?

- Daniel

Am 04.03.2012 10:57, schrieb Erik K.:
> Hi Karl,
> good idea, i have done that -->  http://people.ipfire.org/~ummeegge/Wiki%20PDF/  ... but i´am still unhappy with the segmentation.
>
> A tip if you fill documentation(a)lists.ipfire.org into the reciver field, your mail comes along for all :-)
>
> Greetings
>
> Erik
>
> Am 04.03.2012 um 08:48 schrieb SCHUH Karl, SCHUH-TV:
>
>> Hi Erik,
>> I just had a look at the file - I am in a hurry :-(
>> Maybe you can add a ipfire-logo in the header - gives it a more "official" touch :-)
>>
>> regards
>> Karl
>>
>> ----- Ursprüngliche Mail -----
>>> Hello
>>> i have made now a little test to bring the installation Wiki in .pdf
>>> format. In here -->  http://people.ipfire.org/~ummeegge/Wiki%20PDF/ is
>>> a first revision. If someone would like to modify it also, there is
>>> also an .rtf version in the directory from the actual .pdf file.
>>> I formated some things new, wrote out the links and tried to give it a
>>> little more structure, but it isn´t finished.
>>>
>>> The converting thing goes quiet fast but to find a good looking format
>>> for the .pdf needs a little.
>>>
>>> May someone have new ideas or may done work :-) .
>>>
>>> Greetings to all
>>>
>>> Erik
>>>
>>>
>>> Am 03.03.2012 um 11:55 schrieb SCHUH Karl, SCHUH-TV:
>>>
>>>> Hi Erik,
>>>> of course links would be fine (inside the document and external
>>>> links too). If your system is up, they would be very useful. On the
>>>> other hand, this gives you even more to do. For me, priority No. 1
>>>> would be to have pdf's available. You can always add links, if your
>>>> sparetime allows it. If the links in plain text were clear
>>>> (something like: "link: document/paragraph"), they would be enough
>>>> to help you along.
>>>>
>>>> I am not sure which way to work ist more convenient html ->  pdf or
>>>> pdf ->  html. Maybe you should just try it.
>>>> Thanks for your work!
>>>>
>>>> Karl
>>>>
>>>> ----- Ursprüngliche Mail -----
>>>>> Hi Karl,
>>>>> exactly thats what i was thinking about, also there is a better way
>>>>> to
>>>>> print a docu out, for some reasons i think it is also more pleasant
>>>>> to
>>>>> work something out.
>>>>> So may i will start with a testing .pdf, eventual first for the
>>>>> installation Wiki (what do you think?) to find a suitable .pdf
>>>>> design.
>>>>> Should there also be active links ? What you think ?
>>>>>
>>>>> Greetings
>>>>>
>>>>> Erik
>>>>>
>>>>> Am 03.03.2012 um 10:24 schrieb SCHUH Karl, SCHUH-TV:
>>>>>
>>>>>> Hi,
>>>>>> superb idea. When you have trouble and need the documentation, it
>>>>>> could well be a lost internet connection :-((
>>>>>> You know - the devil never sleeps.
>>>>>>
>>>>>> Karl
>>>>>>
>>>>>> ----- Ursprüngliche Mail -----
>>>>>>> Hi all,
>>>>>>> what are you thinking about this idea, to make one downloadable
>>>>>>> .pdf
>>>>>>> file for each wiki theme ?
>>>>>>>
>>>>>>> Greetings to all
>>>>>>>
>>>>>>> Erik
>>>>>>> _______________________________________________
>>>>>>> Documentation mailing list
>>>>>>> Documentation(a)lists.ipfire.org
>>>>>>> http://lists.ipfire.org/mailman/listinfo/documentation
>>>>>> --
>>>>>> Ing. Karl SCHUH
>>>>>>
>>>>>> Hauptstraße 23a
>>>>>> A-7434 Bernstein
>>>>>> +43(664)38 06 107
>>>>> _______________________________________________
>>>>> Documentation mailing list
>>>>> Documentation(a)lists.ipfire.org
>>>>> http://lists.ipfire.org/mailman/listinfo/documentation
>>>> --
>>>> Ing. Karl SCHUH
>>>>
>>>> Hauptstraße 23a
>>>> A-7434 Bernstein
>>>> +43(664)38 06 107
>>> _______________________________________________
>>> Documentation mailing list
>>> Documentation(a)lists.ipfire.org
>>> http://lists.ipfire.org/mailman/listinfo/documentation
>> -- 
>> Ing. Karl SCHUH
>>
>> Hauptstraße 23a
>> A-7434 Bernstein
>> +43(664)38 06 107
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation

-- 
__________________________________________

You need a firewall?
Easy to use? Powerful? Modular? For free?

www.ipfire.org
An Open Source Firewall Solution


  reply	other threads:[~2012-03-05  7:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <19471799.8884.1330847338807.JavaMail.root@jupiter2>
2012-03-04  9:57 ` Erik K.
2012-03-05  7:53   ` Daniel Weismüller [this message]
2012-03-05 17:28     ` Erik K.
     [not found] <32635390.8742.1330772143686.JavaMail.root@jupiter2>
2012-03-03 18:02 ` Erik K.
     [not found] <20150959.8668.1330766651276.JavaMail.root@jupiter2>
2012-03-03 10:14 ` Erik K.
2012-03-03  8:43 Erik K.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F54710D.70503@ipfire.org \
    --to=whytea@ipfire.org \
    --cc=documentation@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox