Thread: Language Links?
People: What was the problem with having the language links on the front page? I'm afraid that users who don't have a lot of English aren't necessarily going to figure out to click "International Sites". -- Josh Berkus Aglio Database Solutions San Francisco
Josh Berkus wrote: > What was the problem with having the language links on the front > page? I'm afraid that users who don't have a lot of English aren't > necessarily going to figure out to click "International Sites". Whatever you do, please do not use "international" as a synonym for "not English". There are more appropriate phrasings, such as "site in other languages". -- Peter Eisentraut http://developer.postgresql.org/~petere/
On Friday 17 December 2004 12:11, Josh Berkus wrote:
> People:
>
> What was the problem with having the language links on the front page?
> I'm afraid that users who don't have a lot of English aren't necessarily
> going to figure out to click "International Sites".
If we're on the same wavelength, the languague links on the front page were to
see the www site in a different language. Since most of those languages
didn't have translations, we removed them for the final launch. Once they
get translations we will re-enable them.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
> -----Original Message----- > From: pgsql-www-owner@postgresql.org > [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Josh Berkus > Sent: 17 December 2004 17:12 > To: pgsql-www@postgresql.org > Subject: [pgsql-www] Language Links? > > People: > > What was the problem with having the language links on the > front page? I'm > afraid that users who don't have a lot of English aren't > necessarily going to > figure out to click "International Sites". The problem at the moment is that there are a bunch of links to view the site in other languages, yet the only translation we have is Turkish and that is seriously out of date. The first thing we need is for someone to write something to extract all the strings and merge them with the existing .pot file. The second thing is to implement a policy whereby only translations of >90% or so get a link. There also seem to be en, de and es directories under the templates directory (which also contains some en content). I've been working on odds and sods all day and trying to figure this out as I go, but I'm still not sure why it's like that. It seems to me we should have all English files in the template directory, and no en, de or es directories at all. Then, all non-English strings come from an appropriate .mo file. Anyone able to shed some light on this? Regards, Dave.
Hi, Dave Page wrote: > There also seem to be en, de and es directories under the templates > directory (which also contains some en content). I've been working on > odds and sods all day and trying to figure this out as I go, but I'm > still not sure why it's like that. It seems to me we should have all > English files in the template directory, and no en, de or es directories > at all. Then, all non-English strings come from an appropriate .mo file. > > Anyone able to shed some light on this? Well, there is a "readme" file available in portal/ dir in CVS... In short, static templates are to be translated as a whole and placed in appropriate dirs, since pages in different languages may have different layouts and since it makes little sense to have a large amount of HTML in gettext files.
> -----Original Message----- > From: Alexey Borzov [mailto:borz_off@cs.msu.su] > Sent: 17 December 2004 22:04 > To: Dave Page > Cc: Josh Berkus; pgsql-www@postgresql.org > Subject: Re: [pgsql-www] Language Links? > > Well, there is a "readme" file available in portal/ dir in CVS... > > In short, static templates are to be translated as a whole > and placed in > appropriate dirs, since pages in different languages may have > different layouts > and since it makes little sense to have a large amount of > HTML in gettext files. Ahh, yes. Despite reading the readme a couple of times I managed to miss the key para on func_lang. Thanks. Regards, Dave.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
On Fri, 17 Dec 2004, Dave Page wrote:
> The problem at the moment is that there are a bunch of links to view the
> site in other languages, yet the only translation we have is Turkish and
> that is seriously out of date. The first thing we need is for someone to
> write something to extract all the strings and merge them with the
> existing .pot file. The second thing is to implement a policy whereby
> only translations of >90% or so get a link.
I've fully translated portal.pot into Turkish, as a copy of current CVS
but today gborg CVS did not like my password, so I could not commit it.
Anyway, maybe I can extract all the strings on Sunday.
- --
Devrim GUNDUZ
devrim~gunduz.org devrim.gunduz~linux.org.tr
http://www.tdmsoft.com
http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFBw5bKtl86P3SPfQ4RAijgAKDTpWEfd9362YVIRtQpFFyI/Fx27QCfTpvl
v1NtXh2Td74dw8noHuFDeTM=
=GaxC
-----END PGP SIGNATURE-----
> -----Original Message----- > From: Devrim GUNDUZ [mailto:devrim@gunduz.org] > Sent: 18 December 2004 02:33 > To: Dave Page > Cc: PostgreSQL WWW Mailing List > Subject: Re: [pgsql-www] Language Links? > > > I've fully translated portal.pot into Turkish, as a copy of > current CVS OK - you realise that's only part of the task? You also need to copy and translate the template/en/ hierarchy to template/tr > but today gborg CVS did not like my password, so I could not > commit it. Oh. Not sure about that (you are setup as a developer on the project) - you'll need to speak to Chris Ryan if you have continuing problems. > Anyway, maybe I can extract all the strings on Sunday. Do you have a script for this now? Istr Alexey saying you were looking at that - is so, can you commit it to the tools directory when you get access (or send it to me and I'll do it). Thanks, Dave.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
On Sat, 18 Dec 2004, Dave Page wrote:
>> I've fully translated portal.pot into Turkish, as a copy of
>> current CVS
>
> OK - you realise that's only part of the task? You also need to copy and
> translate the template/en/ hierarchy to template/tr
Himm, ok.
>> but today gborg CVS did not like my password, so I could not
>> commit it.
>
> Oh. Not sure about that (you are setup as a developer on the project) -
> you'll need to speak to Chris Ryan if you have continuing problems.
Ok, problem solved...
>> Anyway, maybe I can extract all the strings on Sunday.
>
> Do you have a script for this now? Istr Alexey saying you were looking
> at that - is so, can you commit it to the tools directory when you get
> access (or send it to me and I'll do it).
I don't have a script yet, but I'll do it ASAP...
Regards,
- --
Devrim GUNDUZ
devrim~gunduz.org devrim.gunduz~linux.org.tr
http://www.tdmsoft.com
http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFBxvCptl86P3SPfQ4RAu7+AJ9LFzH7YJyLAJJ1mQ/1rLMBvxfmZACeKhhL
FCGpGH+JXMZV1sgV/sDrvuo=
=qX7k
-----END PGP SIGNATURE-----