TYPO3 Mailingliste: nicht fragen - lesen!

Hi,

When I translate a page and uses the L=2 to view the translation it is
only my menu that is translated. Content is still default language.

How can that be?

Regards,
Jeppe D
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

Hi Jeppe

Are you working with TemplaVoila?

Andi

2007/6/7, Jeppe Donslund <jd (AT) webmasters (DOT) dk>:
>
> Hi,
>
> When I translate a page and uses the L=2 to view the translation it is
> only my menu that is translated. Content is still default language.
>
> How can that be?
>
> Regards,
> Jeppe D
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english (AT) lists (DOT) netfielders.de
> http://lists.netfielders.de/cgi-bin/.../typo3-english
>
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

Yes I Am.
I have tried to follow the localization Tutorial, but it seems a little
out of date.

Jeppe


Andreas Becker skrev:
> Hi Jeppe
>
> Are you working with TemplaVoila?
>
> Andi
>
> 2007/6/7, Jeppe Donslund <jd (AT) webmasters (DOT) dk>:
>>
>> Hi,
>>
>> When I translate a page and uses the L=2 to view the translation it is
>> only my menu that is translated. Content is still default language.
>>
>> How can that be?
>>
>> Regards,
>> Jeppe D
>> _______________________________________________
>> TYPO3-english mailing list
>> TYPO3-english (AT) lists (DOT) netfielders.de
>> http://lists.netfielders.de/cgi-bin/.../typo3-english
>>
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

Ok Jeppe

Then go to Page

Click on Localisation and have a look there is standing Separate Structure
1:1

If yes you are working in an environment where each localised page will be
created with aseparate structure.

Click on view page translation and check if you can see the contentelement
in the backend? if not check under UNUSED Elements

get back here

Andi

2007/6/7, Jeppe Donslund <jd (AT) webmasters (DOT) dk>:
>
> Yes I Am.
> I have tried to follow the localization Tutorial, but it seems a little
> out of date.
>
> Jeppe
>
>
> Andreas Becker skrev:
> > Hi Jeppe
> >
> > Are you working with TemplaVoila?
> >
> > Andi
> >
> > 2007/6/7, Jeppe Donslund <jd (AT) webmasters (DOT) dk>:
> >>
> >> Hi,
> >>
> >> When I translate a page and uses the L=2 to view the translation it is
> >> only my menu that is translated. Content is still default language.
> >>
> >> How can that be?
> >>
> >> Regards,
> >> Jeppe D
> >> _______________________________________________
> >> TYPO3-english mailing list
> >> TYPO3-english (AT) lists (DOT) netfielders.de
> >> http://lists.netfielders.de/cgi-bin/.../typo3-english
> >>
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english (AT) lists (DOT) netfielders.de
> http://lists.netfielders.de/cgi-bin/.../typo3-english
>
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

I can't find Localization anywhere. The only one active in the top is
Advanced functions.

I guess I have forgotten to turn on something.

Jeppe



Andreas Becker skrev:
> Ok Jeppe
>
> Then go to Page
>
> Click on Localisation and have a look there is standing Separate Structure
> 1:1
>
> If yes you are working in an environment where each localised page will be
> created with aseparate structure.
>
> Click on view page translation and check if you can see the contentelement
> in the backend? if not check under UNUSED Elements
>
> get back here
>
> Andi
>
> 2007/6/7, Jeppe Donslund <jd (AT) webmasters (DOT) dk>:
>>
>> Yes I Am.
>> I have tried to follow the localization Tutorial, but it seems a little
>> out of date.
>>
>> Jeppe
>>
>>
>> Andreas Becker skrev:
>> > Hi Jeppe
>> >
>> > Are you working with TemplaVoila?
>> >
>> > Andi
>> >
>> > 2007/6/7, Jeppe Donslund <jd (AT) webmasters (DOT) dk>:
>> >>
>> >> Hi,
>> >>
>> >> When I translate a page and uses the L=2 to view the translation it is
>> >> only my menu that is translated. Content is still default language.
>> >>
>> >> How can that be?
>> >>
>> >> Regards,
>> >> Jeppe D
>> >> _______________________________________________
>> >> TYPO3-english mailing list
>> >> TYPO3-english (AT) lists (DOT) netfielders.de
>> >> http://lists.netfielders.de/cgi-bin/.../typo3-english
>> >>
>> _______________________________________________
>> TYPO3-english mailing list
>> TYPO3-english (AT) lists (DOT) netfielders.de
>> http://lists.netfielders.de/cgi-bin/.../typo3-english
>>
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

Ok Jeppe a bit further:

If you want to setup the pages with the same structure like your original
page the you have to insert some lines in the DS of each Template.

Go to TemplaVoila
StorageFolder
Choose your Datastructure where the Template is in you are using (TIP - make
a copy and then you can switch afterwards between separate and same
structure easily)

