From: Sven Vermeulen <swift@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] GLEP #10 -- Proposal for restructuring the CVS regarding documentation wrt internationalization proposal
Date: Tue, 5 Aug 2003 15:07:36 +0200 [thread overview]
Message-ID: <20030805130736.GA28681@gentoo.org> (raw)
In-Reply-To: <20030805150356.124cb0d6.svyatogor@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1737 bytes --]
On Tue, Aug 05, 2003 at 03:03:56PM +0300, Svyatogor wrote:
> Not only that. It is much less useful for the end user. However, in this
> case we'll have to develop some policy about these pages. Most users will
> see fr.gentoo.org or ru.gentoo.org as official gentoo homepages and we have
> to be careful on what we put there. The policy should cover various
> aspects, such as design (some team might want to change the layout of the
> page or just change the color scheme), content of the pages, people
> responsible for maintaining it up-to-date and accurate.
I agree that translating and maintaining the whole website is cumbersome to
say the least. What I was thinking about was something in the lines of
http://dev.gentoo.org/~swift/international.html (note: the links don't work,
probably never will :) as main page for http://en.gentoo.org (I take this as
an example because I assume all know English :)
From that main webpage, the visitor can reach the translated documentation or
a list of community websites.
Maintaining this is "easy":
* new translations get added as they are now,
+ a newsitem on the site occurs explaining that there is a new
translation
* new community sites are added to two pages: the one which lists
all community sites, and a link on the left of each page
+ a newsitem on the site occurs explaining that there is a new
community site
That's all there is to it. Ofcourse, newsitems regarding new (translated)
GWN's could be listed there too.
Just an idea, ofcourse.
Wkr,
Sven Vermeulen
PS gerrynjr: can you try changing your mailclient so it wraps its sentences
automatically?
--
Save some animals, eat a vegetarian.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-08-05 13:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 18:31 [gentoo-dev] GLEP #10 -- Proposal for restructuring the CVS regarding documentation wrt internationalization proposal Sven Vermeulen
2003-08-05 10:18 ` Svyatogor
2003-08-05 11:43 ` Sven Vermeulen
2003-08-05 11:50 ` FRLinux
2003-08-05 12:03 ` Svyatogor
2003-08-05 13:07 ` Sven Vermeulen [this message]
2003-08-12 13:05 ` Kurt Lieber
2003-08-12 13:20 ` Paul de Vrieze
2003-08-12 13:41 ` Sven Vermeulen
2003-08-12 15:56 ` Kurt Lieber
2003-08-05 13:31 ` Lisa Marie Seelye
2003-08-05 13:25 ` Svyatogor
2003-08-05 14:15 ` Paul de Vrieze
2003-08-05 15:21 ` Sven Vermeulen
2003-08-05 19:51 ` Paul de Vrieze
2003-08-06 8:06 ` Sven Vermeulen
2003-08-12 12:45 ` Kurt Lieber
2003-08-12 13:36 ` Sven Vermeulen
2003-08-12 13:43 ` Svyatogor
2003-08-12 21:56 ` Robin H. Johnson
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=20030805130736.GA28681@gentoo.org \
--to=swift@gentoo.org \
--cc=gentoo-dev@gentoo.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