[kdewebdev-site] status

Chris Hornbaker chrishornbaker at earthlink.net
Mon Apr 26 12:00:21 EDT 2004


On Monday 26 April 2004 02:52, David Joham wrote:
> On Sunday 25 April 2004 12:23 pm, Chris Hornbaker wrote:
> > On Thursday 22 April 2004 04:21, David Joham wrote:
> > > Hello everyone!
> > >
> > > It's mid-week so I thought I would drop in and reduce everyone's
> > > productivity by asking if I could get a status update from the
> > > localization teams and the layout teams. I'd love to hear how all y'all
> > > are doing.
> > >
> > > Also, I'd like to know if there's anything I can do to help anyone out.
> >
> > Here's my proposel.
> > http://jilks.no-ip.org/settings/
> > I only tested it on Konq and Moz Firefox.
> > it's not completely translated, but you get the idea.
>
> I'm a little concerned about the requirement for cookies. We should
> probably defult to using the HTTP request headers for the language
> settings.

Cookies are used because the user can change the language. Say I speak German, 
but prefer English on the kdewebdev site. :-D

> Can you write this proposal up for me Chris as outlined in one of my
> previous emails please? I would really like to see how you put this
> together in a brief document so I understand the plumbing involved. I can
> probably dig the email up if you don't have it.

It's simple. Just use xgettext to pull out the strings you want translated, 
which gives you a .pot file. Then use KBabel (or a text editor, or whatever) 
to translate the strings and save it as a .po file. Then run the shell script 
I made that converts the .po file to a PHP include.

For example:
<option><?php i18n("English"); ?></option>

Will give you the following in the .pot file:
msgid "English"
msgstr ""

You change msgstr:
msgstr "glico"

Shell script makes:
$text["English"] = "glico";

To get the translation, you do a typical language check, which loads the 
associated PHP includes.

If you prefer using the <i18n> tag (example: 
<option><i18n>English</i18n></option>), then you end up doing an extra step, 
which just involves running a script that converts <i18n></i18n> to
<?php i18n(""); ?>


> Can you also let me know the status of the site mockups?

It's close to being done, but I don't like the color scheme I chose. :-/

-- 
Christopher Hornbaker           
Jabber ID: Jilks at jabber.org     Email: chrishornbaker at earthlink.net
Join the Free State Project!    http://www.freestateproject.org
   "Liberty in Our Lifetime"
Was I helpful? Let me know! http://svcs.affero.net/rm.php?r=Jilks


More information about the kdewebdev-site mailing list