Open the DS Record
Check the Datastructure XML:
here you have to insert
<meta type="array">
<langChildren type="integer">1</langChildren>
<langDisable type="integer">1</langDisable>
</meta>

Should look like this afterwards:

<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
> <T3DataStructure>
> <meta type="array">
> <langChildren type="integer">1</langChildren>
> <langDisable type="integer">1</langDisable>
> </meta>
> <ROOT type="array">
> <tx_templavoila type="array">
> <title>ROOT</title>
> <description>Select the HTML element on the page which you
> want to be the overall container element for the template.</description>
> </tx_templavoila>
> ...
> ...
>

Now you will be able to use ONLY the same structure

If you have made a copy of the DS before we changed it rename it something
like DS-seperate.

Now you copy also all TOs assigned to this DS
Open every TO record and assign the DS-separate Structure to it.

Now you can choose between working with an separate structure or with same
structure easily and you can switch inbetween.

--------------------

LAST an IMPORTANT step

Check if you have created the Languages in te Globe
Then check your setup if you have inserted the Language record here.

i.e.
#LanguageMenu
lib.languageMenu < plugin.tx_srlanguagemenu_pi1
lib.languageMenu.languagesUidsList = 1,2,3,4,5,6,7,8,9,10
lib.languageMenu.defaultLayout= 0
subparts.languageMenu < lib.languageMenu

# Localization:
config {
linkVars = L
sys_language_mode = content_fallback
sys_language_overlay = 1
}

[globalVar = GP:L=1]
config {
sys_language_uid = 1
language = en
locale_all = en_EN
metaCharset = utf-8
}

[globalVar = GP:L=2]
config {
sys_language_uid = 2
language = de
}

[globalVar = GP:L=3]
config {
sys_language_uid = 3
language = th
}

[globalVar = GP:L=4]
config {
sys_language_uid = 4
language = cn
}

[globalVar = GP:L=5]
config {
sys_language_uid = 5
language = ar
}

[globalVar = GP:L=6]
config {
sys_language_uid = 6
language = il
}

[globalVar = GP:L=7]
config {
sys_language_uid = 7
language = gr
}

[globalVar = GP:L=8]
config {
sys_language_uid = 8
language = ru
}

[globalVar = GP:L=9]
config {
sys_language_uid = 9
language = hi
}

[globalVar = GP:L=10]
config {
sys_language_uid = 10
language = jp
}

[global]

And then it should work - if you have also a language changer on the page
- Check it

Andi






2007/6/7, Andreas Becker <ab.becker (AT) web (DOT) de>:
>
> Ok Jeppe
>
> Then go to Page
>
> Click on Localisation and have a look there is standing Separate Structure
> 1:1
>
> If yes you are working in an environment where each localised page will be
> created with aseparate structure.
>
> Click on view page translation and check if you can see the contentelement
> in the backend? if not check under UNUSED Elements
>
> get back here
>
> Andi
>
> 2007/6/7, Jeppe Donslund < jd (AT) webmasters (DOT) dk>:
> >
> > Yes I Am.
> > I have tried to follow the localization Tutorial, but it seems a little
> > out of date.
> >
> > Jeppe
> >
> >
> > Andreas Becker skrev:
> > > Hi Jeppe
> > >
> > > Are you working with TemplaVoila?
> > >
> > > Andi
> > >
> > > 2007/6/7, Jeppe Donslund < jd (AT) webmasters (DOT) dk>:
> > >>
> > >> Hi,
> > >>
> > >> When I translate a page and uses the L=2 to view the translation it
> > is
> > >> only my menu that is translated. Content is still default language.
> > >>
> > >> How can that be?
> > >>
> > >> Regards,
> > >> Jeppe D
> > >> _______________________________________________
> > >> TYPO3-english mailing list
> > >> TYPO3-english (AT) lists (DOT) netfielders.de
> > >> http://lists.netfielders.de/cgi-bin/.../typo3-english
> > >>
> > _______________________________________________
> > TYPO3-english mailing list
> > TYPO3-english (AT) lists (DOT) netfielders.de
> > http://lists.netfielders.de/cgi-bin/.../typo3-english
> >
>
>
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

Hi Jeppe
If you are using RealURL - you also have to define all localisation records
in localconf.php

If you are using CoolUri it is much simpler as you only have to edit some
code in the .xml file of Cool Uri.

Examples of how to setup the right code for the languages in RealURL and
CoolUri you can find here:
Tutorial - cooluri:
http://docs.google.com/View?docid=dd33gg45_3f8j96p

---
CoolUri Tutorial

It is described in the EXAMPLE section.

I hope this helps

Andi



