Sites with multiple languages

Bret Dawson wrote:
> You could do it all with a single set of templates, if
you like, though.
> $burner->get_oc will tell you what output channel
you're on, and you can
> take things from there. I kind of like having actual
distinct templates,
> but maybe that's just habit.

It was $burner->oc I was looking for. I will take a look
at it when I get
the time.

> If you're using the same layout for both languages, it
might be easier
> to do it the way you describe.

I am using the same layout for both language, so most
templates will be
the same and it will be easier to maintain if templates
aren't duplicated.

I think I will be able to figure out how to do this, now.
Thanks to all
for your help

Regards,
Jesper

On Apr 24, 2007, at 02:50, Scott Lanning wrote:

> As long as the stories in different languages are
considered to be
> separate stories, I think that's reasonable. You might
do other things
> besides begin with "/en" (URI Prefix).

This is integrated into the URI Format in 1.10 and later.
Just type  
whatever you want into the output channel's format.


>   Something that we (Bricolage team) had been working
on for  
> "Bricolage 2.0"
> was the concept of "Input Channels", which
would allow entering  
> content
> into these different channels, kind of like the inverse
of
> output channels, and handled similarly to how sites are
currently
> handled in the UI.
> http
://bricolage.cc/docs/design/ElementRevision/ 
> FunctionalSpec.html#input_channels
> That's never made it into the code, though, as far as I
know
> (didn't Marshall work on that two years ago for Summer
of Code?).

Yep. We never did finish getting Marshall's 2005 "Input
Channels"  
summer of code work integrated, which would solve this
problem.  
Someone want to take that on and finish it? I've always
thought that  
it would be one of the biggest features to set Bricolage
apart from  
other publishing systems.

>> Shouls I instead create an 'en' category and
re-create all my  
>> categories
>> as a sub-category to this?
>
> That doesn't really sound like a good idea to me,
but..

I agree, I think that would be a PITA.

Best,

David

On Apr 24, 2007, at 02:54, Scott Lanning wrote:

> and an even more extreme example (David did this one):
> http://www.rfa.org/

Yes, but RFA has separate content for each service, not the
same  
stories in 10 languages.

Best,

David

On Apr 24, 2007, at 08:59, Bret Dawson wrote:

> We have one template for each language for each story
element type.  
> (So there's an English press_release.mc and a French  
> press_release.mc, for example.) For elements that
handle images,  
> there's only one template (in the English OC), and we
just have the  
> French output channel include the English one's
templates.

This is a very sensible way to do it for two languages.

> You could do it all with a single set of templates, if
you like,  
> though. $burner->get_oc will tell you what output
channel you're  
> on, and you can take things from there. I kind of like
having  
> actual distinct templates, but maybe that's just
habit.

Yes, dispatch is better than if/then everywhere. But you
could  
probably do dispatch with a single if/then in a single set
of  
templates if all of your fields are named consistently.

Best,

David

Hello Jesper


The fun starts if the content of each language is related,
meaning it
would be the same content.

JKA> Shouls I instead create an 'en' category and
re-create all my categories
JKA> as a sub-category to this?

We solved it with categories as '/en', '/de', '/fr' because
it was
mandatory, that each path of subcategories and slug is
written in the
corresponding language.

I dislike to create all content in the same story (WHO
model, please
correct me, if I'm wrong), even if you add first the story
and then
for each language a page with the complete  structure. A
concept I also
used once ... many many clicking.

Probably it will work similar with output channels. I prefer
to use
them rather for the copy platform (media) or territory.


Ideas/Limitations:

The problem is the relation of each of those stories. This
is
important for the translation but also for the quick switch
to the
same content in a different language.

Other CMS has solved this with language instances of the
same object.
So being in the authoring client you see a story and you can
quick
check the same story in another language.

I suggested once to have a button similar to 'Clone Story',
let's call
it 'Create Story Instance' which would, do the same as
clone, but
would add at the same time a reference back to the new copy
and vice
versa. Of course a later new special 'language reference'
would be perfect.

.....................................

Best Regards, Christian -  administratoritassistance.ch  -


====== START ORIGINAL MESSAGE ======

Sites with multiple languages

Hi,

I would like to hear how other users are handling websites
with multiple
languages. The situation is, that I am creating a website,
that needs to
support both danish and english. My own idea was to create
two output
channels, one for danish webpages and one for english
webpages. The
difference being that for the english output channel, the
paths start
with '/en'. The idea is, that the authors must write their
stories and
select  the proper output channel.

My problem is, that I am creating the front page for the
website. I have
created the danish front page, which got the name
/index.html. Now I
can't create the english front page, because the name
/index.html is not
unique. I can't select the other output channel yet, because
the story
isn't created yet.

Shouls I instead create an 'en' category and re-create all
my categories
as a sub-category to this?

Hope you will share your ideas on this.

Regards,
Jesper

======= END ORIGINAL MESSAGE =======

On Sun, 13 May 2007, Christian wrote:
> I dislike to create all content in the same story (WHO
model, please
> correct me, if I'm wrong),

That's how we did it over two years ago.
Since then, there are separate stories for each language
(I'm not claiming this is the best way to do things).