From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: Not only wiki
Date: Mon, 12 Aug 2013 18:05:07 +0200 [thread overview]
Message-ID: <1376323507.18941.28.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <5207DA02.6070501@drcomputer.nl>
[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]
Hello ?,
technically, the website cannot be translated into other languages in
the same way as the wiki.
We also don't need this functionality, because we have some underlying
problem that is that there were not enough translators in the past, who
could help translating all content that is on there. We also discussed
several times to drop the German translation, because it takes a lot of
time to translate release announcements and what else we post on there.
So, I guess that it is still not worth the effort to translate the
IPFire website. There is other stuff that should be done first.
That means, we can discuss this again in a year or two. But right now,
it don't think that it's worth the effort.
-Michael
On Sun, 2013-08-11 at 20:37 +0200, info(a)drcomputer.nl wrote:
> Hi there,
>
> I'm reading a lot regarding the wiki and it's translations. But I was
> wondering if the website could be translated in the same way. In this
> way, if people refer to IPFire website they can read it. For now
> everything looks so english! For example, if I surf to nl.ipfire.org I
> get the Dutch (NOT German!) language.
>
> Would this be an idea? I'm willing to translate it to dutch.
>
> Kind regards,
>
> drcomputer.nl
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation
prev parent reply other threads:[~2013-08-12 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 18:37 info
2013-08-12 16:05 ` Michael Tremer [this message]
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=1376323507.18941.28.camel@rice-oxley.tremer.info \
--to=michael.tremer@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