htdocs and the newest news.

[Neil Williams]

On Saturday 11 February 2006 7:24 pm, Derek Atkins wrote:
> > How many sites are actually translated? The old method of separate
> > directories led to huge inconsistencies in the different sites and
> > still left large sections untranslated.
>
> Depends on your definition to "translated".  To me, as a user, a
> translated site is one where I click on an icon (usually a flag,
> but sometimes a country name) and see the site in that language.
> As a user I don't particularly care how that happens.

Well, we are one step ahead there because the PHP translation happens without 
any clicks whatsoever. (The user only needs to click if their browser fails 
to declare the correct language variable.)

Once some translations come in, I'll change the current links to simply load 
the correct translation and put a note on the site about how to force the 
browser to pass the correct language using a querystring ?lang=

> As a developer, I want to make the process as simple and
> straightforward as possible, and try not to overload the poor
> webserver.

It seems very light-on-it's-feet so far - most of the translation happens in 
cache and PHP itself is, IMHO, no slower than redirecting Apache to a 
separate sub-domain.

> Keep in mind that www.gnucash.org is a rather old, overutilized
> machine.  So, yes, CPU usage per-page is definitely an issue to think
> about.

The demo machine isn't exactly new - from memory it's at least 10yrs old. It's 
running maybe a dozen other websites, some quite busy and some with some 
seriously large (image based) pages.

> > As for the content, I can't find any reference to translating the content
> > of MediaWiki sites into multiple languages per site, i.e. i18n. Being a
> > wiki, the strings in Language.php can be edited in the wiki itself but
> > only by admins - one per site. Further development of i18n is still only
> > in the planning stage:
> > http://meta.wikimedia.org/wiki/Interface_translations_wiki
>
> It's the content that interests me..  

(and me)

> As we're moving most of the 
> content from www.gnucash.org into the wiki, it would seem to imply
> that we want to have the wiki content internationalized too, right?

If we can . . . but that's nothing to do with the htdocs svn module. The wiki, 
unfortunately, is almost certain to require a completely different method of 
translation.

> > (Why is this all up to me? Does anyone have some ideas about what we want
> > in the Features pages?) I don't think I'm best placed to decide what we
> > put up there.
>
> It's not all up to you.. 

:-) Thanks.

> But I think most people are waiting for you 
> to finalize the website format before they go make changes to the
> content.

I've marked up the features pages for new content, I'll commit a few other 
mark up changes and a tweak to oldnews. Then I'm done.

I'll make an announcement on -user and -devel tonight.

-- 

Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.gnucash.org/pipermail/gnucash-devel/attachments/20060211/17042474/attachment.bin