[TYPO3-calendar] My experiences with cal and a multilanguage website

[Christian Hernmarck]

Hi

I just want to write down my experiences I had with cal(base) v1.4.3  
and TYPO3 4.5.16/.17 on a website with three languages:
german (default), french (1) and italian (2).

I tried alot until I found that you need to "make a translation of" 
the sysfolder-page with the event data (calendars, categories, events 
etc). Then the entries can be localized (list view, column "Localize 
to:" with flags...).

But then the next problem occured: how can I tell the content plugin 
to display the right events?
On the frontend, the content-plugin on the default-language page is 
ok:
I can choose the calendar and the categories I want to display: -> 
works (after finding out that you have to set the calendar-pid in the 
"record storage page"...)

Then on the "translation page" I copied the content (plugin) and there 
I cannot choose the categories... I only see
***
Category selection
The translation original of this record has no categories assigned.
***
which is not true... (it seems that the same message also appeared 
with the event translation...).

So I had to find my own solution:
Since in my project the events are not needed to be translated - there 
are events in german, some in french and some in italian - I did not 
make use of the "Localize to" feature - I just added 3 categories: GE, 
FR and IT with the idea that I can select the "language category" in 
the plugin. This last thing I had to do manually in the database 
(field: pi_flexform) - there I could type in the category uid of the 
FR or IT category... and with this: it works!

I learned: "localization" can be done in very different ways - and it 
seems that maybe only one is really working completely (but I didn't 
find it) and that many conditions have to be set....
It would maybe make life easier if the admin can choose how deep the 
localization in the project goes...

I hope this text will help some people - or maybe the devs can tell 
what the correct way is without "hacking" the database fields...

Regards
Christian