[kdewebdev-site] Localisation

[jacob coby]

--- Chris Hornbaker <chrishornbaker at earthlink.net>
wrote:

> Your perception is incorrect, as what Jacob showed
> is exactly what I do, 
> except I make it easier for translators by using the
> tools/formats of the 
> trade.

What I showed was what was generated _after_ whatever
localization tools got done with the original input. 
I had always planned on using the gettext tools to do
the actual translation.

I honestly don't know how much overhead gettext() has.
 If it's comparable to a php include like I outlined
earlier, let's just use that.  If it won't scale
beyond a handful of simultaneous connections, we
obviously need to try something else.

> Also, with Jacob's and D's design, you have one file
> per translation per file, 
> which creates a huge mess of files to deal with and
> possibly you have 
> translators messing with more markup than they
> should. This is the exact 
> reason why I initially liked kde.org's design so
> much.

So your design has only one file for all translations?
 What happens if there are two different translators
for the same language working on two different parts
of the site?  Does having one large translation file
cause a heavy I/O hit per page? 

Whoever wants to throw their comments and code into
the localization stuff, let's schedule a group chat
(IRC, AIM, or Jabber, I don't care) and get this taken
care of.  2 weeks seems like an excessive amount of
time to handle something this simple.

Eric: do you have statistics for the current Quanta
website?  Hits, pages, transfer, things like that? 
It'd really be ideal if you had growth numbers (both
past and predicted) so we know what we're shooting
for. 

=====
--
-Jacob


	
		
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs  
http://hotjobs.sweepstakes.yahoo.com/careermakeover