2007/6/7, Andreas Becker <ab.becker (AT) web (DOT) de >:
>
> Ok Jeppe a bit further:
>
> If you want to setup the pages with the same structure like your original
> page the you have to insert some lines in the DS of each Template.
>
> Go to TemplaVoila
> StorageFolder
> Choose your Datastructure where the Template is in you are using (TIP -
> make a copy and then you can switch afterwards between separate and same
> structure easily)
>
> Open the DS Record
> Check the Datastructure XML:
> here you have to insert
> <meta type="array">
> <langChildren type="integer">1</langChildren>
> <langDisable type="integer">1</langDisable>
> </meta>
>
> Should look like this afterwards:
>
> <?xml version="1.0" encoding="utf-8" standalone="yes" ?>
> > <T3DataStructure>
> > <meta type="array">
> > <langChildren type="integer">1</langChildren>
> > <langDisable type="integer">1</langDisable>
> > </meta>
> > <ROOT type="array">
> > <tx_templavoila type="array">
> > <title>ROOT</title>
> > <description>Select the HTML element on the page which you
> > want to be the overall container element for the template.</description>
> > </tx_templavoila>
> > ...
> > ...
> >
>
> Now you will be able to use ONLY the same structure
>
> If you have made a copy of the DS before we changed it rename it something
> like DS-seperate.
>
> Now you copy also all TOs assigned to this DS
> Open every TO record and assign the DS-separate Structure to it.
>
> Now you can choose between working with an separate structure or with same
> structure easily and you can switch inbetween.
>
> --------------------
>
> LAST an IMPORTANT step
>
> Check if you have created the Languages in te Globe
> Then check your setup if you have inserted the Language record here.
>
> i.e.
> #LanguageMenu
> lib.languageMenu < plugin.tx_srlanguagemenu_pi1
> lib.languageMenu.languagesUidsList = 1,2,3,4,5,6,7,8,9,10
> lib.languageMenu.defaultLayout= 0
> subparts.languageMenu < lib.languageMenu
>
> # Localization:
> config {
> linkVars = L
> sys_language_mode = content_fallback
> sys_language_overlay = 1
> }
>
> [globalVar = GP:L=1]
> config {
> sys_language_uid = 1
> language = en
> locale_all = en_EN
> metaCharset = utf-8
> }
>
> [globalVar = GP:L=2]
> config {
> sys_language_uid = 2
> language = de
> }
>
> [globalVar = GP:L=3]
> config {
> sys_language_uid = 3
> language = th
> }
>
> [globalVar = GP:L=4]
> config {
> sys_language_uid = 4
> language = cn
> }
>
> [globalVar = GP:L=5]
> config {
> sys_language_uid = 5
> language = ar
> }
>
> [globalVar = GP:L=6]
> config {
> sys_language_uid = 6
> language = il
> }
>
> [globalVar = GP:L=7]
> config {
> sys_language_uid = 7
> language = gr
> }
>
> [globalVar = GP:L=8]
> config {
> sys_language_uid = 8
> language = ru
> }
>
> [globalVar = GP:L=9]
> config {
> sys_language_uid = 9
> language = hi
> }
>
> [globalVar = GP:L=10]
> config {
> sys_language_uid = 10
> language = jp
> }
>
> [global]
>
> And then it should work - if you have also a language changer on the page
> - Check it
>
> Andi
>
>
>
>
>
>
> 2007/6/7, Andreas Becker <ab.becker (AT) web (DOT) de >:
> >
> > Ok Jeppe
> >
> > Then go to Page
> >
> > Click on Localisation and have a look there is standing Separate
> > Structure 1:1
> >
> > If yes you are working in an environment where each localised page will
> > be created with aseparate structure.
> >
> > Click on view page translation and check if you can see the
> > contentelement in the backend? if not check under UNUSED Elements
> >
> > get back here
> >
> > Andi
> >
> > 2007/6/7, Jeppe Donslund < jd (AT) webmasters (DOT) dk>:
> > >
> > > Yes I Am.
> > > I have tried to follow the localization Tutorial, but it seems a
> > > little
> > > out of date.
> > >
> > > Jeppe
> > >
> > >
> > > Andreas Becker skrev:
> > > > Hi Jeppe
> > > >
> > > > Are you working with TemplaVoila?
> > > >
> > > > Andi
> > > >
> > > > 2007/6/7, Jeppe Donslund < jd (AT) webmasters (DOT) dk>:
> > > >>
> > > >> Hi,
> > > >>
> > > >> When I translate a page and uses the L=2 to view the translation it
> > > is
> > > >> only my menu that is translated. Content is still default language.
> > >
> > > >>
> > > >> How can that be?
> > > >>
> > > >> Regards,
> > > >> Jeppe D
> > > >> _______________________________________________
> > > >> TYPO3-english mailing list
> > > >> TYPO3-english (AT) lists (DOT) netfielders.de
> > > >> http://lists.netfielders.de/cgi-bin/.../typo3-english
> > > >>
> > > _______________________________________________
> > > TYPO3-english mailing list
> > > TYPO3-english (AT) lists (DOT) netfielders.de
> > > http://lists.netfielders.de/cgi-bin/.../typo3-english
> > >
> >
> >
>
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

