From: info@drcomputer.nl
To: documentation@lists.ipfire.org
Subject: Promotion purposes maybe?
Date: Thu, 28 Mar 2013 15:19:17 +0100 [thread overview]
Message-ID: <51545165.1070409@drcomputer.nl> (raw)
In-Reply-To: <mailman.1.1364468402.22705.documentation@lists.ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2888 bytes --]
Dear Michael,
I will translate it anyway. Maybe you can use it to promote IPfire in
the netherlands. At the moment I'm using IPfire to protect my Virtual
Machines in VMware workstation. If I can figure out how it works, maybe
I can ditch my router too. Just a modem and IPfire.
It would also great to have IPfire for home use. For example, Android is
linux based and a lot of malware is written for it, I guess it is a
question of time for linux to become susceptible for attacks. Although I
know a few things about linux, i'm still not an expert.
The Ancient one.
Op 28-03-13 12:00, documentation-request(a)lists.ipfire.org schreef:
> Send Documentation mailing list submissions to
> documentation(a)lists.ipfire.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.ipfire.org/mailman/listinfo/documentation
> or, via email, send a message with subject or body 'help' to
> documentation-request(a)lists.ipfire.org
>
> You can reach the person managing the list at
> documentation-owner(a)lists.ipfire.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Documentation digest..."
>
>
> Today's Topics:
>
> 1. Re: Hi! (Michael Tremer)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 27 Mar 2013 23:16:19 +0100
> From: Michael Tremer <michael.tremer(a)ipfire.org>
> To: documentation(a)lists.ipfire.org
> Subject: Re: Hi!
> Message-ID: <1364422579.2635.15.camel(a)hughes.tremer.info>
> Content-Type: text/plain; charset="UTF-8"
>
> Hello,
>
> it's great that you want to contribute!
>
> On Tue, 2013-03-26 at 17:34 +0100, info(a)drcomputer.nl wrote:
>> Hi Guys and Girls,
>>
>> I would like to help translate. I'm from the netherlands (holland). And
>> ofcourse I do speak dutch. I'm able to translate from english to dutch.
>> So is there somebody who can help me getting started? I would like to
>> begin with the wiki.
> I am not sure if there is need for a Dutch version of the wiki right
> now, because I think that there are not many Dutch speakers around.
>
> We could use a lot of help improving the English pages if you are up for
> that.
>
>> Maybe in time if someone would help me i can also translate the web
>> interface from IPfire. Although I'm a Linux user and play a lot with
>> VMware, I'm still a user not an expert in these things.
> The web user interface should be available in Dutch since Core Update
> 66. But I think some parts are missing and maybe some strings require a
> second opinion.
>
> -Michael
>
>
>
> ------------------------------
>
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation
>
>
> End of Documentation Digest, Vol 19, Issue 3
> ********************************************
next parent reply other threads:[~2013-03-28 14:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1364468402.22705.documentation@lists.ipfire.org>
2013-03-28 14:19 ` info [this message]
2013-03-28 16:00 ` Michael Tremer
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=51545165.1070409@drcomputer.nl \
--to=info@drcomputer.nl \
--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