forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Brondsema <d...@brondsema.net>
Subject Re: i18n suggestion
Date Tue, 16 Mar 2004 00:55:35 GMT
Sjur Nørstebø Moshagen wrote:

> The present i18n stuff in Cocoon is all about translation and 
> localisation of *single items* on a page, to be able to localise table 
> headings, date formats etc of dynamic pages generated from f.ex. an 
> external source (a database, whatever).
>
> The typical scenario that has been in the minds of the i18n team seems 
> to have been:
>
> -get some tabular/business data out of an RDBMS or similar;
> -present it to the user,
> -on the way, localise the presentation of it if wanted (and possible)
>
> Thus, you can localise most things, BUT NOT WHOLE PAGES ON A FILE 
> LEVEL. This is where the i18nFile generator comes in. We need this for 
> being able to serve whole pages, where the different language/locale 
> versions of the page is stored in different files.
>
> The funny thing is, that we're almost there;) If you look at how the 
> present i18n features of Cocoon work, you'll find something like this 
> for the menu generation (this is based on the i18n sample coming with 
> the default installation of Cocoon - I have not yet looked at the Java 
> src code of the i18n block):
>

Can this be used in forrest documents?  For example if a page is heavily 
dependant on graphics and doesn't have much text, it would be easier to 
maintain one source file that had all the text section translations in it. 

Dave Brondsema

Mime
View raw message