I have put the 4 lines into the DS XML.

This is what I use in my Setup:

# Localization:
config {
linkVars = L
}
[globalVar = GP:L=1]
config {
sys_language_uid = 1
language = gb
locale_all = en_EN
metaCharset = iso-8859-1
}
[globalVar = GP:L=2]
config {
sys_language_uid = 2
language = de
locale_all = de_DE
}
[global]


## Localization menu:
lib.langMenu = HMENU
lib.langMenu {
special = language
special.value = 0,1,2
special.normalWhenNoLanguage = 0
1 = GMENU
1.NO {
XY = [5.w]+2, [5.h]+2
backColor = #646464
5 = IMAGE
5.file = EXT:cms/tslib/media/flags/hl_dk.gif ||
EXT:cms/tslib/media/flags/hl_uk.gif || EXT:cms/tslib/media/flags/hl_de.gif
5.offset = 1,1
}

1.ACT < lib.langMenu.1.NO
1.ACT=1
1.ACT.backColor = #CECECE

1.USERDEF1 < lib.langMenu.1.NO
1.USERDEF1=1
1.USERDEF1.5.file = EXT:cms/tslib/media/flags/hl_dk.gif ||
EXT:cms/tslib/media/flags/hl_uk.gif || EXT:cms/tslib/media/flags/hl_de.gif
1.USERDEF1.noLink = 0

1.USERDEF2 < lib.langMenu.1.USERDEF1
1.USERDEF2.backColor = white
}

Shouldn't that be okay?

/Jeppe



Andreas Becker skrev:
> Ok Jeppe a bit further:
>
> If you want to setup the pages with the same structure like your original
> page the you have to insert some lines in the DS of each Template.
>
> Go to TemplaVoila
> StorageFolder
> Choose your Datastructure where the Template is in you are using (TIP -
> make
> a copy and then you can switch afterwards between separate and same
> structure easily)
>
> Open the DS Record
> Check the Datastructure XML:
> here you have to insert
> <meta type="array">
> <langChildren type="integer">1</langChildren>
> <langDisable type="integer">1</langDisable>
> </meta>
>
> Should look like this afterwards:
>
> <?xml version="1.0" encoding="utf-8" standalone="yes" ?>
>> <T3DataStructure>
>> <meta type="array">
>> <langChildren type="integer">1</langChildren>
>> <langDisable type="integer">1</langDisable>
>> </meta>
>> <ROOT type="array">
>> <tx_templavoila type="array">
>> <title>ROOT</title>
>> <description>Select the HTML element on the page which you
>> want to be the overall container element for the template.</description>
>> </tx_templavoila>
>> ...
>> ...
>>
>
> Now you will be able to use ONLY the same structure
>
> If you have made a copy of the DS before we changed it rename it something
> like DS-seperate.
>
> Now you copy also all TOs assigned to this DS
> Open every TO record and assign the DS-separate Structure to it.
>
> Now you can choose between working with an separate structure or with same
> structure easily and you can switch inbetween.
>
> --------------------
>
> LAST an IMPORTANT step
>
> Check if you have created the Languages in te Globe
> Then check your setup if you have inserted the Language record here.
>
> i.e.
> #LanguageMenu
> lib.languageMenu < plugin.tx_srlanguagemenu_pi1
> lib.languageMenu.languagesUidsList = 1,2,3,4,5,6,7,8,9,10
> lib.languageMenu.defaultLayout= 0
> subparts.languageMenu < lib.languageMenu
>
> # Localization:
> config {
> linkVars = L
> sys_language_mode = content_fallback
> sys_language_overlay = 1
> }
>
> [globalVar = GP:L=1]
> config {
> sys_language_uid = 1
> language = en
> locale_all = en_EN
> metaCharset = utf-8
> }
>
> [globalVar = GP:L=2]
> config {
> sys_language_uid = 2
> language = de
> }
>
> [globalVar = GP:L=3]
> config {
> sys_language_uid = 3
> language = th
> }
>
> [globalVar = GP:L=4]
> config {
> sys_language_uid = 4
> language = cn
> }
>
> [globalVar = GP:L=5]
> config {
> sys_language_uid = 5
> language = ar
> }
>
> [globalVar = GP:L=6]
> config {
> sys_language_uid = 6
> language = il
> }
>
> [globalVar = GP:L=7]
> config {
> sys_language_uid = 7
> language = gr
> }
>
> [globalVar = GP:L=8]
> config {
> sys_language_uid = 8
> language = ru
> }
>
> [globalVar = GP:L=9]
> config {
> sys_language_uid = 9
> language = hi
> }
>
> [globalVar = GP:L=10]
> config {
> sys_language_uid = 10
> language = jp
> }
>
> [global]
>
> And then it should work - if you have also a language changer on the page
> - Check it
>
> Andi
>
>
>
>
>
>
> 2007/6/7, Andreas Becker <ab.becker (AT) web (DOT) de>:
>>
>> Ok Jeppe
>>
>> Then go to Page
>>
>> Click on Localisation and have a look there is standing Separate
>> Structure
>> 1:1
>>
>> If yes you are working in an environment where each localised page
>> will be
>> created with aseparate structure.
>>
>> Click on view page translation and check if you can see the
>> contentelement
>> in the backend? if not check under UNUSED Elements
>>
>> get back here
>>
>> Andi
>>
>> 2007/6/7, Jeppe Donslund < jd (AT) webmasters (DOT) dk>:
>> >
>> > Yes I Am.
>> > I have tried to follow the localization Tutorial, but it seems a little
>> > out of date.
>> >
>> > Jeppe
>> >
>> >
>> > Andreas Becker skrev:
>> > > Hi Jeppe
>> > >
>> > > Are you working with TemplaVoila?
>> > >
>> > > Andi
>> > >
>> > > 2007/6/7, Jeppe Donslund < jd (AT) webmasters (DOT) dk>:
>> > >>
>> > >> Hi,
>> > >>
>> > >> When I translate a page and uses the L=2 to view the translation it
>> > is
>> > >> only my menu that is translated. Content is still default language.
>> > >>
>> > >> How can that be?
>> > >>
>> > >> Regards,
>> > >> Jeppe D
>> > >> _______________________________________________
>> > >> TYPO3-english mailing list
>> > >> TYPO3-english (AT) lists (DOT) netfielders.de
>> > >> http://lists.netfielders.de/cgi-bin/.../typo3-english
>> > >>
>> > _______________________________________________
>> > TYPO3-english mailing list
>> > TYPO3-english (AT) lists (DOT) netfielders.de
>> > http://lists.netfielders.de/cgi-bin/.../typo3-english
>> >
>>
>>
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

