forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sjur Nørstebø Moshagen <sjur.mosha...@kolumbus.fi>
Subject Re: [I18n] Alternatives locales for a given page.
Date Wed, 28 Apr 2004 10:44:39 GMT
På 28. apr. 2004 kl. 13.25 skrev Upayavira:

> You're missing me. That is what I am proposing to do - at the output 
> side.

<snip/>

> So you would have source of:
>
> /xml/en/foo.xml
> /xml/de/foo.xml
> /xml/pl/foo.xml
>
> Which would map to output of:
>
> /html/foo.html.en
> /html/foo.html.de
> /html/foo.html.pl
> and possibly, if I can work it out:
> /html/foo.html (with the content type stuff that I was just reading 
> about, and you described above.)
>
> Basically, I don't want my content authors to be treading on each 
> other's toes - I want each translator to have their own source folder 
> where they work - but Cocoon and its CLI can then rewrite these to be 
> in Apache's preferred format. That's what I have in mind.

Now I get you, thanks for explaining;)

Does the above imply that you have locale folders at each and every 
level, or only at the starting point?

/xml/en/foo.xml
/xml/bar/en/foo.xml

or

/xml/en/foo.xml
/xml/en/bar/foo.xml

for output:

/html/foo.html.en
/html/bar/foo.html.en

Sjur


Mime
View raw message