Hi Jeppe

The localisation looks fine for me

With the other stuff I don't know sorry - to complicated

I am using the sr_languagemenu
and the settings are easy

#LanguageMenu
lib.languageMenu < plugin.tx_srlanguagemenu_pi1
lib.languageMenu.languagesUidsList = 1,2,3
lib.languageMenu.defaultLayout= 0
subparts.languageMenu < lib.languageMenu

Thats it and it is working in TemplaVoila

You can see it here:

http://www.t3pack.org/support/multilingual/

You can choose between showing flags and showing a dropdown menu

Greetings

Andi

2007/6/7, Jeppe Donslund <jd (AT) webmasters (DOT) dk>:
>
> I have put the 4 lines into the DS XML.
>
> This is what I use in my Setup:
>
> # Localization:
> config {
> linkVars = L
> }
> [globalVar = GP:L=1]
> config {
> sys_language_uid = 1
> language = gb
> locale_all = en_EN
> metaCharset = iso-8859-1
> }
> [globalVar = GP:L=2]
> config {
> sys_language_uid = 2
> language = de
> locale_all = de_DE
> }
> [global]
>
>
> ## Localization menu:
> lib.langMenu = HMENU
> lib.langMenu {
> special = language
> special.value = 0,1,2
> special.normalWhenNoLanguage = 0
> 1 = GMENU
> 1.NO {
> XY = [5.w]+2, [5.h]+2
> backColor = #646464
> 5 = IMAGE
> 5.file = EXT:cms/tslib/media/flags/hl_dk.gif ||
> EXT:cms/tslib/media/flags/hl_uk.gif ||
> EXT:cms/tslib/media/flags/hl_de.gif
> 5.offset = 1,1
> }
>
> 1.ACT < lib.langMenu.1.NO
> 1.ACT=1
> 1.ACT.backColor = #CECECE
>
> 1.USERDEF1 < lib.langMenu.1.NO
> 1.USERDEF1=1
> 1.USERDEF1.5.file = EXT:cms/tslib/media/flags/hl_dk.gif ||
> EXT:cms/tslib/media/flags/hl_uk.gif ||
> EXT:cms/tslib/media/flags/hl_de.gif
> 1.USERDEF1.noLink = 0
>
> 1.USERDEF2 < lib.langMenu.1.USERDEF1
> 1.USERDEF2.backColor = white
> }
>
> Shouldn't that be okay?
>
> /Jeppe
>
>
>
> Andreas Becker skrev:
> > Ok Jeppe a bit further:
> >
> > If you want to setup the pages with the same structure like your
> original
> > page the you have to insert some lines in the DS of each Template.
> >
> > Go to TemplaVoila
> > StorageFolder
> > Choose your Datastructure where the Template is in you are using (TIP -
> > make
> > a copy and then you can switch afterwards between separate and same
> > structure easily)
> >
> > Open the DS Record
> > Check the Datastructure XML:
> > here you have to insert
> > <meta type="array">
> > <langChildren type="integer">1</langChildren>
> > <langDisable type="integer">1</langDisable>
> > </meta>
> >
> > Should look like this afterwards:
> >
> > <?xml version="1.0" encoding="utf-8" standalone="yes" ?>
> >> <T3DataStructure>
> >> <meta type="array">
> >> <langChildren type="integer">1</langChildren>
> >> <langDisable type="integer">1</langDisable>
> >> </meta>
> >> <ROOT type="array">
> >> <tx_templavoila type="array">
> >> <title>ROOT</title>
> >> <description>Select the HTML element on the page which you
> >> want to be the overall container element for the
> template.</description>
> >> </tx_templavoila>
> >> ...
> >> ...
> >>
> >
> > Now you will be able to use ONLY the same structure
> >
> > If you have made a copy of the DS before we changed it rename it
> something
> > like DS-seperate.
> >
> > Now you copy also all TOs assigned to this DS
> > Open every TO record and assign the DS-separate Structure to it.
> >
> > Now you can choose between working with an separate structure or with
> same
> > structure easily and you can switch inbetween.
> >
> > --------------------
> >
> > LAST an IMPORTANT step
> >
> > Check if you have created the Languages in te Globe
> > Then check your setup if you have inserted the Language record here.
> >
> > i.e.
> > #LanguageMenu
> > lib.languageMenu < plugin.tx_srlanguagemenu_pi1
> > lib.languageMenu.languagesUidsList = 1,2,3,4,5,6,7,8,9,10
> > lib.languageMenu.defaultLayout= 0
> > subparts.languageMenu < lib.languageMenu
> >
> > # Localization:
> > config {
> > linkVars = L
> > sys_language_mode = content_fallback
> > sys_language_overlay = 1
> > }
> >
> > [globalVar = GP:L=1]
> > config {
> > sys_language_uid = 1
> > language = en
> > locale_all = en_EN
> > metaCharset = utf-8
> > }
> >
> > [globalVar = GP:L=2]
> > config {
> > sys_language_uid = 2
> > language = de
> > }
> >
> > [globalVar = GP:L=3]
> > config {
> > sys_language_uid = 3
> > language = th
> > }
> >
> > [globalVar = GP:L=4]
> > config {
> > sys_language_uid = 4
> > language = cn
> > }
> >
> > [globalVar = GP:L=5]
> > config {
> > sys_language_uid = 5
> > language = ar
> > }
> >
> > [globalVar = GP:L=6]
> > config {
> > sys_language_uid = 6
> > language = il
> > }
> >
> > [globalVar = GP:L=7]
> > config {
> > sys_language_uid = 7
> > language = gr
> > }
> >
> > [globalVar = GP:L=8]
> > config {
> > sys_language_uid = 8
> > language = ru
> > }
> >
> > [globalVar = GP:L=9]
> > config {
> > sys_language_uid = 9
> > language = hi
> > }
> >
> > [globalVar = GP:L=10]
> > config {
> > sys_language_uid = 10
> > language = jp
> > }
> >
> > [global]
> >
> > And then it should work - if you have also a language changer on the
> page
> > - Check it
> >
> > Andi
> >
> >
> >
> >
> >
> >
> > 2007/6/7, Andreas Becker <ab.becker (AT) web (DOT) de>:
> >>
> >> Ok Jeppe
> >>
> >> Then go to Page
> >>
> >> Click on Localisation and have a look there is standing Separate
> >> Structure
> >> 1:1
> >>
> >> If yes you are working in an environment where each localised page
> >> will be
> >> created with aseparate structure.
> >>
> >> Click on view page translation and check if you can see the
> >> contentelement
> >> in the backend? if not check under UNUSED Elements
> >>
> >> get back here
> >>
> >> Andi
> >>
> >> 2007/6/7, Jeppe Donslund < jd (AT) webmasters (DOT) dk>:
> >> >
> >> > Yes I Am.
> >> > I have tried to follow the localization Tutorial, but it seems a
> little
> >> > out of date.
> >> >
> >> > Jeppe
> >> >
> >> >
> >> > Andreas Becker skrev:
> >> > > Hi Jeppe
> >> > >
> >> > > Are you working with TemplaVoila?
> >> > >
> >> > > Andi
> >> > >
> >> > > 2007/6/7, Jeppe Donslund < jd (AT) webmasters (DOT) dk>:
> >> > >>
> >> > >> Hi,
> >> > >>
> >> > >> When I translate a page and uses the L=2 to view the translation
> it
> >> > is
> >> > >> only my menu that is translated. Content is still default
> language.
> >> > >>
> >> > >> How can that be?
> >> > >>
> >> > >> Regards,
> >> > >> Jeppe D
> >> > >> _______________________________________________
> >> > >> TYPO3-english mailing list
> >> > >> TYPO3-english (AT) lists (DOT) netfielders.de
> >> > >> http://lists.netfielders.de/cgi-bin/.../typo3-english
> >> > >>
> >> > _______________________________________________
> >> > TYPO3-english mailing list
> >> > TYPO3-english (AT) lists (DOT) netfielders.de
> >> > http://lists.netfielders.de/cgi-bin/.../typo3-english
> >> >
> >>
> >>
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english (AT) lists (DOT) netfielders.de
> http://lists.netfielders.de/cgi-bin/.../typo3-english
>
_______________________________________________
TYPO3-english mailing list
TYPO3-english (AT) lists (DOT) netfielders.de
http://lists.netfielders.de/cgi-bin/.../typo3-english

Hi Andi

Thanks for your time.
I do not think it is the language menu that i causing the problem.
I will see if I can solve the problem.

Maybe the extension is worth trying anyway.

Regards,
Jeppe

Andreas Becker skrev:
> Hi Jeppe
>
> The localisation looks fine for me
>
> With the other stuff I don't know sorry - to complicated
>
> I am using the sr_languagemenu
> and the settings are easy
>
> #LanguageMenu
> lib.languageMenu < plugin.tx_srlanguagemenu_pi1
> lib.languageMenu.languagesUidsList = 1,2,3
> lib.languageMenu.defaultLayout= 0
> subparts.languageMenu < lib.languageMenu
>
> Thats it and it is working in TemplaVoila
>
> You can see it here:
>
> http://www.t3pack.org/support/multilingual/
>
> You can choose between showing flags and showing a dropdown menu
>
> Greetings
>
> Andi
>
> 2007/6/7, Jeppe Donslund <jd (AT) webmasters (DOT) dk>:
>>
>> I have put the 4 lines into the DS XML.
>>
>> This is what I use in my Setup:
>>
>> # Localization:
>> config {
>> linkVars = L
>> }
>> [globalVar = GP:L=1]
>> config {
>> sys_language_uid = 1
>> language = gb
>> locale_all = en_EN
>> metaCharset = iso-8859-1
>> }
>> [globalVar = GP:L=2]
>> config {
>> sys_language_uid = 2
>> language = de
>> locale_all = de_DE
>> }
>> [global]
>>
>>
>> ## Localization menu:
>> lib.langMenu = HMENU
>> lib.langMenu {
>> special = language
>> special.value = 0,1,2
>> special.normalWhenNoLanguage = 0
>> 1 = GMENU
>> 1.NO {
>> XY = [5.w]+2, [5.h]+2
>> backColor = #646464
>> 5 = IMAGE
>> 5.file = EXT:cms/tslib/media/flags/hl_dk.gif ||
>> EXT:cms/tslib/media/flags/hl_uk.gif ||
>> EXT:cms/tslib/media/flags/hl_de.gif
>> 5.offset = 1,1
>> }
>>
>> 1.ACT < lib.langMenu.1.NO
>> 1.ACT=1
>> 1.ACT.backColor = #CECECE
>>
>> 1.USERDEF1 < lib.langMenu.1.NO
>> 1.USERDEF1=1
>> 1.USERDEF1.5.file = EXT:cms/tslib/media/flags/hl_dk.gif ||
>> EXT:cms/tslib/media/flags/hl_uk.gif ||
>> EXT:cms/tslib/media/flags/hl_de.gif
>> 1.USERDEF1.noLink = 0
>>
>> 1.USERDEF2 < lib.langMenu.1.USERDEF1
>> 1.USERDEF2.backColor = white
>> }
>>
>> Shouldn't that be okay?
>>
>> /Jeppe
>>
>>
>>
>> Andreas Becker skrev:
>> > Ok Jeppe a bit further:
>> >
>> > If you want to setup the pages with the same structure like your
>> original
>> > page the you have to insert some lines in the DS of each Template.
>> >
>> > Go to TemplaVoila
>> > StorageFolder
>> > Choose your Datastructure where the Template is in you are using (TIP -
>> > make
>> > a copy and then you can switch afterwards between separate and same
>> > structure easily)
>> >
>> > Open the DS Record
>> > Check the Datastructure XML:
>> > here you have to insert
>> > <meta type="array">
>> > <langChildren type="integer">1</langChildren>
>> > <langDisable type="integer">1</langDisable>
>> > </meta>
>> >
>> > Should look like this afterwards:
>> >
>> > <?xml version="1.0" encoding="utf-8" standalone="yes" ?>
>> >> <T3DataStructure>
>> >> <meta type="array">
>> >> <langChildren type="integer">1</langChildren>
>> >> <langDisable type="integer">1</langDisable>
>> >> </meta>
>> >> <ROOT type="array">
>> >> <tx_templavoila type="array">
>> >> <title>ROOT</title>
>> >> <description>Select the HTML element on the page which you
>> >> want to be the overall container element for the
>> template.</description>
>> >> </tx_templavoila>
>> >> ...
>> >> ...
>> >>
>> >
>> > Now you will be able to use ONLY the same structure
>> >
>> > If you have made a copy of the DS before we changed it rename it
>> something
>> > like DS-seperate.
>> >
>> > Now you copy also all TOs assigned to this DS
>> > Open every TO record and assign the DS-separate Structure to it.
>> >
>> > Now you can choose between working with an separate structure or with
>> same
>> > structure easily and you can switch inbetween.
>> >
>> > --------------------
>> >
>> > LAST an IMPORTANT step
>> >
>> > Check if you have created the Languages in te Globe
>> > Then check your setup if you have inserted the Language record here.
>> >
>> > i.e.
>> > #LanguageMenu
>> > lib.languageMenu < plugin.tx_srlanguagemenu_pi1
>> > lib.languageMenu.languagesUidsList = 1,2,3,4,5,6,7,8,9,10
>> > lib.languageMenu.defaultLayout= 0
>> > subparts.languageMenu < lib.languageMenu
>> >
>> > # Localization:
>> > config {
>> > linkVars = L
>> > sys_language_mode = content_fallback
>> > sys_language_overlay = 1
>> > }
>> >
>> > [globalVar = GP:L=1]
>> > config {
>> > sys_language_uid = 1
>> > language = en
>> > locale_all = en_EN
>> > metaCharset = utf-8
>> > }
>> >
>> > [globalVar = GP:L=2]
>> > config {
>> > sys_language_uid = 2
>> > language = de
>> > }
>> >
>> > [globalVar = GP:L=3]
>> > config {
>> > sys_language_uid = 3
>> > language = th
>> > }
>> >
>> > [globalVar = GP:L=4]
>> > config {
>> > sys_language_uid = 4
>> > language = cn
>> > }
>> >
>> > [globalVar = GP:L=5]
>> > config {
>> > sys_language_uid = 5
>> > language = ar
>> > }
>> >
>> > [globalVar = GP:L=6]
>> > config {
>> > sys_language_uid = 6
>> > language = il
>> > }
>> >
>> > [globalVar = GP:L=7]
>> > config {
>> > sys_language_uid = 7
>> > language = gr
>> > }
>> >
>> > [globalVar = GP:L=8]
>> > config {
>> > sys_language_uid = 8
>> > language = ru
>> > }
>> >
>> > [globalVar = GP:L=9]
>> > config {
>> > sys_language_uid = 9
>> > language = hi
>> > }
>> >
>> > [globalVar = GP:L=10]
>> > config {
>> > sys_language_uid = 10
>> > language = jp
>> > }
>> >
>> > [global]
>> >
>> > And then it should work - if you have also a language changer on the
>> page
>> > - Check it
>> >
>> > Andi
>> >
>> >
>> >
>> >
>> >
>> >
>> > 2007/6/7, Andreas Becker <ab.becker (AT) web (DOT) de>:
>> >>
>> >> Ok Jeppe
>> >>
>> >> Then go to Page
>> >>
>> >> Click on Localisation and have a look there is standing Separate
>> >> Structure
>> >> 1:1
>> >>
>> >> If yes you are working in an environment where each localised page
>> >> will be
>> >> created with aseparate structure.
>> >>
>> >> Click on view page translation and check if you can see the
>> >> contentelement
>> >> in the backend? if not check under UNUSED Elements
>> >>
>> >> get back here
>> >>
>> >> Andi
>> >>
>> >> 2007/6/7, Jeppe Donslund < jd (AT) webmasters (DOT) dk>:
>> >> >
>> >> > Yes I Am.
>> >> > I have tried to follow the localization Tutorial, but it seems a
>> little
>> >> > out of date.
>> >> >
>> >> > Jeppe
>> >> >
>> >> >
>> >> > Andreas Becker skrev:
>> >> > > Hi Jeppe
>> >> > >
>> >> > > Are you working with TemplaVoila?
>> >> > >
>> >> > > Andi
>> >> > >
>> >> > > 2007/6/7, Jeppe Donslund < jd (AT) webmasters (DOT) dk>:
>> >> > >>
>> >> > >> Hi,
>> >> > >>
>> >> > >> When I translate a page and uses the L=2 to view the translation
>> it
>> >> > is
>> >> > >> only my menu that is translated. Content is still default
>> language.
>> >> > >>
>> >> > >> How can that be?
>> >> > >>
>> >> > >> Regards,
>> >> > >> Jeppe D
>> >> > >> ___